-
Notifications
You must be signed in to change notification settings - Fork 2.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
adding SES Email Template Crud Policy Template #723
Conversation
Codecov Report
@@ Coverage Diff @@
## develop #723 +/- ##
========================================
Coverage 94.18% 94.18%
========================================
Files 67 67
Lines 2683 2683
Branches 478 478
========================================
Hits 2527 2527
Misses 80 80
Partials 76 76 Continue to review full report at Codecov.
|
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 only blocker is the question on scoping. If the IAM action doesn't support scoping to a specific resource, then this should be fine.
You have a good point! Will add, it makes sense as it’s for SES template operations |
Description of changes:
Add SESEmailTemplateCrudPolicy which grants the user access to:
ses:CreateTemplate
ses:GetTemplate
ses:ListTemplates
ses:UpdateTemplate
ses:DeleteTemplate
ses:TestRenderTemplate
Thank you for taking this into consideration. I would be interested in adding more in the future.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.