-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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(secretsmanager): L2 construct for Secret #1686
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.
high quality shit
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.
Raise an issue for creating an environmental context provider for secrets so people can just specify the secret name/ARN without the key. Otherwise the usability of import is questionable
* Returns a SecretString corresponding to this secret, so that the secret value can be referred to from other parts | ||
* of the application (such as an RDS instance's master user password property). | ||
*/ | ||
asSecretString(): SecretString; |
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.
rename to toSecretString
. We use the "asXXX" notation for inversion of control methods and users are not supposed to use them directly.
Context provider suggestion now at #1689 |
Pull Request Checklist
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license.