-
Notifications
You must be signed in to change notification settings - Fork 9.2k
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
New resource aws_secretsmanager_resource_policy #14618
Labels
enhancement
Requests to existing resources that expand the functionality or scope.
service/secretsmanager
Issues and PRs that pertain to the secretsmanager service.
Comments
ribeiroh
added
the
enhancement
Requests to existing resources that expand the functionality or scope.
label
Aug 13, 2020
ghost
added
the
service/secretsmanager
Issues and PRs that pertain to the secretsmanager service.
label
Aug 13, 2020
github-actions
bot
added
the
needs-triage
Waiting for first response or review from a maintainer.
label
Aug 13, 2020
will be added in #14468 ill add |
DrFaust92
removed
the
needs-triage
Waiting for first response or review from a maintainer.
label
Aug 13, 2020
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks! |
ghost
locked as resolved and limited conversation to collaborators
Dec 3, 2020
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
enhancement
Requests to existing resources that expand the functionality or scope.
service/secretsmanager
Issues and PRs that pertain to the secretsmanager service.
Community Note
Description
It would be interesting to have the ability to decouple the creation of a Secrets Manager from the definition of its resource policy. This is useful if you need to "inject" the policy from a separate module, especially when that happens after the secret already exists.
New or Affected Resource(s)
Potential Terraform Configuration
References
The text was updated successfully, but these errors were encountered: