Manage Hashicorp Vault with Salt.
This formula contains several custom modules. The vault
modules should be backwards-compatible with the ones currently found in Salt and might become available there at some point. For details, see #62684 and #63314.
Table of Contents
See the full SaltStack Formulas installation and usage instructions.
If you are interested in writing or contributing to formulas, please pay attention to the Writing Formula Section.
If you want to use this formula, please pay attention to the FORMULA
file and/or git tag
,
which contains the currently released version. This formula is versioned according to Semantic Versioning.
See Formula Versioning Section for more details.
If you need (non-default) configuration, please refer to:
- how to configure the formula with map.jinja
- the
pillar.example
file - the Special notes section
An example pillar is provided, please see pillar.example. Note that you do not need to specify everything by pillar. Often, it's much easier and less resource-heavy to use the parameters/<grain>/<value>.yaml
files for non-sensitive settings. The underlying logic is explained in map.jinja.
The following states are found in this formula:
vault
vault.package
vault.package.repo
vault.config
vault.config.file
vault.config.system
vault.cert
vault.service
vault.initialize
vault.database
vault.leases
vault.pki
vault.pki.base
vault.pki.ca
vault.pki.roles
vault.plugins
vault.secrets
vault.ssh
vault.ssh.ca
vault.ssh.roles
vault.clean
vault.package.clean
vault.package.repo.clean
vault.config.clean
vault.cert.clean
vault.service.clean
vault.database.clean
vault.leases.clean
vault.pki.clean
vault.plugins.clean
vault.secrets.clean
vault.ssh.clean
Meta-state.
This installs Vault,
manages the Vault and system swap configuration
and then starts the Vault service.
Also ensures the cluster is initialized if vault:init
is not false.
Installs Vault (+ necessary service unit overrides) only.
This state will install the configured vault repository. This works for apt/dnf/yum/zypper-based distributions only by default.
Ensures the system and Vault is configured as specified.
Manages the Vault configuration. Has a dependency on vault.package.
Manages system settings required for Vault: disable swap. Includes vault.package.
Generates a TLS certificate + key for Vault. Depends on vault.package.
Starts the vault service and enables it at boot time. Has a dependency on vault.config.
Ensures a running Vault cluster has been initialized. Will output key shares and initial root token to file paths. Ensure you provide the correct GPG keys in order to encrypt the output.
Manages database connections and their roles.
Manages cached leases and associated beacons.
Manages PKI backend URL endpoints.
Manages intermediate CAs on PKI backend mounts.
Manages present and absent roles on configured PKI mounts.
Manages present/absent custom plugins. For present ones, pulls binaries from a URI and registers them.
Manages Vault KV secrets.
Manages SSH secret backend roles and, if required, CAs.
Meta-state.
Undoes everything performed in the vault
meta-state
in reverse order, i.e.
stops the service,
removes the configuration file and then
uninstalls the package.
Removes Vault and service unit overrides. Has a dependency on vault.config.clean.
This state will remove the configured vault repository. This works for apt/dnf/yum/zypper-based distributions only by default.
Removes the Vault configuration only and has a dependency on vault.service.clean.
Removes generated Vault TLS certificate + key. Depends on vault.service.clean.
Stops the vault service and disables it at boot time.
Removes managed database connections and their roles.
Requires remove_all_data_for_sure
to be set to true
to prevent accidental damage.
Removes managed leases.
Does nothing at the moment.
Removes managed secrets.
Removes managed SSH roles and SSH CAs.
For CAs, requires remove_all_data_for_sure
to be set to true
to prevent accidental damage.
Commit message formatting is significant!
Please see How to contribute for more details.
pre-commit is configured for this formula, which you may optionally use to ease the steps involved in submitting your changes.
First install the pre-commit
package manager using the appropriate method, then run bin/install-hooks
and
now pre-commit
will run automatically on each git commit
.
$ bin/install-hooks pre-commit installed at .git/hooks/pre-commit pre-commit installed at .git/hooks/commit-msg
There is a script that semi-autodocuments available states: bin/slsdoc
.
If a .sls
file begins with a Jinja comment, it will dump that into the docs. It can be configured differently depending on the formula. See the script source code for details currently.
This means if you feel a state should be documented, make sure to write a comment explaining it.