terraform-null-label

what

• Fix tags: don't include tags with empty values
• Fix Travis URL in README

why

• Many resources (e.g. Elastic Beanstalk) fail if provided with tags with empty values

references

• closes #42

what

• Make attributes output a list
• Fix race conditions when processing attributes

why

• attributes input is a list, we should keep the same type for the output
• Due to TF limitations, there was a race condition when merging attributes using the calculated delimiter. The delimiter was always taken from the context even if it was provided in var.delimiter, and just for attributes, the other outputs were OK

what

• Change how the final delimiter from the provided context or input variable is calculated

why

Fix the case where a module label is instantiated with a non-default delimiter, and then another label is generated based off the context but uses the default delimiter as the local var takes
precedence.

The only case this actually applies to is the delimiter, which has a default value of '-', however all others changed to make them consistent.

what

• Add new variable that allows for providing a label_order as a list to specify which variables and in what order go into the id output and Name tag.
• The list can include all or none of the a variable names:
  "namespace", "environment", "stage", "name", "attributes"

why

Resolves https://github.com/cloudposse/terraform-null-label/issues/35

The module has a new context variable and output.
The module has a new environment variable.
The module now allows all variables to be optional and follows a set of rules to generate the outputs.

Context allows the variables of one label module to be passed to the next label module.
Allowing you to create one label that has the base set of values, and then creating every extra label
as a derivative of that.

The environment variable can be used with the stage variable or alone.
It was added because in some businesses the term environment is embedded as a "known term" for the separation of resources from development to production, so to keep this module from changing the embedded nomenclature this variable was added with backwards compatibility.

what

• Remove home pages and avatars links

why

• Build-harness does it automatically

what

• Update README
• Fix make targets

why

• Some improvements and fixes
• Use / instead of : in make targets

what

• Add support for list of tag maps

why

• Certain kinds of resources (e.g. AWS AutoScaling groups) need them

what

• Use join+splat pattern in tags

why

• New Terraform versions complain if a resource with count is used in outputs without splat syntax

Terraform will now detect and warn about outputs containing potentially-problematic references to resources with count set where the references does not use the "splat" syntax. This identifies situations where an output may reference a resource with count = 0 even if the count expression does not currently evaluate to 0, allowing the bug to be detected and fixed before the value is later changed to 0 and would thus become an error. This usage will become a fatal error in Terraform 0.12. (#16735)

what

• Use join+splat pattern for outputs using resources with count

why

• New Terraform versions complain if a resource with count is used in outputs without splat syntax

Resource 'null_resource.default' not found for variable 'null_resource.default.triggers.id'

Terraform will now detect and warn about outputs containing potentially-problematic references to resources with count set where the references does not use the "splat" syntax. This identifies situations where an output may reference a resource with count = 0 even if the count expression does not currently evaluate to 0, allowing the bug to be detected and fixed before the value is later changed to 0 and would thus become an error. This usage will become a fatal error in Terraform 0.12. (#16735)

What

• Fix enabled argument default value

Why

• Terraform can't compare bool with string
• It is recommended to avoid boolean values https://www.terraform.io/docs/configuration/variables.html

what

Add enabled variable which can be used to disable any resources within the module

why

If you have resources that are conditionally created and they refer to this module, your plan will always show null-label resources in the plan. As Terraform does not support conditionally including a module, this is the recommend solution

See https://github.com/hashicorp/terraform/issues/12906

what

• Validate terraform code
• Add build status badge

why

• Improve code quality/consistency

demo

depends on

• merge https://github.com/cloudposse/build-harness/pull/34
• drop git checkout from .travis.yml