Updating example plugin name in Oracle DB examples #1142
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As of Vault v1.9.0 (per commit
30a483088d8e3ed9f659f6072c9ee5f3a6dae90e), Vault's UI does not support custom plugin names. The OracleDB plugin's officially supported name is `vault-plugin-database-oracle'. Using another name will cause Vault's UI to throw a warning to the user, and redirect them to the CLI/API.
This change just updates the plugin name used in the examples for the Oracle Database Secret Engine doc to use the officially support name, so as to reduce confusion for customers who may encounter this warning in the UI.
Please go to the
Previewtab and select the appropriate template: