-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Add deprecation status to list commands #16849
Conversation
@tomhjp brought up a good point out of band. This lookup is happening client-side, so will not reflect the state as it exists in the server. Going to update the deprecation lookups to happen server-side and do a bit more testing around this. |
I totally missed that. Thanks for the update! |
895540d
to
aebc75e
Compare
@tomhjp the I have the changes to the backend handling, but Should I go ahead and add both version and deprecation status as a part of this PR, or are you comfortable with the following for now:
This is just my inclination for the sake of getting the PR merged, but more than happy to add version information to |
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.
I'm fine with a phased approach 👍
vault/mount.go
Outdated
if c.builtinRegistry.Contains(entry.Type, consts.PluginTypeSecrets) { | ||
pluginTypes = append(pluginTypes, consts.PluginTypeSecrets) | ||
} | ||
|
||
if c.builtinRegistry.Contains(entry.Type, consts.PluginTypeDatabase) { | ||
pluginTypes = append(pluginTypes, consts.PluginTypeDatabase) | ||
} |
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.
These seem like unsafe assumptions to me. e.g. If we are processing an externally registered k8s auth plugin, it will get labelled as a secrets engine because there is also a built-in kubernetes secret engine
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.
Agreed, and this actually makes for a good test case. I'll see about adding that to the PR.
8023fec
to
fe223f2
Compare
fe223f2
to
cf8ab35
Compare
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
9bbbdf4
to
dd67781
Compare
This PR adds the ability to query builtin deprecation status by adding a new column to the auth, secrets, and plugins lists. This will be further augmented in a follow-up PR which will add the status information to API endpoints as well.