Skip to content
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.

Sign up for GitHub

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

Jump to bottom

adjustment of order of options #12804

Merged
merged 1 commit into from
Dec 18, 2021
Merged

adjustment of order of options #12804

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions website/content/docs/enterprise/license/autoloading.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down