Releases: hashicorp/terraform-aws-vault
Releases · hashicorp/terraform-aws-vault
v0.10.1
4cdae98: Fix the AWS account we use for publishing the public example AMIs.
v0.10.0
#86:
- BACKWARDS INCOMPATIBLE CHANGE: The
lb_tags
parameter in the vault-elb
module has been renamed to load_balancer_tags
.
- You can now set custom security group tags in the
vault-elb
module using the new security_group_tags
parameter.
- You can now set custom security group tags in the
vault-cluster
module using the new security_group_tags
parameter.
- You can now set custom S3 bucket tags in the
vault-cluster
module using the new s3_bucket_tags
parameter.
v0.9.3
#83: You can now specify a custom port number to use for Vault health checks in the vault-elb
module using the optional param health_check_port
.
v0.9.2
#81: You can now set custom tags for the Vault ELB using the optional parameter lb_tags
.
v0.9.1
#80: Fix aws
install with yum
to use the proper package name.
v0.9.0
#78: If you're using Vault 0.10.0 or above, the UI will now be enabled by default.
v0.8.0
#72: The Vault user is now marked as a system user.
v0.7.2
#70: Fix typo in the docs where we listed the parameter name as --s3-backend-enable
but it should actually be --enable-s3-backend
.
v0.7.1
#69: Vault will now exit with an error if cluster_addr == api_addr
, so default api_addr
to a different value, and make it configurable via a new --api-addr
parameter.
v0.7.0
#68:
BACKWARDS INCOMPATIBLE CHANGE
The vault-cluster
module now requires a new parameter called allowed_inbound_security_group_count
to be set. This is unfortunately required to work around a limitation in Terraform with the count
parameter.