-
Notifications
You must be signed in to change notification settings - Fork 3.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CloudFormationProduct: product_versions only support ONE version #16892
Comments
Thanks for bringing this issue up with detailed write up. We will look into this and release fix soon, I think I know what the issue is. |
…on from assets This small PR should fix an issue brought up that we used a static `Template` as the resource name for assets which causes a collision if you have multiple versions. The correct configuration should be that the asset name is unique for each unique template file uploaded for a product version. Fixes: [aws#16892](aws#16892) Testing done ------------------ * `yarn build && yarn test`
…ons from assets This small PR should fix an issue brought up that we used a static `Template` as the resource name for assets which causes a collision if you have multiple versions. The correct configuration should be that the asset name is unique for each unique template file uploaded for a product version. Fixes: aws#16892
…ons from assets This small PR should fix an issue brought up that we used a static `Template` as the resource name for assets which causes a collision if you have multiple versions. The correct configuration should be that the asset name is unique for each unique template file uploaded for a product version. Fixes: aws#16892
…ons from assets. (#16914) This small PR should fix an issue brought up that we used a static `Template` as the resource name for assets which causes a collision if you have multiple versions. The correct configuration should be that the asset name is unique for each unique template file uploaded for a product version. Fixes: #16892 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
|
…ons from assets. (aws#16914) This small PR should fix an issue brought up that we used a static `Template` as the resource name for assets which causes a collision if you have multiple versions. The correct configuration should be that the asset name is unique for each unique template file uploaded for a product version. Fixes: aws#16892 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
What is the problem?
When adding more than one
CloudFormationProductVersion
element the sequence ofproduct_versions
in theCloudFormationProduct
constructor, CDK errors out during synth.Reproduction Steps
With the following in
./example/service_catalog.py
...the following in ./example/products/AccountSpecificTrustRoleReadOnlyAccess.yaml"
.. the following in
./example/product/AccountSpecificTrustRole.yaml
.. and the following in
./app.py
This error will be produced:
What did you expect to happen?
I expected
product_versions
to be able to handle a sequence ofCloudFormationProductVersion
as stated in the documentation :What actually happened?
The first element creates a "Template" construct, which is the same name the following elements tries to use. Which causes the problem, as the Construct names have to be unique.
CDK CLI Version
1.127.0 (build 0ea309a)
Framework Version
No response
Node.js Version
v16.10.0
OS
macOS Big Sur, Version 11.5.2
Language
Python
Language Version
Python 3.9.7
Other information
No response
The text was updated successfully, but these errors were encountered: