puppet-vault | Puppet module to manage Vault | Identity Management library

user: Customise the user vault runs as, will also create the user unless manage_user is false. manage_user: Whether or not the module should create the user. group: Customise the group vault runs as, will also create the user unless manage_group is false. manage_group: Whether or not the module should create the group. bin_dir: Directory the vault executable will be installed in. config_dir: Directory the vault configuration will be kept in. config_mode: Mode of the configuration file (config.json). Defaults to '0750'. purge_config_dir: Whether the config_dir should be purged before installing the generated config. install_method: Supports the values repo or archive. See Installation parameters. service_name: Customise the name of the system service. service_enable: Tell the OS to enable or disable the service at system startup. service_ensure: Tell the OS whether the service should be running or stopped. service_provider: Customise the name of the system service provider; this also controls the init configuration files that are installed. service_options: Extra argument to pass to vault server, as per: vault server --help. num_procs: Sets the GOMAXPROCS environment variable, to determine how many CPUs Vault can use. The official Vault Terraform install.sh script sets this to the output of nprocs, with the comment, "Make sure to use all our CPUs, because Vault can block a scheduler thread". Default: number of CPUs on the system, retrieved from the processorcount fact. manage_storage_dir: When using the file storage, this boolean determines whether or not the path (as specified in the ['file']['path'] section of the storage config) is created, and the owner and group set to the vault user. Default: false. manage_service_file: Manages the service file regardless of the defaults. Default: See Installation parameters. manage_config_file: Manages the configuration file. When set to false, config.json will not be generated. manag_storage_dir is ignored. Default: true.
user: Customise the user vault runs as, will also create the user unless manage_user is false.
manage_user: Whether or not the module should create the user.
group: Customise the group vault runs as, will also create the user unless manage_group is false.
manage_group: Whether or not the module should create the group.
bin_dir: Directory the vault executable will be installed in.
config_dir: Directory the vault configuration will be kept in.
config_mode: Mode of the configuration file (config.json). Defaults to '0750'
purge_config_dir: Whether the config_dir should be purged before installing the generated config.
install_method: Supports the values repo or archive. See Installation parameters.
service_name: Customise the name of the system service
service_enable: Tell the OS to enable or disable the service at system startup
service_ensure: Tell the OS whether the service should be running or stopped
service_provider: Customise the name of the system service provider; this also controls the init configuration files that are installed.
service_options: Extra argument to pass to vault server, as per: vault server --help
num_procs: Sets the GOMAXPROCS environment variable, to determine how many CPUs Vault can use. The official Vault Terraform install.sh script sets this to the output of nprocs, with the comment, "Make sure to use all our CPUs, because Vault can block a scheduler thread". Default: number of CPUs on the system, retrieved from the processorcount fact.
manage_storage_dir: When using the file storage, this boolean determines whether or not the path (as specified in the ['file']['path'] section of the storage config) is created, and the owner and group set to the vault user. Default: false
manage_service_file: Manages the service file regardless of the defaults. Default: See Installation parameters.
manage_config_file: Manages the configuration file. When set to false, config.json will not be generated. manag_storage_dir is ignored. Default: true
When repo is set the module will attempt to install a package corresponding with the value of package_name. When archive the module will attempt to download and extract a zip file from the download_url, the extracted file will be placed in the bin_dir folder. The module will not manage any required packages to un-archive, e.g. unzip. See puppet-archive setup documentation for more details.
package_name: Name of the package to install, default: vault
package_ensure: Desired state of the package, default: installed
bin_dir: Set to the path where the package will install the Vault binary, this is necessary to correctly manage the disable_mlock option.
manage_service_file: Will manage the service file in case it's not included in the package, default: false
manage_file_capabilities: Will manage file capabilities of the vault binary. default: false
download_url: Optional manual URL to download the vault zip distribution from. You can specify a local file on the server with a fully qualified pathname, or use http, https, ftp or s3 based URI's. default: undef
download_url_base: This is the base URL for the hashicorp releases. If no manual download_url is specified, the module will download from hashicorp. default: https://releases.hashicorp.com/vault/
download_extension: The extension of the vault download when using hashicorp releases. default: zip
download_dir: Path to download the zip file to, default: /tmp
manage_download_dir: Boolean, whether or not to create the download directory, default: false
download_filename: Filename to (temporarily) save the downloaded zip file, default: vault.zip
version: The Version of vault to download. default: 1.4.2
manage_service_file: Will manage the service file. default: true
manage_file_capabilities: Will manage file capabilities of the vault binary. default: true