You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You can no longer invoke cdk synth for Stack1. Even if you call cdk synth Stack1, you will get the following error:
Multiple stacks selected (Stack1, Stack2), but output is directed to stdout. Either select one stack, or use --output to send templates to a directory.
Removing the stack1.addDependency(stack2) line makes cdk synth work again.
The text was updated successfully, but these errors were encountered:
rix0rrr
changed the title
cdk synth and Stack dependencies are in an unsolvable conflict
toolkit: make cdk synth to stdout not automatically select dependency stacks
Feb 19, 2019
If we report synthesis errors, they should only prevent the
affected stack from deploying; right now, since they are checked
during the synthesis step, they would abort the entire toolkit
run regardless of whether they would be selected or not.
Makes it possible to do region-dependent verification.
Fixes#1784.
ALSO IN THIS COMMIT
If the 'cdk synth' output goes to the screen, don't automatically
select upstream stacks for synthesis (as that would lead to an
immediate error).
Fixes#1783.
If we report synthesis errors, they should only prevent the
affected stack from deploying; right now, since they are checked
during the synthesis step, they would abort the entire toolkit
run regardless of whether they would be selected or not.
Makes it possible to do region-dependent verification.
Fixes#1784.
ALSO IN THIS COMMIT
If the 'cdk synth' output goes to the screen, don't automatically
select upstream stacks for synthesis (as that would lead to an
immediate error).
Fixes#1783.
If we report synthesis errors, they should only prevent the
affected stack from deploying; right now, since they are checked
during the synthesis step, they would abort the entire toolkit
run regardless of whether they would be selected or not.
Makes it possible to do region-dependent verification.
Fixes#1784.
ALSO IN THIS COMMIT
If the 'cdk synth' output goes to the screen, don't automatically
select upstream stacks for synthesis (as that would lead to an
immediate error).
Fixes#1783.
Right now, if you in your code, you do:
You can no longer invoke
cdk synth
forStack1
. Even if you callcdk synth Stack1
, you will get the following error:Removing the
stack1.addDependency(stack2)
line makescdk synth
work again.The text was updated successfully, but these errors were encountered: