Terraform module for deploying Atlantis as an ECS Task
use_alb_security_group flag to pass along to the ecs-web-app module so that a security group ingress rule will be added to the service for the ALB.https://github.com/cloudposse/terraform-aws-ecs-web-app/pull/113 <-- That PR broke this module.
Error: Output refers to sensitive values
on outputs.tf line 46:
46: output "container_definition_json" {
Expressions used in outputs can only refer to sensitive values if the
sensitive attribute is true.
Error: Output refers to sensitive values
on outputs.tf line 51:
51: output "container_definition_json_map" {
Expressions used in outputs can only refer to sensitive values if the
sensitive attribute is true.
This PR contains the following updates:
| Package | Type | Update | Change |
|---|---|---|---|
| cloudposse/ecs-web-app/aws (source) | terraform | minor | 0.53.1 -> 0.54.0 |
v0.54.0v0.53.7This PR contains the following updates:
| Package | Type | Update | Change |
|---|---|---|---|
| cloudposse/ecs-cloudwatch-sns-alarms/aws (source) | terraform | patch | 0.12.0 -> 0.12.1 |
This PR contains the following updates:
| Package | Type | Update | Change |
|---|---|---|---|
| cloudposse/label/null (source) | terraform | minor | 0.22.1 -> 0.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 ids in Pascal case by setting label_value_case = "title" and delimiter = "".
Incorporates and closes #&#​8203;120
Incorporates and closes #&#​8203;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 ids in Pascal case by setting label_value_case = "title" and delimiter = "".
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 ids in Pascal case by setting label_value_case = "title" and delimiter = "".
v0.53.6This PR contains the following updates:
| Package | Type | Update | Change |
|---|---|---|---|
| cloudposse/ecs-container-definition/aws (source) | terraform | minor | 0.47.0 -> 0.49.2 |
v0.53.5This PR contains the following updates:
| Package | Type | Update | Change |
|---|---|---|---|
| cloudposse/alb-ingress/aws (source) | terraform | minor | 0.18.0 -> 0.20.0 |
v0.53.4This PR contains the following updates:
| Package | Type | Update | Change |
|---|---|---|---|
| cloudposse/ecs-cloudwatch-sns-alarms/aws (source) | terraform | minor | 0.11.1 -> 0.12.0 |
v0.53.3This PR contains the following updates:
| Package | Type | Update | Change |
|---|---|---|---|
| cloudposse/ecs-alb-service-task/aws (source) | terraform | minor | 0.44.1 -> 0.47.0 |
This PR contains the following updates:
| Package | Type | Update | Change |
|---|---|---|---|
| cloudposse/label/null (source) | terraform | minor | 0.22.1 -> 0.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 ids in Pascal case by setting label_value_case = "title" and delimiter = "".
Incorporates and closes #&#​8203;120
Incorporates and closes #&#​8203;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 ids in Pascal case by setting label_value_case = "title" and delimiter = "".
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 ids in Pascal case by setting label_value_case = "title" and delimiter = "".
v0.53.2This PR contains the following updates:
| Package | Type | Update | Change |
|---|---|---|---|
| cloudposse/ecr/aws (source) | terraform | patch | 0.32.1 -> 0.32.2 |
This PR contains the following updates:
| Package | Type | Update | Change |
|---|---|---|---|
| cloudposse/ecs-web-app/aws (source) | terraform | patch | 0.53.0 -> 0.53.1 |
v0.53.1Restore correct ordering of attributes in IDs.
context.tf and dependent modules to be compatible with Null Label v0.24.1Supersedes and replaces #28 Supersedes and replaces #29
github_webhooks_anonymous no longer supported by GitHub and causing https://github.com/cloudposse/terraform-aws-ecs-web-app/issues/63
Note that this version is affected by a bug that puts attributes provided by the caller in the wrong place in some identifiers. If you are not providing attributes, it is not an issue, but if you are, please upgrade instead to v0.21.0 which has the correct order. Otherwise you may find resources being unnecessarily deleted.
github_anonymous
github_anonymous
This PR contains the following updates:
| Package | Type | Update | Change |
|---|---|---|---|
| cloudposse/ecs-web-app/aws (source) | terraform | patch | 0.48.1 -> 0.48.2 |
v0.48.2This PR contains the following updates:
| Package | Type | Update | Change |
|---|---|---|---|
| cloudposse/alb-ingress/aws (source) | terraform | minor | 0.16.1 -> 0.17.0 |
Guard the creation of the condition block on the length of the optional listener_http_header_conditions.
Fixes #​42
Fixes #​42