-
Notifications
You must be signed in to change notification settings - Fork 47
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
Rotating secret resource implementation #1101
Rotating secret resource implementation #1101
Conversation
918507b
to
f45ec8c
Compare
* lint * lint * tidy imports * rename
2e50904
to
b33d732
Compare
…otating-secret-resource
…otating-secret-resource
…otating-secret-resource
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.
LGTM
- `integration_name` (String) The Vault Secrets integration name with the capability to manage the secret's lifecycle. | ||
- `name` (String) The Vault Secrets secret name. | ||
- `rotation_policy_name` (String) Name of the rotation policy that governs the rotation of the secret. | ||
- `secret_provider` (String) The third party platform the dynamic credentials give access to. One of `aws` or `gcp`. |
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.
nit: could drop "dynamic" here since these fields are shared between both capabilities
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.
My bad I missed that comment. I'll fix it in a follow-up.
dfd1361
into
vault-29950/dynamic-secret-resource
🛠️ Description
Added the Vault Secrets rotating secret resource.
Using the interfaces and abstractions introduced in #1097
🏗️ Acceptance tests
Output from acceptance testing: