Add charm metadata for 'juju run-action' on the operator pod
Bug #1870487 reported by
John A Meinel
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
Low
|
Unassigned |
Bug Description
At least as far as I can tell, you can't do:
juju run-action --operator
We do support 'juju run --operator'. There are use cases for getting information from the state that the charm is acting on, not just the state that the application is operating on.
(sorry about the earlier confusion around juju-v3 feature flag, that isn't actually relevant here.)
summary: |
- 'juju run --operator' only available with juju-v3 set + 'juju run --operator' not available for 'juju run-action' |
description: | updated |
To post a comment you must log in.
actions that are for k8s operator charms (you need to turn on the k8s-operators feature flag to use this capability) automatically run actions on the charm pod as there is no separate workload.
But yes, actions currently only run on the workload pod as the expectation was that the semantics would be similar to vm deployments; actions are operations on the workload.
Do we have any use cases that we don't yet satisfy either of the above scenarios?