v0.13.9

Modules affected

• private-tls-cert
• vault-cluster
• vault-elb

Description

• Update this repo to work with AWS Provider 3.x. This includes defaulting subnet_ids and availability_zones to null instead of an empty list, as AWS Provider 3.x only allows one or the other of these parameters to be set. Note that if you are using terraform-aws-consul, we recommend updating to at least version v0.7.7, which has similar fixes.

Related links

• #195

v0.13.8

Modules affected

• run-vault

Description

• You can now override the data directory for Vault using the --data-dir argument in run-vault.

Special thanks

• Thank you to @andrew-womeldorf for the contribution!

Related links

• #203

v0.13.7

Modules affected

• run-vault

Description

• Fix a typo in the argument parsing of the run-vault script. The script now correctly looks for a --agent-ca-cert-file argument instead of --agent-ca-cert_file.

Special thanks

• Thank you to @codegabru for the fix!

Related links

• #199

v0.13.6

Modules affected

• run-vault
• vault-cluster

Description

• You can now use Vault with DynamoDB as a backend by specifying the --enable-dynamo-backend, --dynamo-region, and --dynamo--table parameters in run-vault and the enable_dynamo_backend, dynamo_table_name, and dynamo_table_region in vault-cluster.

Special thanks

• Thank you to @stephencoe for the contribution!

Related links

• #181

v0.13.5

Modules affected

• (none)

Description

• Updated the example Packer template to use the clean_resource_name function instead of the deprecated clean_ami_name function.

Special thanks

• Thanks to @JulianRunnels for the PR!

Related links

• #180

v0.13.4

Modules affected

• (none)

Description

• Fix a few broken links in the READMEs

Related links

• #178

v0.13.3

Modules affected

• run-vault

Description

• Adds a --s3-bucket-path option for the run-vault script. It is useful when you configure S3 as a storage backend and want to store vault data at a specific path in the S3 bucket.

Related links

• #160

Special thanks

Thanks, @adriananeci, for this contribution!

v0.13.2

Modules affected

• install-vault

Description

• This repo now works with Ubuntu 18.04. Updates install-vault for Ubuntu 18.04 compatibility and updates tests and examples.

Related links

• #159

v0.13.1

Modules affected

• vault-cluster

Description

• Fixed the syntax in the for_each loop used to add tags to the ASG from the cluster_extra_tags argument.

Special thanks

Thanks @rjshep for the PR!

Related links

• #157

v0.13.0

Modules affected

• private-tls-cert [BACKWARDS INCOMPATIBLE]
• vault-cluster [BACKWARDS INCOMPATIBLE]
• vault-elb [BACKWARDS INCOMPATIBLE]
• vault-security-group-rules [BACKWARDS INCOMPATIBLE]
• vault-security-group-rules [BACKWARDS INCOMPATIBLE]

Description

All the modules are now terraform 0.12.0 compatible. Note that this means the modules are no longer compatible with terraform 0.11 and under. Starting this release, you must use terraform 0.12.0 or greater to use this module.

All the module variables have been updated to use concrete types based on the new type system introduced in terraform 0.12.0. You can learn more about the types in the official documentation.

Note that as part of this, we switched to using null to indicate unset values when passing them through to resources. If you were previously using a 0 value ("" for strings and 0 for numbers), review the module variables.tf file to double check if the 0 value has been converted to a null.

Related links

• #154