Skip to content
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(cli): externally managed stack notification arns are deleted on deploy #32163

Merged
merged 7 commits into from
Nov 18, 2024

Conversation

iliapolo
Copy link
Contributor

@iliapolo iliapolo commented Nov 17, 2024

Closes #32153.

Reason for this change

When a stack contains externally managed notification ARNs (i.e ones that were added outside of CDK), a cdk deploy command will remove those ARNs.

Description of changes

We incorrectly default notification ARNs to [] instead of undefined. When an empty array is passed to the SDK , it reasonably assumes you want to delete existing ARNs (because how otherwise would you delete them). If on the other hand you don't pass notification ARNs at all to the SDK (e.g undefined), it will preserve them.

This is the correct behavior and CDK should follow suite. This does however create a (maybe) quirky API ergonomic where in order to remove notification ARNs, one must pass [] instead of simply omitting the property.

This stems from the fact notification ARNs are not managed through the template, but rather through imperative actions. So it seems reasonable al things considered.

Description of how you validated changes

Added both unit and integration tests.

Checklist


By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

@github-actions github-actions bot added the p2 label Nov 17, 2024
@aws-cdk-automation aws-cdk-automation requested a review from a team November 17, 2024 10:45
@mergify mergify bot added the contribution/core This is a PR that came from AWS. label Nov 17, 2024
@github-actions github-actions bot added bug This issue is a bug. effort/medium Medium work item – several days of effort p0 and removed p2 labels Nov 17, 2024
Copy link
Collaborator

@aws-cdk-automation aws-cdk-automation left a 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.

@aws-cdk-automation aws-cdk-automation added the pr/needs-cli-test-run This PR needs CLI tests run against it. label Nov 17, 2024
@@ -830,9 +841,7 @@ switch (stackSet) {
new DockerInUseStack(app, `${stackPrefix}-docker-in-use`);
new DockerStackWithCustomFile(app, `${stackPrefix}-docker-with-custom-file`);

new NotificationArnPropStack(app, `${stackPrefix}-notification-arn-prop`, {
notificationArns: [`arn:aws:sns:${defaultEnv.region}:${defaultEnv.account}:${stackPrefix}-test-topic-prop`],
Copy link
Contributor Author

@iliapolo iliapolo Nov 17, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Moved this to inside the stack, which now reads it from an env variable to avoid hard coding stuff.

}
}));

integTest('deploy deletes ALL notification arns when empty array is passed', withDefaultFixture(async (fixture) => {
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is essentially testing SDK behavior but what the heck

// - undefined => cdk ignores it, as if it wasn't supported (allows external management).
// - []: => cdk manages it, and the user wants to wipe it out.
// - ['arn-1'] => cdk manages it, and the user wants to set it to ['arn-1'].
const notificationArns = (!!options.notificationArns || !!stack.notificationArns)
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is the fix.

@iliapolo iliapolo marked this pull request as ready for review November 17, 2024 15:07
Copy link

codecov bot commented Nov 17, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 77.18%. Comparing base (b70ad52) to head (b63d5c0).
Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main   #32163      +/-   ##
==========================================
- Coverage   77.18%   77.18%   -0.01%     
==========================================
  Files         105      105              
  Lines        7163     7161       -2     
  Branches     1311     1312       +1     
==========================================
- Hits         5529     5527       -2     
  Misses       1454     1454              
  Partials      180      180              
Flag Coverage Δ
suite.unit 77.18% <100.00%> (-0.01%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Components Coverage Δ
packages/aws-cdk 77.18% <100.00%> (-0.01%) ⬇️

@mrgrain mrgrain added the pr-linter/exempt-integ-test The PR linter will not require integ test changes label Nov 17, 2024
@mrgrain
Copy link
Contributor

mrgrain commented Nov 17, 2024

Build failed in CodeBuild. Not clear why status not reported back.

@iliapolo iliapolo removed the pr-linter/exempt-integ-test The PR linter will not require integ test changes label Nov 18, 2024
@iliapolo iliapolo added the pr-linter/exempt-integ-test The PR linter will not require integ test changes label Nov 18, 2024
@iliapolo
Copy link
Contributor Author

Waiting for the pipeline to succeed

@aws-cdk-automation
Copy link
Collaborator

➡️ PR build request submitted to test-main-pipeline ⬅️

A maintainer must now check the pipeline and add the pr-linter/cli-integ-tested label once the pipeline succeeds.

@aws-cdk-automation
Copy link
Collaborator

AWS CodeBuild CI Report

  • CodeBuild project: AutoBuildv2Project1C6BFA3F-wQm2hXv2jqQv
  • Commit ID: b63d5c0
  • Result: SUCCEEDED
  • Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

@mrgrain mrgrain added pr-linter/cli-integ-tested Assert that any CLI changes have been integ tested and removed pr/needs-cli-test-run This PR needs CLI tests run against it. labels Nov 18, 2024
@aws-cdk-automation aws-cdk-automation dismissed their stale review November 18, 2024 13:53

✅ Updated pull request passes all PRLinter validations. Dismissing previous PRLinter review.

Copy link
Contributor

mergify bot commented Nov 18, 2024

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).

@mergify mergify bot merged commit 9966f57 into main Nov 18, 2024
23 of 24 checks passed
@mergify mergify bot deleted the epolon/preserver-notification-arns branch November 18, 2024 13:57
Copy link

Comments on closed issues and PRs are hard for our team to see.
If you need help, please open a new issue that references this one.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 18, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug This issue is a bug. contribution/core This is a PR that came from AWS. effort/medium Medium work item – several days of effort p0 pr-linter/cli-integ-tested Assert that any CLI changes have been integ tested pr-linter/exempt-integ-test The PR linter will not require integ test changes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

core: cdk deploy wiping stack notification ARNs property
3 participants