-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
feat(core): configure SNS topics to receive stack events on the Stack construct #30551
base: main
Are you sure you want to change the base?
Conversation
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.
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.
➡️ PR build request submitted to A maintainer must now check the pipeline and add the |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
✅ Updated pull request passes all PRLinter validations. Dismissing 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.
Looks solid. Couple clarifying questions so I can get a better sense of a few parts of the PR.
Other than the individual comments, main question would be about the notificationArns being put into the toolkit in some tests. From a user perspective, these options are added on the stack. Are the toolkit Arns a product of the cli option?
if (process.env.REPO_ROOT) { | ||
const monoRepo = await findYarnPackages(process.env.REPO_ROOT ?? ''); |
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.
When we go into this if block, will REPO_ROOT
ever be undefined?
@@ -75,13 +75,14 @@ const YARN_MONOREPO_CACHE: Record<string, any> = {}; | |||
* | |||
* Cached in YARN_MONOREPO_CACHE. | |||
*/ | |||
async function findYarnPackages(root: string): Promise<Record<string, string>> { | |||
export async function findYarnPackages(root: string): Promise<Record<string, string>> { |
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.
Quick blurb about the purpose of these changes? Is this cli integ test related?
@@ -187,7 +187,10 @@ integTest('context setting', withDefaultFixture(async (fixture) => { | |||
} | |||
})); | |||
|
|||
integTest('context in stage propagates to top', withDefaultFixture(async (fixture) => { | |||
// bootstrapping also performs synthesis. As it turns out, bootstarp-stage synthesis still causes the lookups to be cached, meaning that the lookup never |
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.
// bootstrapping also performs synthesis. As it turns out, bootstarp-stage synthesis still causes the lookups to be cached, meaning that the lookup never | |
// bootstrapping also performs synthesis. As it turns out, bootstrap-stage synthesis still causes the lookups to be cached, meaning that the lookup never |
// bootstrapping also performs synthesis. As it turns out, bootstarp-stage synthesis still causes the lookups to be cached, meaning that the lookup never | ||
// happens when we actually call `cdk synth --no-lookups`. This results in the error never being thrown, because it never tries to lookup anything. | ||
// Fix this by not trying to bootstrap; there's no need to bootstrap anyway, since the test never tries to deploy anything. | ||
integTest('context in stage propagates to top', withoutBootstrap(async (fixture) => { |
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.
🙏
sdkProvider: cloudExecutable.sdkProvider, | ||
deployments: new FakeCloudFormation({ | ||
'Test-Stack-A': { Foo: 'Bar' }, | ||
}, notificationArns), |
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.
Why are the arns being passed into the toolkit?
Issue # (if applicable)
#8581.
Reason for this change
It is easier and clearer to specify the SNS Topic ARNs on the stack construct itself instead of passing it as a command line argument.
Description of changes
Added a new optional stack prop,
notificationArns
, that is written to the CloudAssembly and concatenated with the CLI option--notification-arns
.Description of how you validated changes
Unit tests.
Checklist
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license