How to work with action output

[sssler-scania (Erik Lönroth)]

I have a large model with a few hundreds of units.

An action; “diagnose”, outputs some values set by the action.

I want to write some code to filter the result from the action and the documentation is not covering well how to do this. Here is the documentation I refer to:

Working with actions

Actions are scripts that are triggered via the client, and applied to a unit. They are described within individual charms. An action’s parameters are defined as a map in a YAML file, and are validated against the schema defined in actions.yaml. See Actions for the charm author for detailed information. Action commands The following commands are used to manage actions: actions : list actions defined for a service run-action : queue an action for execution show-action-output : show output of…

Is there anyone who can assist me on this topic?

• I would love to get some pointers as how I can work with actions with a juju and/or bash application for building, automation around actions.

• Adding the above information to the official documentation would be a great thing.

[timClicks (Tim McNamara)]

@sssler-scania

I want to write some code to filter the result from the action and the documentation is not covering well how to do this.

We’ve recently changed the behaviour of actions to make this simpler. There shouldn’t need to be show-action-output step.

Juju Actions: opt-in to new behaviour from Juju 2.8

The UX around Juju Actions has undergone a fairly radical re-design to address some long standing issues and deliver some nice usability improvements. An early version of this was delivered in Juju 2.7. Coming in Juju 2.8 is a more polished iteration. Key points: terminology changes running an action defaults to synchronous (block until done) running actions can be cancelled new ability to display progress log messages cleaner plain text output option stdout and stderr included in output nume…