User defined plugin deployment order selection

[LeoDiazL]

Nowadays we have a pretty static definition of what to run and when in Bitops.

Even though I know the order can be changed by doing some mods, I think it would be nice to do something that could adapt easily to what the user needs.
I can think of more than one scenario where I would like to run some Ansible playbooks before running Terraform for example, but would like to run an Ansible playbook post terraform excecution too.

I can think of two approaches.

• Folder based order. Simple 0 --> Z
• File definition with the order this folders should be read.

We can populate the deployments list by just listing the directories available inside the deployment, and then read which plugin is needed based on the bitops.config.yaml

---

Slack discussion: https://bitovi.slack.com/archives/C0129U3GL93/p1669301822079609

[arm4b]

From the discussion, the following projects were mentioned where user can control the order of runs in the workflow config:

• https://atmos.tools/core-concepts/workflows/
• https://pypyr.io/
• https://dagger.io/

Per @PhillypHenning :

YAML deployment order control via root-level bitops.config.yaml:

deployments:
    ansible_first:
      plugin: ansible
    terraform:
      plugin: terraform
    ansible_final:
      plugin: ansible

Alphanumeric dir name order in bitops.config.yaml via option:

deployment_order: alphanum
deployments: {}

User names the deployment dirs like 00_ansible, 01_terraform, 02_ansible, or similar.

[arm4b]

Speaking of UX, if going with the YAML config definition, it could consistently work together with a Feature: Run a Deployment sub-step CLI #318.
For instance, having this bitops config:

deployments:
  prepare-instance:
    plugin: ansible
  terraform-provision:
    plugin: terraform
  setup-instance:
    plugin: ansible

Based on the named deployment definitions, we could potentially provide an option to nicely run the deployment sub-step in CLI like this:

$ <docker_cmd> bitops run prepare-instance
$ <docker_cmd> bitops run terraform-provision
$ <docker_cmd> bitops run setup-instance

[mickmcgrath13]

@LeoDiazL @armab is this a duplicate of #259 ?

[arm4b]

Good find on
Duplicate of #259

Let's close it in favor of the original one.