-
Notifications
You must be signed in to change notification settings - Fork 4k
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
fix(servicecatalogappregistry): RAM Share is replaced on every change to Application #24760
Conversation
<body> Testing done ------------------------------------- * Related items ------------------------------------ * SIM/auto-cut ticket
<body> Testing done ------------------------------------- * Related items ------------------------------------ * SIM/auto-cut ticket
<body> Testing done ------------------------------------- * Related items ------------------------------------ * SIM/auto-cut ticket
<body> Testing done ------------------------------------- * Related items ------------------------------------ * SIM/auto-cut ticket
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The pull request linter has failed. See the aws-cdk-automation comment below for failure reasons. If you believe this pull request should receive an exemption, please comment and provide a justification.
A comment requesting an exemption should contain the text Exemption Request
. Additionally, if clarification is needed add Clarification Request
to a comment.
✅ Updated pull request passes all PRLinter validations. Dissmissing previous PRLinter review.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please make sure that your PR title confirms to the conventional commit standard (fix
, feat
, chore
) and that it is written in a style that will reflect correctly in the change log. In particular, if this is a bug fix, please describe the bug that was fixed, not the change you made (See Contributing Guide, Pull Requests)
Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
… to Application (aws#24760) `Application.shareApplication` can be called multiple times which generates different resources within the same `Application` construct. The share construct id generation was based on child length of `Application` construct. This makes every change to the `Application` construct can unnecessarily replace the RAM share when the share actually needs no update. Similar to the solution for `addAttributeGroup` introduced in the [previous update](aws#24672), this commit starts to require both construct id and share name in the `Application.shareApplication` method input, which are used to create RAM share construct. For `ApplicationAssociator`, `Application.shareApplication` is called for cross-account stack associations. Share construct id depends on the node unique id of the application in `ApplicationAssociator` and the node unique id of the stack to be associated. This reduces unnecessary share replacement in `ApplicationAssociator` stack. BREAKING CHANGE: This commit involves share replacement during the deployment of `ApplicationAssociator` due to share construct id update. After this change, frequent share replacements due to structural change in `Application` construct should be avoided. `Application.shareApplication` starts to require construct id (first argument) and share name (added in `ShareOption`) as input. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Application.shareApplication
can be called multiple times which generates different resources within the sameApplication
construct. The share construct id generation was based on child length ofApplication
construct. This makes every change to theApplication
construct can unnecessarily replace the RAM share when the share actually needs no update.Similar to the solution for
addAttributeGroup
introduced in the previous update, this commit starts to require both construct id and share name in theApplication.shareApplication
method input, which are used to create RAM share construct.For
ApplicationAssociator
,Application.shareApplication
is called for cross-account stack associations. Share construct id depends on the node unique id of the application inApplicationAssociator
and the node unique id of the stack to be associated. This reduces unnecessary share replacement inApplicationAssociator
stack.BREAKING CHANGE: This commit involves share replacement during the deployment of
ApplicationAssociator
due to share construct id update. After this change, frequent share replacements due to structural change inApplication
construct should be avoided.Application.shareApplication
starts to require construct id (first argument) and share name (added inShareOption
) as input.By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license