fix: add flag that allows us to control al2 rollout independent of buildbot #6021
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
As explained in https://github.com/netlify/pod-dev-foundations/issues/581#issuecomment-1731022753, enabling the
zisi_golang_use_al2
flag will lead to failures in versions of the CLI that don't have the #6020 patch. That means we need to decouple the rollout ofzisi_golang_use_al2
in buildbot (where @netlify/build is always up-to-date) from the rollout in the CLI, where the flag also affects versions with broken behaviour. That's why this PR adds a second flag, which we can use to control the CLI rollout independently.Part of https://github.com/netlify/pod-dev-foundations/issues/581
For us to review and ship your PR efficiently, please perform the following steps:
passes our tests.
A picture of a cute animal (not mandatory, but encouraged)