Do not resolve params of irrelevant stages - #425
Merged
Conversation
GrahamCampbell
force-pushed
the
defer-irrelevant-stage-params
branch
from
August 4, 2026 15:39
100ce06 to
a9de240
Compare
GrahamCampbell
force-pushed
the
defer-irrelevant-stage-params
branch
from
August 4, 2026 15:46
a9de240 to
b0c2f96
Compare
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Variables in
params.<stage>sections are now only resolved for the effective stage (anddefault). Params of other stages are left untouched: their sources are not invoked (no wasted SSM/remote calls) and their errors (unknown sources, missing env vars, etc.) no longer fail the command.Explicit references like
${self:params.prod.domain}still resolve the targeted property on demand, exactly as before. Variable syntax errors are still reported for all stages, including ones surfaced late (e.g. in an object resolved from a plugin-provided source).Known limitation: when a whole section is defined with a single variable (e.g.
params: ${file(./params.yml)}orparams.prod: ${file(./prod-params.yml)}), that variable itself is still resolved, as the configuration schema requires these sections to be objects. Values nested in the resolved object are however only resolved for the effective stage.