This repository has been archived by the owner on Jan 8, 2024. It is now read-only.
Backport of Feature: Update pipelines parser to evaluate input variables into release/0.10.x #4133
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
hc-github-team-waypoint
force-pushed
the
backport/feat/pipelines/input-variables/oddly-desired-seal
branch
from
f73dc74
to
20058b2
Compare
hc-github-team-waypoint
deleted the
backport/feat/pipelines/input-variables/oddly-desired-seal
branch
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Backport
This PR is auto-generated from #4132 to be assessed for backporting due to the inclusion of the label backport/0.10.x.
The below text is copied from the body of the original PR.
This pull request introduces input variables being evaluated inside
pipeline {}stanzas. It ends up rearranging how we parse pipelines and steps to support the lazy-decoding that Waypoint does to evaluate and resolve variables later in the parsing process.It also had to modify how
waypoint initdoes its initial sync of pipeline definitions. Now instead we do a "shallow sync" of the pipeline name, owner, and a base step. This mirrors how we sync applications onwaypoint initin that we don't sync the entire parsed hcl config, only the app name on init.Fixes #4122