Activity log for bug #1870487
| Date | Who | What changed | Old value | New value | Message |
|---|---|---|---|---|---|
| 2020-04-03 06:50:28 | John A Meinel | bug | added bug | ||
| 2020-04-03 06:54:24 | John A Meinel | summary | 'juju run --operator' only available with juju-v3 set | 'juju run --operator' not available for 'juju run-action' | |
| 2020-04-03 06:55:23 | John A Meinel | description | At least as far as I can tell, you can't do: juju run-action --operator You have to do: export JUJU_DEV_FEATURE_FLAG=juju-v3 juju run --operator I don't think there is any reason to not allow executing an action in the operator pod with --operator, and v3 should be used just because of the name of run-action => run. | 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.) | |
| 2020-04-07 01:38:23 | Ian Booth | juju: milestone | 2.8-beta1 | 2.8.1 | |
| 2020-04-07 01:38:46 | Ian Booth | summary | 'juju run --operator' not available for 'juju run-action' | Add charm metadata for 'juju run-action' on the operator pod | |
| 2020-06-08 04:22:06 | Tim Penhey | tags | k8s | act k8s | |
| 2020-06-08 04:22:14 | Tim Penhey | tags | act k8s | actions k8s | |
| 2020-06-08 04:22:19 | Tim Penhey | juju: milestone | 2.8.1 | 2.8-next | |
| 2022-11-03 17:14:52 | Canonical Juju QA Bot | juju: importance | High | Low | |
| 2022-11-03 17:14:54 | Canonical Juju QA Bot | tags | actions k8s | actions expirebugs-bot k8s |
