Skip to content

feat(gen/circleci): add --skip-ats to opt out of ATS chart tests - #2097

Open
mcharriere wants to merge 3 commits into
mainfrom
opt-out-ats
Open

feat(gen/circleci): add --skip-ats to opt out of ATS chart tests#2097
mcharriere wants to merge 3 commits into
mainfrom
opt-out-ats

Conversation

@mcharriere

Copy link
Copy Markdown
Contributor

What

Adds a --skip-ats opt-out flag to devctl gen circleci.

By default an app-flavour repo runs architect/run-tests-with-ats between build-chart and the chart push, and generation emits the canonical tests/ats/Pipfile. --skip-ats opts out:

  • Omits the run-tests-with-ats jobs (execute-chart-tests / execute-chart-tests-release) from .circleci/workflows.yml.
  • Re-points the chart push jobs' requires to build-chart directly, keeping the dependency graph valid.
  • Suppresses the tests/ats/Pipfile (ATSInputs() returns nil).

Only applies to the app flavour. Follows the existing --branch-publish opt-in wiring end to end (flag -> circleci.Config -> params.Params -> template).

Notes

Template edits are whitespace-neutral for the default (SkipATS=false), so existing golden tests pass unchanged. Added Test_SkipATSOmitsChartTests; package tests and go vet are green.

By default an app-flavour repo runs architect/run-tests-with-ats between
build-chart and the chart push, and generation emits tests/ats/Pipfile.
--skip-ats suppresses those test jobs and the Pipfile; the chart push then
gates directly on build-chart.
@mcharriere
mcharriere requested a review from a team as a code owner July 23, 2026 17:27
@mcharriere mcharriere changed the title feat(gen-circleci): add --skip-ats to opt out of ATS chart tests feat(gen/circleci): add --skip-ats to opt out of ATS chart tests Jul 23, 2026

@piontec piontec left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Do you also have the part that has to go to github/github?

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