Add oblt-cli/flags action

[reakaleek]

No description provided.

[reakaleek]

@v1v I was playing around with this a bit.

But this is the only common I could find across the commands.

Adding all the cases would make this unnecessarily complex.

Should we still use this for the common flags?

[v1v]

Should we still use this for the common flags?

Maybe we need one per cli flag?

• oblt-cli/flag-prefix
• oblt-cli/flag-suffix
• oblt-cli/flag-gitops

Then consumers can choose the ones they need , for instance , oblt-cli/cluster-create-serverless/action.yml could be changed to something like:

name: 'oblt-cli/cluster-create-serverless'
description: 'Run the oblt-cli wrapper to create a serverless cluster.'
inputs:
...
runs:
  using: "composite"
  steps:
   - uses: elastic/oblt-actions/oblt-cli/flags-prefix@v1
      id: prefix
      with:
        cluster-name-prefix: 'prefix'

    - uses: elastic/oblt-actions/oblt-cli/flags-suffix@v1
      id: suffix
      with:
        cluster-name-suffix: 'suffix'

    - uses: elastic/oblt-actions/oblt-cli/flags-gitops@v1
      id: gitops
      with:
        gitops: true

    - uses: elastic/oblt-actions/oblt-cli/flags-dry-run@v1
      id: dry-run
      with:
        dry-run: true

    - uses: elastic/oblt-actions/oblt-cli/setup@v1.2.0
      with:
        github-token: ${{ inputs.github-token }}
        slack-channel: ${{ inputs.slack-channel }}
        username: ${{ inputs.username }}

    - run: |
        oblt-cli cluster create custom \
          --template serverless \
          ${{ steps.dry-run.outputs.params }} \
          ${{ steps.gitops.outputs.params }} \
          ${{ steps.suffix.outputs.params }} \
          ${{ steps.prefix.outputs.params }}
      shell: bash
      env:
        GITHUB_TOKEN: ${{ inputs.github-token }}

What do you think?

[reakaleek]

Maybe we need one per cli flag?

IMO, all those params can be put into a single action.
The complexity lies in the logic when gitops: true is enabled.
which is totally different for cluster-create-ccs.