0.6.0: Terraform 0.12+ syntax update (#25)

This change makes the module more compatible with Terraform 0.12+ and makes it fully compatible with Terraform 0.15.

More specifically, it gets rid of the Invalid quoted type constraints deprecation errors.

Unfortunately, this syntax change makes the module incompatible with Terraform 0.11 and below. The minimum version is reflected in the versions.tf file along with required module version pinning.

0.5.0 Change the block syntax to the argument syntax (with =) to work with Terraform 0.12

what

• Change the block syntax to the argument syntax (with =) to work with Terraform 0.12

why

• See here for details. The bit that is most relevant to this pull request is the paragraph that reads:

Due to the design of the configuration language decoder in Terraform v0.11 and earlier, it was in many cases possible to interchange the argument syntax (with =) and the block syntax (with just braces) when dealing with map arguments vs. nested blocks. However, this led to some subtle bugs and limitations, so Terraform v0.12 now requires consistent usage of argument syntax for arguments and nested block syntax for nested blocks.

Regenerate README.md

what

• Regenerate README.md

why

• Previous version of build-harness has some typos

Migrate to README.yaml format

what

• Add README.yaml

why

• Standardize README

Fix. Ansible provisioner shows pending changes each time. Make `arguments` and `envs` variables not required

What

• Ansible provisioner shows pending changes each time
• Make arguments and envs variables not required #14

Why

• Module shouldn't rerun playbook if nothing has changed
• Keep everything DRY

Rename Repo

what

• Rename repo

why

• To conform to community standard: https://www.terraform.io/docs/registry/modules/publish.html

0.3.0

Do not run ansible if playbook empty (#5)