Actions API

[b-avb]

No description provided.

[olanod]

Before we grow current actions into a mess, let's define what an action is and draft an API for them :)

What is an "Action"?
The Virto app is a front-end for the Virto OS, like a regular OS it has executables/programs that are installed/removed dynamically, actions are an abstraction over the "programs" available in the OS, we can think of them as scripts that validate some inputs to execute one or more programs.

Actions need an API to allow anyone extend what users and organizations can execute in their OS via governance or a permissioned mechanism

• they need to provide information about their inputs and types to allow clients/front-ends prompt/display the right interface to the user to gather the required data
• they should allow to "dry-run" or a way to validate user input without triggering side effects
• they need some docs/description
• status / progress (?)