This repository has been archived by the owner on Jan 25, 2023. It is now read-only.
Releases: hashicorp/terraform-aws-consul
Releases · hashicorp/terraform-aws-consul
v0.7.5
v0.7.4
v0.7.3
Modules affected
run-consul
Description
- After #146 , systemd now waits for consul's notification of having joined the cluster before signaling that the service is alive. This however may occasionally result in larger waiting times and intermittent timeout failures. As a remedy, this release raises the systemd service timeout from 90s (the default) to a more reasonable 300s.
Related links
v0.7.2
Modules affected
install-consulsetup-systemd-resolved[NEW MODULE]
Description
- This repo now works with Ubuntu 18.04.
- Added a new module called
setup-systemd-resolvedthat can be used on Ubuntu 18.04 instead ofdnsmasqfor configuring systemd-resolved to forward requests for a specific domain to Consul.
Special thanks
- Thank you to @sharmaanshul21 for the PR!
Related links
v0.7.1
Modules affected
run-consul
Description
- Add
Type=notifytosystemdconfig for Consul so that any othersystemdservices that depend on Consul (e.g., viaRequires=consul.service) will be started after Consul is fully up and running, rather than as soon as the Consul task is started.
Special thanks
- Thanks to @gilesvangruisen for the fix!
Related links
v0.7.0
Modules affected
consul-cluster[BACKWARDS INCOMPATIBLE]consul-iam-policies[BACKWARDS INCOMPATIBLE]consul-client-security-group-rules[BACKWARDS INCOMPATIBLE]consul-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
v0.6.1
v0.6.0
Modules affected
install-consul[BREAKING CHANGE]run-consul[BREAKING CHANGE]
Description
- We have switched this Consul repo to use systemd instead of supervisord as a process supervisor, as systemd is now available on most major Linux distributions by default. You will need to build a new AMI with the new version of
install-consuland run it with the new version ofrun-consulfor this change to take affect. Also, take note that therun-consulscript no longer exposes a--log-dirparameter; this has been replaced by--systemd-stdoutand--systemd-stderrparams (the default is to write logs tojournalctl).
Related links
v0.5.0
Modules affected
consul-cluster[BREAKING CHANGE]
Description
- Work around for a Terraform limitation that would cause errors if the
allowed_ssh_security_group_countparameter referenced any resources, as theconsul-clustermodule was using that variable in acountparameter. The only available option is that you now MUST pass in a redundant variable calledallowed_ssh_security_group_countthat specifies the number of security group IDs inallowed_ssh_security_group_count.