Terraform module to provision an Elastic MapReduce (EMR) cluster on AWS
security_configuration
variable ) using KMS CMK needs KMS permissions attached to the policies of the service role. This needs to happen before the cluster creation so that cluster can read the certs from s3 & enable at rest encryption using customer specified KMS key.This PR contains the following updates:
Package | Type | Update | Change |
---|---|---|---|
cloudposse/label/null (source) | terraform | minor | 0.19.2 -> 0.24.1 |
v0.24.1
You now have control over the letter case of generated tag names and supplied labels, which means you also have control over the letter case of the ultimate id
.
Labels are the elements you can include in label_order
, namely namespace
, environment
, stage
, name
, and attributes
. For every non-empty label, a corresponding tag name is generated. For namespace
, environment
, stage
, the output is the formatted, normalized input. (By "normalized" we mean that it goes through regex_replace_chars
.), For attributes
, which is a list, each element is normalized, duplicates are removed, and the resulting list is converted to a string by joining the elements with the delimiter
(defaults to hyphen). For name
, which is special, the output is the same as id
, which is the joining of the labels in the order specified by label_order
and separated by delimiter
.
label_key_case
to one of upper
, lower
, or title
, which will result in generated tag
names in the corresponding case: NAME
, name
, or Name
. For backwards compatibility, title
is the defaultlabel_value_case
to one of upper
, lower
, title
, or none
, which will result in output label values in the corresponding case (with none
meaning no case conversion of any kind will be done, though the labels will still be subject to regex_replace_chars
). The case converted labels will show up not just in the module output of the labels themselves, but also in the tag
values and in the id
string.You can look at the test cases in examples/complete
and the expected results in test/src/examples_complete_test.go
to see examples of how this is supposed to work.
One interesting example is that you can create id
s in Pascal case by setting label_value_case = "title"
and delimiter = ""
.
Incorporates and closes #​120
v0.24.0
Incorporates and closes #​120
You now have control over the letter case of generated tag names and supplied labels, which means you also have control over the letter case of the ultimate id
.
Labels are the elements you can include in label_order
, namely namespace
, environment
, stage
, name
, and attributes
. For every non-empty label, a corresponding tag name is generated. For namespace
, environment
, stage
, the output is the formatted, normalized input. (By "normalized" we mean that it goes through regex_replace_chars
.), For attributes
, which is a list, each element is normalized, duplicates are removed, and the resulting list is converted to a string by joining the elements with the delimiter
(defaults to hyphen). For name
, which is special, the output is the same as id
, which is the joining of the labels in the order specified by label_order
and separated by delimiter
.
label_key_case
to one of upper
, lower
, or title
, which will result in generated tag
names in the corresponding case: NAME
, name
, or Name
. For backwards compatibility, title
is the defaultlabel_value_case
to one of upper
, lower
, title
, or none
, which will result in output label values in the corresponding case (with none
meaning no case conversion of any kind will be done, though the labels will still be subject to regex_replace_chars
). The case converted labels will show up not just in the module output of the labels themselves, but also in the tag
values and in the id
string.You can look at the test cases in examples/complete
and the expected results in test/src/examples_complete_test.go
to see examples of how this is supposed to work.
One interesting example is that you can create id
s in Pascal case by setting label_value_case = "title"
and delimiter = ""
.
v0.23.0
null-label
. The canonical context = module.this.context
fails if module.this.context
is an older versioncontext.tf
does not incorporate var.label_key_case
and var.label_value_case
into the module.this
object, preventing those variables from taking effect in the root module's module.this
.With this release, you gain control over the letter case of generated tag names and supplied labels, which means you also have control over the letter case of the ultimate id
.
Labels are the elements you can include in label_order
, namely namespace
, environment
, stage
, name
, and attributes
. For every non-empty label, a corresponding tag name is generated. For namespace
, environment
, stage
, the output is the formatted, normalized input. (By "normalized" we mean that it goes through regex_replace_chars
.), For attributes
, which is a list, each element is normalized, duplicates are removed, and the resulting list is converted to a string by joining the elements with the delimiter
(defaults to hyphen). For name
, which is special, the output is the same as id
, which is the joining of the labels in the order specified by label_order
and separated by delimiter
.
label_key_case
to one of upper
, lower
, or title
, which will result in generated tag
names in the corresponding case: NAME
, name
, or Name
. For backwards compatibility, title
is the defaultlabel_value_case
to one of upper
, lower
, title
, or none
, which will result in output label values in the corresponding case (with none
meaning no case conversion of any kind will be done, though the labels will still be subject to regex_replace_chars
). The case converted labels will show up not just in the module output of the labels themselves, but also in the tag
values and in the id
string.You can look at the test cases in examples/complete
and the expected results in test/src/examples_complete_test.go
to see examples of how this is supposed to work.
One interesting example is that you can create id
s in Pascal case by setting label_value_case = "title"
and delimiter = ""
.
v0.22.1
v0.22.0
Breaking change: This release updates minimum Terraform version requirement to 0.12.26
v0.21.0
v0.20.0
Adds support for Terraform 0..14
(currently in beta2
)
I've currently got it pinned to < 0.14.1
to be conservative. Can update to < 0.15
or similar.
versions.tf
to support terraform 0.14
0.13
. The proposed workaround for that unrelated issue does not work for me at this time.0.14
which is in beta, now.Fixes #​104
This PR contains the following updates:
Package | Type | Update | Change |
---|---|---|---|
cloudposse/route53-cluster-hostname/aws (source) | terraform | minor | 0.7.0 -> 0.12.0 |
v0.12.0
v0.11.0
v0.10.1
v0.10.0
v0.9.0
v0.8.0
make this module v14 compatible