-
Notifications
You must be signed in to change notification settings - Fork 18
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
Feature/improve arn parsing and IAM Policy testability #1080
Feature/improve arn parsing and IAM Policy testability #1080
Conversation
Is this sort of small improvement okay to add without a ticket - Please let me know if I overstep :) |
Codecov Report
@@ Coverage Diff @@
## main #1080 +/- ##
==========================================
+ Coverage 84.80% 86.11% +1.30%
==========================================
Files 135 136 +1
Lines 3298 3299 +1
==========================================
+ Hits 2797 2841 +44
+ Misses 501 458 -43
Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
I can do the same for |
796a0fe
to
967198c
Compare
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.
Nice!
Thanks for this @PeterKneale, these improvements are always appreciated 🙂. We don't mind skipping issues when there isn't a design discussion to be had. |
SnsPolicy.cs
was using regex to parse the source ARN instead of using Amazons suppliedARN.Parse(..)
method.generating
andapplying
the policyapproval test
against the IAM policy generatedARN.Parse(..)
and observed no regressions.