If you have a stacker file A.yaml that uses a substitution ${{A}}, and then another file B.yaml, that does not use ${{A}}, but does have A.yaml as a prerequisite, then running stacker build on B.yaml still requires a sub value for ${{A}}.
The build fails with the error error: no value for substitution A but does not say that it came from A.yaml.
This is confusing when you look for the use of ${{A}} in B.yaml and don't find it.
stacker version
main
Describe the bug
If you have a stacker file A.yaml that uses a substitution
${{A}}, and then another file B.yaml, that does not use${{A}}, but does have A.yaml as a prerequisite, then runningstacker buildon B.yaml still requires a sub value for${{A}}.The build fails with the error
error: no value for substitution Abut does not say that it came from A.yaml. This is confusing when you look for the use of${{A}}in B.yaml and don't find it.To reproduce
No response
Expected behavior
No response
Screenshots
No response
Additional context
No response