Docs: Updated plugin versioning usage docs for pinned versions (#25607)

This commit is contained in:
Tom Proctor
2024-03-14 17:29:21 +00:00
committed by GitHub
parent 9523667a6a
commit 6482672d12
3 changed files with 49 additions and 32 deletions

View File

@@ -57,12 +57,19 @@ registering an external plugin. Multiple versions of a plugin can be registered
in the catalog simultaneously, and a version can be selected when mounting a
plugin or tuning an existing mount in-place.
Alternatively, users can select pinned versions to enforce uniform cluster-wide
version selection. When a pinned version is in effect, versions cannot be
specified in mount config, and existing mounts that specify a version will
ignore the locally configured version. See the
[pinned versions](/vault/api-docs/system/plugins-pins) API for more details.
If no version is specified when creating a new mount, the following precedence is used
for any available plugins whose type and name match:
* The plugin registered with no version
* The plugin with the most recent semantic version among any registered versions
* The plugin built into Vault
1. The pinned version of the plugin, if any exists.
1. The plugin registered with no version.
1. The plugin with the most recent semantic version among any registered versions.
1. The plugin built into Vault.
### Built-In versions