-
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(custom-resources): incorrect IAM prefix generated for CloudWatch actions #33078
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 fails with the following errors:
❌ Fixes must contain a change to an integration test file and the resulting snapshot.
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.
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #33078 +/- ##
=======================================
Coverage 80.78% 80.78%
=======================================
Files 232 232
Lines 14111 14111
Branches 2453 2453
=======================================
Hits 11400 11400
Misses 2431 2431
Partials 280 280
Flags with carried forward coverage won't be shown. Click here to find out more.
|
✅ Updated pull request passes all PRLinter validations. Dismissing previous PRLinter review.
f64d0b2
to
3f74d79
Compare
I want to understand this more. Have you tested on existing stack that uses |
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.
Changes look good, just one minor comment.
onDelete: { | ||
service: 'CloudWatchLogs', | ||
action: 'deleteRetentionPolicy', | ||
service: 'CloudWatch', | ||
action: 'tagResource', | ||
parameters: { | ||
logGroupName: '/aws/lambda/loggroup', | ||
ResourceARN: 'dummy', | ||
Tags: [{ Key: 'Name', Value: 'prod' }], | ||
}, | ||
physicalResourceId: PhysicalResourceId.of('add_tag'), |
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.
Should we add a new test instead of modifying this one so that we can continue testing cloudwatch-logs?
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.
I did this because the onCreate
is already testing service: 'CloudWatchLogs'
(on line 19 above). So my thinking is, rather than testing the same thing via onDelete
, I can change the onDelete
to test service: 'CloudWatch'
.
@samson-keung this PR is 3 times the GetFunction custom resource PR.. This worries me a bit. |
That one was 700 files. This is way smaller. I had some trouble making the big one. This one was good, no trouble. |
OK cool, I was looking at the lines changed and this one is much bigger. |
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). |
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). |
This pull request has been removed from the queue for the following reason: The merge conditions cannot be satisfied due to failing checks:You should look at the reason for the failure and decide if the pull request needs to be fixed or if you want to requeue it. If you want to requeue this pull request, you need to post a comment with the text: |
83a15f1
to
b259882
Compare
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). |
Comments on closed issues and PRs are hard for our team to see. |
Issue # (if applicable)
Closes #32968.
Reason for this change
The mapping to look up the IAM prefix from a given service has a incorrect entry for Cloudwatch. It says Cloudwatch uses
monitoring
as the prefix but it is actuallycloudwatch
instead.I cannot find any service that uses
monitoring
as prefix so I think it is safe to assume that nothing relies on themonitoring
value. Therefore, there is no feature flag used in this PR.Description of changes
Updated the IAM prefix mapping.
Describe any new or updated permissions being added
Updated the mapping to use correct IAM prefix.
Description of how you validated changes
Updated unit tests to use AwsCustomResource with a Cloudwatch call.
Added integ test to use AwsCustomResource with a Cloudwatch call to tag an alarm and verify the tag is indeed added successfully.
Checklist
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license