feat(secretsmanager): add grantUpdate method#8600
Conversation
Sure, no problem. I wasn't sure which was the better route to take, as I could see use cases for both. I'll push up a revision soon. |
|
I've updated as requested. Feel free to review when able. |
|
Thank you for contributing! Your pull request will be updated from master 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 master and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
This method does not exist. This mention in the docs is leftover from an abandoned approach in #8600 and should have been reverted. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
This method does not exist. This mention in the docs is leftover from an abandoned approach in aws#8600 and should have been reverted. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
This creates the
grantUpdatemethod to give aniam.IGrantablethe ability to update a secret in Secrets Manager.I opted to move it out from the
grantWritemethod, as there may be cases where we want something to write an initial value, but not change it later on. This decision could be reversed if it seems too granular or too much of an edge-case.Closes #8491
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license