Introduce meta actions

[davidferlay]

Observed

User may need to often execute the same suite of commands Yet there is no way to execute multiple actions using only 1 single command

For instance, For each deploy, after having done some devlopments+bumped, user currently needs to run 4 actions

plasmactl compose --skip-not-versioned --conflicts-verbosity
plasmactl platform:compare-artifacts
plasmactl platform:components-propagate dev file.diff

Gradle has a way to do that "meta action": The common pattern there is to have a task that depends on tasks. One task that has ONLY dependencies will be a "meta" task

Expected

Would be great to have a way to define meta actions, where one command would run multiple actions

• This should work for both commands brought by native plugins + commands brought by actions
• Maybe meta action should be defined with a different kind of action.yaml

  action:
  kind: Meta
  title: Build
  description: Handles every actions related to building artifact to be deployed
  actions: 
  - compose --skip-not-versioned --conflicts-verbosity
  - platform:compare-artifacts
  - platform:components-propagate dev file.diff

• Or maybe instead of creating a new kind of action, it could be handled solely by dependencies, like
  • action platform:components-propagate has an attribute that says it need to run platform:compare-artifacts before running itself
  • and action platform:compare-artifacts dev file.diff has an attribute that says it need to run compose --skip-not-versioned --conflicts-verbosity before running itself
  • but in this case need ability to run all actions with expected args and options

In any case, maybe this functionality should be brought by a launchrctl plugin, to keep functionality separate from core and keep it simple

• Or maybe instead of adding this to launchrctl, we could simply use a Makefile (or something similar)

[davidferlay]

For now, meta action was built as a plugin : https://github.com/skilld-labs/plasmactl-meta

[davidferlay]

Re-opening this issue as plasmactl web-ui also have a need to visually represent actions that should run sequentially and in parallel

For now it's kind of hardcoded in plasmactl-meta action, which execute calls to other actions. But looks like we need a more generic approach to make a visual representation of that "flow" in UI

Most likely that will requre more thinking and refactor of meta action. If we need to show something in web-ui before that happens, we could duplicate logic in some config file (but that's obviously not a viable long term solution)

[davidferlay]

Got the wrong idea about the intent of this UI, it's related to integration flows; not actions