-
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
ServiceCatalog: Not possible to deploy two products within the same portfolio both of which have custom assets (lambdas) #25189
Comments
thanks for reporting this bug @ViktarKhomich. I am able to reproduce the issue and see that this id is static in the code. I am marking this bug as P2 which means our team won't be able to work on it immediately. However we welcome community PRs. If you would also like to contribute , here is the contributing guide to get started. |
@khushail thank you for your reply! In meanwhile, I noticed that you changed the current status of the issue to P1 and expected efforts for fixing are large. Does it mean you will fix it? Otherwise, I would like to contribute, because for us this issue is kind of blocker. |
Hi @ViktarKhomich , I marked it as P1 to bring it to the notice of Core team so it could be prioritised. But I understand they have a lot on their plate and might not work on a fix as soon as needed by you. So it sounds great if you are contributing. Please feel free to create a PR and our team would be happy to review it. |
… in the same portfolio (aws#25189)
Hi @khushail, |
I think the problem also applies to products in different portfolios in the same stack. |
Please discuss amongs the cdk team if you want to go for the proposed code change, or want to explore the suggestion proposed. I feel the suggested fix is accurate, so I would disagree with closing this and leaving it unattended: https://github.com/aws/aws-cdk/pull/26039/files/51c6272831ff7a82e06de5a0a9db44b055d7626a#r1243504435 |
… in the same portfolio (aws#25189) Check for the existing AssetDeploymentBucket and if it is, use it otherwise create a new one
…ts (#26885) To move the assets into the target bucket, a `BucketDeployment` was created for every `ProductStack`. Instead, we will now share the same `BucketDeployment` for all `ProductStacks`. This moves the custom resource around in the construct tree (leading to replacement), but that is a safe operation. Nothing will be destroyed by this move. Closes #25189. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
|
Describe the bug
I am facing an issue while working with the service catalog. Specifically, I am trying to deploy two service catalog products within the same portfolio, both of which have custom assets (lambdas in this case). However, I am encountering an error during the
synth
process.When I am using custom assets only for one product, then everything works fine.
Expected Behavior
I expect to be able to deploy two or more products within the same portfolio which can have the custom assets.
Current Behavior
I am able to use custom assets in every product within the same portfolio.
Reproduction Steps
cdk app with which bug can be easily reproduced:
Possible Solution
If I am right, then in the
ProductStackSynthesizer.js
file inaddFileAsset
method the name of the assets bucket deployment (marked with bold in the code snippet below) should be generated dynamically (now it is static):Additional Information/Context
No response
CDK CLI Version
2.75.1
Framework Version
No response
Node.js Version
16.17.0
OS
MacOS
Language
Typescript
Language Version
4.8.4
Other information
No response
The text was updated successfully, but these errors were encountered: