upstream/vault
1
0
Fork 0
mirror of https://github.com/hashicorp/vault.git synced 2026-02-03 20:40:45 -05:00
Code Issues Projects Releases Packages Wiki Activity Actions 11

adjustemnt of options order (#12804)

Browse source 
Co-authored-by: tograla <tograla@gmail.com>
This commit is contained in:
Tom 2021-12-18 01:22:52 +01:00 committed by GitHub
parent 0a7941a9a8
commit e0c79e367d
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
website/content/docs/enterprise/license/autoloading.mdx
View file

@ -12,12 +12,12 @@ As of Vault 1.8 those options still exist but are deprecated, and the recommende
mechanism for managing licenses is called License Autoloading. New clusters are
required to use the autoloading method.
License Autoloading can be done using one of these mechanisms, in increasing order
License Autoloading can be done using one of these mechanisms, in decreasing order
of priority (i.e. `VAULT_LICENSE` takes precedence over `VAULT_LICENSE_PATH`, which
takes precedence over `license_path` in config.)
* [license_path in config](/docs/configuration#license_path)
* [VAULT_LICENSE_PATH environment variable](/docs/commands#vault_license_path)
* [VAULT_LICENSE environment variable](/docs/commands#vault_license)
* [VAULT_LICENSE_PATH environment variable](/docs/commands#vault_license_path)
* [license_path in config](/docs/configuration#license_path)
Nodes within a cluster should be consistently licensed. All nodes in a cluster
should use autoloading, or none should. If autoloading is used, all nodes should