fix(validate): honor effective env cascade - #524
Merged
Conversation
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
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
Advance #248 by making
strut <stack> validateevaluaterequired_varsagainst the same effective environment cascade used by deployment.Changes
validate_env_filecommon.env, the selected stack/project base env, the active topology host layer, and generated stack/host layers in normal last-wins precedenceset -eValidation
bats tests/test_validate.bats tests/test_utils.bats tests/test_env_gen_layer.bats tests/test_topology.bats tests/test_cli_resolve.bats </dev/null— 178 passedbats tests/ </dev/null— 2,650 passed, 2 expected skipsshellcheck -x -S warning lib/cmd_validate.shbash -n lib/cmd_validate.shgit diff --checkAdvances #248.