`juju run` should have method to trigger the action to run on all units of an application
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
Wishlist
|
Unassigned |
Bug Description
Some charms, such as cs:telegraf require running actions to complete charm/software upgrades.
for instance, going from telegraf-28 to telegraf-29 provides a juju status which notes:
Install filebeat-6.8.0 with the 'reinstall' action.
On each unit.
As a standard openstack cloud has ~50+ such units, I'd rather not have to write an awk-based loop to iterate through these units, but rather juju run-action should have an [--application | -a] flag or an application/all argument to trigger the action to run on all units of the application.
While this is certainly not an ideal way for the charm to be written for upgrades, it is the choice of that charm development team to continue requiring the upgrade to be triggered manually. See issue https:/
For simple actions with no parameters, the simple workaround is to use:
juju run --application filebeat actions/reinstall
summary: |
- run-action should have a --application flag to trigger the action to run - on all units of an application + run-action should have method to trigger the action to run on all units + of an application |
Changed in juju: | |
status: | New → Triaged |
Thanks for the suggestion Drew. I've added it to the community discourse[0] to see if we can judge support. Feels like a useful feature, in my opinion.
[0]: https:/ /discourse. jujucharms. com/t/1529