This repository has been archived by the owner on Jan 25, 2023. It is now read-only.
Releases: hashicorp/terraform-aws-nomad
Releases · hashicorp/terraform-aws-nomad
v0.6.4
v0.6.3
v0.6.2
v0.6.1
Modules affected
- None (only the example Packer template is affected)
Description
- Updated the example Packer template in
nomad-consul.jsonto useclean_resource_nameinstead ofclean_ami_name, as the latter was deprecated in Packer 1.5+.
Special thanks
- Thanks to @kshahar for the PR!
Related links
v0.6.0
Modules affected
install-nomad[BREAKING CHANGES]run-nomad[BREAKING CHANGES]
Description
- We have switched Nomad to using
systemdinstead ofsupervisord, assystemdis now available on all major Linux distros.
Migration guide
- The only API change is that the
run-nomadscript now takes in optional--systemd-stdoutand--systemd-stderrparameters instead of a--log-dirparameter. If you don't specify these params, logs will go tosystemd'sdefault (journal). - You will now need to use
systemdto interact with Nomad on the OS, mainly by usingsystemctl.
Special thanks
- Thanks to @draoncc for the PR!
Related links
v0.5.2
v0.5.1
v0.5.0
Modules affected
nomad-cluster[BACKWARDS INCOMPATIBLE]nomad-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.