Stack Artifact Parameters Ignored #19720
Replies: 6 comments 2 replies
-
Hey @rabbittsoup 👋🏻 Are you still looking for guidance on this issue? If so, could you elaborate on what you mean by
Also an explanation of how you're checking this would be helpful. |
Beta Was this translation helpful? Give feedback.
-
Yes, this is still an open issue. |
Beta Was this translation helpful? Give feedback.
-
It's been a while since I looked at this. If I recall, the issue is that the cloud assembly stack artifact contains an interface for cloud formation parameters. However this interface is dropped during deployment, so it never gets merged into the deployment time stack parameters. i.e. Setting parameters during synthesis is allowed, but never used. |
Beta Was this translation helpful? Give feedback.
-
I'm not sure why i originally relabeled this as a guidance issue - Ryan or I will investigate this. Thanks for getting back quickly! |
Beta Was this translation helpful? Give feedback.
-
If this is still relevant, please open a bug report with more detail |
Beta Was this translation helpful? Give feedback.
-
Hello! Reopening this discussion to make it searchable. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
The stack artifact in a manifest allows for passing codified parameters to the deploy phase. However, those parameters never seem to be merged into the parameters used at deploy time.
At deploy time, only the parameters specified on the command line, or those retrieved from a previously deployed stack in the cloud are used.
aws-cdk/packages/aws-cdk/lib/api/deploy-stack.ts
Line 217 in 8a949dc
Beta Was this translation helpful? Give feedback.
All reactions