Skip to content

feat(runners): add runs_on input to infracost, smurf-tf-checks and tf-drift - #453

Closed
clouddrove-ci wants to merge 1 commit into
masterfrom
feat/runs-on-input
Closed

clouddrove-ci wants to merge 1 commit into
masterfrom
feat/runs-on-input

Conversation

@clouddrove-ci

Copy link
Copy Markdown
Member

Description

Adds a runs_on input to infracost.yml, smurf-tf-checks.yml and tf-drift.yml, with the same name, type and default (ubuntu-latest) that smurf-helm-deploy.yml and smurf-docker.yml already use. Every runs-on: ubuntu-latest in those three workflows becomes runs-on: ${{ inputs.runs_on }} (1, 3 and 1 jobs).

Existing callers are unchanged. Callers that must run on self-hosted runners (for example clouddrove/cd-baseline on the org k3s ARC scale set arc-runners, where GitHub-hosted runners are blocked) can pass their label. cd-baseline currently has these three callers paused with if: false for exactly this reason.

Docs: runs_on added to the usage examples in docs/infracost.md and docs/smurf-tf-checks.md.

Type of Change

  • 🔧 Workflow enhancement

Testing

  • actionlint: no new findings (the existing required-with-default and shellcheck notes in these files predate this change).

Release

Needs a patch tag (e.g. v2.1.8) so callers can pin it.

…-drift

Same input and default as smurf-helm-deploy and smurf-docker: runs_on defaults to ubuntu-latest, so existing callers are unchanged. Callers on self-hosted runners (for example an org k3s ARC scale set) can pass their label; today these three workflows cannot run anywhere GitHub-hosted runners are unavailable.
@clouddrove-ci

Copy link
Copy Markdown
Member Author

Closing: not pursuing this for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants