-
Notifications
You must be signed in to change notification settings - Fork 540
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
Oracle DB engine enablement on HCP Vault #2006
Conversation
|
ba36540
to
4a03824
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.
Looks great! Just one minor nit.
@@ -1659,11 +1675,11 @@ func validateDBPluginName(s string) error { | |||
func getSortedPluginPrefixes() ([]string, error) { | |||
var pluginPrefixes []string | |||
for _, d := range dbEngines { | |||
prefix, err := d.PluginPrefix() | |||
prefix, err := d.PluginPrefixes() |
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: should be plural
prefix, err := d.PluginPrefixes() | |
prefixes, err := d.PluginPrefixes() |
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
0eb07b1
to
8bf2e67
Compare
Description
The PR introduces the concept of plugin aliases so that different plugin names on HCP Vault can also be supported. The immediate fix is going to allow our customers to use
vault-plugin-database-oracle
in place oforacle-plugin
while enabling the engine via Vault TFP on a HCP Vault cluster.Checklist
Output from acceptance testing:
Community Note