-
|
Hello folks Migration guide mentions that legacy synthesizer is not supported by V2:
However, I tried deploying a cdk v2 project with Can somebody clarify this? Is it safe to use legacy stack synthesizer or it will be removed soon? Thanks! |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 3 replies
-
|
Yes, this is a mistake in the migration guide. The @jerry-aws we should probably fix this, specifically this bullet point:
We should probably say something like "the legacy stack synthesizer is not recommended in V2". |
Beta Was this translation helpful? Give feedback.
-
|
@skinny85 thank you for clarifying this.
Can you please clarify this statement too? I'm considering using legacy synthesizer(and assume-role-credentials-plugin) because it is far less invasive approach for cross-account deployments using role requiring external id. |
Beta Was this translation helpful? Give feedback.
-
That's a pretty good summary 🙂.
Curious: what makes the legacy synthesizer better in this case? The default (non-legacy) synthesizer uses assume Roles for cross-account deployments too. |
Beta Was this translation helpful? Give feedback.
-
|
Right, it does use assume Roles for cross-account deployment. But in order to make it work, I need to a) make a custom bootstrap stack and b) explicitly pass synthesizer into every stack with explicitly passed external id. Setting one property in cdk.json is more convenient. |
Beta Was this translation helpful? Give feedback.
-
|
Hello! Reopening this discussion to make it searchable. |
Beta Was this translation helpful? Give feedback.
Yes, this is a mistake in the migration guide. The
LegacySynthesizeris definitely still supported, and will not be removed in V2, as it would be considered a breaking change.@jerry-aws we should probably fix this, specifically this bullet point:
We should probably say something like "the legacy stack synthesizer is not recommended in V2".