-
Notifications
You must be signed in to change notification settings - Fork 3
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
Release hcp vault-secrets integrations and rotating/dynamic secrets #176
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.
🚢
Flags: cmd.Flags{ | ||
Local: []*cmd.Flag{ | ||
{ | ||
Name: "type", | ||
DisplayValue: "TYPE", | ||
Description: "The type of the integration to read.", | ||
Value: flagvalue.Simple("", &opts.Type), | ||
}, | ||
}, | ||
}, |
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.
Sorry for getting to this review late, but I was curious why we needed the --type
flag to read an integration!
Could all of the providers use the generic read endpoint instead?
Changes proposed in this PR:
This PR encompasses the work for epic https://hashicorp.atlassian.net/browse/VAULT-28135 to gain HCP CLI Parity for Vault Secrets. It includes:
All changes in this PR have already gone through code review to make into this branch. Those PRs are here:

How I've tested this PR:
This PR includes unit tests, and has also been manually tested during a project bug bash
How I expect reviewers to test this PR:
make go/build
Checklist: