Releases: cloudposse/terraform-aws-ecs-cloudwatch-sns-alarms
v0.13.1
🚀 Enhancements
fix: Memory High description typo @pazaan (#51)
`Hight` -> `High`what
Fix typo in alarm description
🤖 Automatic Updates
Contributors
Assets 2
v0.13.0
Update upstream module versions in examples/complete @joe-niland (#41)
what
- bump upstream module versions
- bump min provider & tf versions in line with deps
why
- Fix errors in Terratest related to outdated provider versions
references
- none
Sync github @max-lobur (#36)
Sync github from the template
Use cloudposse/template for arm support @nitrocode (#34)
what
- Use cloudposse/template for arm support
why
- The new cloudposse/template provider has a darwin arm binary for M1 laptops
references
git.io->cloudposse.tools update @dylanbannon (#29)
what and why
Change all references to git.io/build-harness into cloudposse.tools/build-harness, since git.io redirects will stop working on April 29th, 2022.
References
- DEV-143
context.tf updated to v0.24.1, minimum required Terraform version bumped to 0.13.0 when needed, readme updated @maximmi (#25)
what
- update context.tf to v0.24.1
- minimum required Terraform version bumped to 0.13.0
- readme updated, Bridgecrew compliance badges added
why
- It allows for setting the letter case of tag names and labels, back compatibility with context v0.22.0 and below
- we have dropped support for Terraform 0.12
- To be able see and fix the recommendations from Bridgecrew so we can position our modules as standards compliant
minimum required Terraform version bumped to 0.13.0, context.tf updated, readme updated @maximmi (#24)
what
- update context.tf to v0.23.0
- minimum required Terraform version bumped to 0.13.0
- readme updated, Bridgecrew compliance badges added
why
- It allows for setting the letter case of tag names and labels
- we have dropped support for Terraform 0.12
- To be able see and fix the recommendations from Bridgecrew so we can position our modules as standards compliant
readme updated, BC checks fixed for example/test module @maximmi (#21)
what
- BridgeCrew compliance checks fix
- readme updated
why
- To be able to position our modules as standards compliant
- To comply BridgeCrew check
references
Terraform 0.14 upgrade @maximmi (#19)
what
- Upgrade to support Terraform 0.14 and bring up to current Cloud Posse standard
why
- Support Terraform 0.14
Use context.tf and latest null-label module @okgolove (#17)
what
- Use context feature and latest null-label module
why
- The module should have context feature due to it is used by another modules like ecs-web-app
Update provider pinning @jamengual (#16)
what
- upgrade aws provider to > 3.1
why
- Updating base modules
[AUTOMATED] Update terraform-null-label versions to support Terraform 0.13 @Gowiem (#14)
What
- Updates terraform-null-label versions 0.14.1, 0.15.0, and 0.16.0 to version 0.17.0
- This is an automated commit and pull request created by Microplane. More information here.
Why
- This module and the mentioned previous versions are used extensively across the large majority of Cloud Posse's Terraform Modules. They're currently holding back support for Terraform v0.13. Doing this upgrade in mass will alleviate the pain in our efforts to support Terraform v0.13
[AUTOMATED] Update Version Pinning for Terraform to support 0.13 @Gowiem (#12)
What
- Update Version Pinning for Terraform to support 0.13
Why
- This is a relatively minor update that the CloudPosse module already likely supports.
- This allows module consumers to not individually update our Terraform module to support Terraform 0.13.
Updates to ChatOps - Automated commit @Gowiem (#11)
What
- Adds chatops commands
- '/test all'
- '/test bats'
- '/test readme'
- '/test terratest'
- Drops codefresh
- Drops slash-command-dispatch
- Removes codefresh badge
- Rebuilds README
Why
- Change over from codefresh to GH Actions
- Facilitate testing of PRs from forks
Convert to TF 0.12. Add tests. Add Codefresh test pipeline @aknysh (#10)
what
- Port module to Terraform 0.12
- Pin all providers
- Add example for testing
- Add
batsandterratestfor the example - Add Codefresh badge to point to the test pipeline in
terraform-modulesproject - Update README
why
- Module currently does not work with 0.12. Much easier syntax
- Better regression control
- Automatically test the example on every commit and pull request
- Provision resources on AWS in the test account and check the outputs for the correct values
terraform-modulesproject contains pipelines for all terraform modules
related
- Closes #9
test
Apply complete! Resources: 34 added, 0 changed, 0 destroyed.
Outputs:
container_definition_json = [{"command":null,"cpu":256,"dependsOn":null,"dnsServers":null,"dockerLabels":null,"entryPoint":null,"environment":[{"name":"false_boolean_var","value":"false"},{"name":"integer_var","value":"42"},{"name":"string_var","value":"I am a string"},{"name":"true_boolean_var","value":"true"}],"essential":true,"firelensConfiguration":null,"healthCheck":null,"image":"cloudposse/geodesic","links":null,"logConfiguration":null,"memory":256,"memoryReservation":128,"mountPoints":null,"name":"geodesic","portMappings":[{"containerPort":80,"hostPort":80,"protocol":"tcp"},{"containerPort":443,"hostPort":443,"protocol":"udp"}],"privileged":null,"readonlyRootFilesystem":false,"repositoryCredentials":null,"secrets":null,"startTimeout":30,"stopTimeout":30,"systemControls":null,"ulimits":null,"user":null,"volumesFrom":null,"workingDirectory":null}]
container_definition_json_map = {"command":null,"cpu":256,"dependsOn":null,"dnsServers":null,"dockerLabels":null,"entryPoint":null,"environment":[{"name":"false_boolean_var","value":"false"},{"name":"integer_var","value":"42"},{"name":"string_var","value":"I am a string"},{"name":"true_boolean_var","value":"true"}],"essential":true,"firelensConfiguration":null,"healthCheck":null,"image":"cloudposse/geodesic","links":null,"logConfiguration":null,"memory":256,"memoryReservation":128,"mountPoints":null,"name":"geodesic","portMappings":[{"containerPort":80,"hostPort":80,"protocol":"tcp"},{"containerPort":443,"hostPort":443,"protocol":"udp"}],"privileged":null,"readonlyRootFilesystem":false,"repositoryCredentials":null,"secrets":null,"startTimeout":30,"stopTimeout":30,"systemControls":null,"ulimits":null,"user":null,"volumesFrom":null,"workingDirectory":null}
cpu_utilization_high_cloudwatch_metric_alarm_arn = arn:aws:cloudwatch:us-east-2:126450723953:alarm:eg-test-ecs-cloudwatch-sns-alarms-cpu-utilization-high
cpu_utilization_high_cloudwatch_metric_alarm_id = eg-test-ecs-cloudwatch-sns-alarms-cpu-utilization-high
cpu_utilization_low_cloudwatch_metric_alarm_arn = arn:aws:cloudwatch:us-east-2:126450723953:alarm:eg-test-ecs-cloudwatch-sns-alarms-cpu-utilization-low
cpu_utilization_low_cloudwatch_metric_alarm_id = eg-test-ecs-cloudwatch-sns-alarms-cpu-utilization-low
ecs_cluster_arn = arn:aws:ecs:us-east-2:126450723953:cluster/eg-test-ecs-cloudwatch-sns-alarms
ecs_cluster_id = arn:aws:ecs:us-east-2:126450723953:cluster/eg-test-ecs-cloudwatch-sns-alarms
ecs_exec_role_policy_id = eg-test-ecs-cloudwatch-sns-alarms-exec:eg-test-ecs-cloudwatch-sns-alarms-exec
ecs_exec_role_policy_name = eg-test-ecs-cloudwatch-sns-alarms-exec
memory_utilization_high_cloudwatch_metric_alarm_arn = arn:aws:cloudwatch:us-east-2:126450723953:alarm:eg-test-ecs-cloudwatch-sns-alarms-memory-utilization-high
memory_utilization_high_cloudwatch_metric_alarm_id = eg-test-ecs-cloudwatch-sns-alarms-memory-utilization-high
memory_utilization_low_cloudwatch_metric_alarm_arn = arn:aws:cloudwatch:us-east-2:126450723953:alarm:eg-test-ecs-cloudwatch-sns-alarms-memory-utilization-low
memory_utilization_low_cloudwatch_metric_alarm_id = eg-test-ecs-cloudwatch-sns-alarms-memory-utilization-low
private_subnet_cidrs = [
"172.16.0.0/19",
"172.16.32.0/19",
]
public_subnet_cidrs = [
"172.16.96.0/19",
"172.16.128.0/19",
]
service_name = eg-test-ecs-cloudwatch-sns-alarms
service_role_arn = arn:aws:iam::126450723953:role/eg-test-ecs-cloudwatch-sns-alarms-service
service_security_group_id = sg-0a841038ac859d842
task_definition_family = eg-test-ecs-cloudwatch-sns-alarms
task_definition_revision = 1
task_exec_role_arn = arn:aws:iam::126450723953:role/eg-test-ecs-cloudwatch-sns-alarms-exec
task_exec_role_name = eg-test-ecs-cloudwatch-sns-alarms-exec
task_role_arn = arn:aws:iam::126450723953:role/eg-test-ecs-cloudwatch-sns-alarms-task
task_role_id = AROAR24IM5RYUCXV7QQLU
task_role_name = eg-test-ecs-cloudwatch-sns-alarms-task
vpc_cidr = 172.16.0.0/16
Regenerate README.md @vadim-hleif (#6)
what
- Regenerate
README.md
why
- Previous version of build-harness has some typos
Contributors
Assets 2
v0.12.3
git.io->cloudposse.tools update @dylanbannon (#29)
what and why
Change all references to git.io/build-harness into cloudposse.tools/build-harness, since git.io redirects will stop working on April 29th, 2022.
References
- DEV-143
🤖 Automatic Updates
Update context.tf @cloudpossebot (#30)
what
This is an auto-generated PR that updates the context.tf file to the latest version from cloudposse/terraform-null-label
why
To support all the features of the context interface.
Contributors
Assets 2
v0.12.2
🤖 Automatic Updates
Update Terraform cloudposse/label/null to v0.25.0 @renovate (#27)
This PR contains the following updates:
| Package | Type | Update | Change |
|---|---|---|---|
| cloudposse/label/null (source) | module | minor | 0.24.1 -> 0.25.0 |
Release Notes
cloudposse/terraform-null-label
v0.25.0
Add "tenant", "labels_as_tags", and "descriptors" @Nuru (#132)
##### what - Add additional label and `id` component: `tenant` - New input `labels_as_tags` controls which labels are exported as tags - New input `descriptor_formats` generates new output `descriptors` - Update README, remove link to obsolete `terraform-terraform-label` ##### why - Support users that host resources on behalf of and/or dedicated to single customers - Supersedes and closes #131, giving people control over which tags the module generates - Simple mechanism for creating multiple identifiers from the same inputs, reducing the need to create multiple instances of `null-label` - Document `tenant`, `labels_as_tags`, `descriptor_formats`, add additional clarification, stop promoting obsolete moduleFix: Update README Snippets @korenyoni (#130)
##### what * Update README snippets to reflect use of Terraform Registry. ##### why * Including snippets that reflect use of the Terraform Registry make it easier for users to quickly instantiate a null_label module. * README is out of date and does not include snippets that reflect use of the Terraform Registry. ##### references * N/ABridgecrew compliance @Nuru (#125)
##### what - Resolve Bridgecrew compliance complaint about example Autoscaling Group (BC_AWS_GENERAL_31) - Fix typo in README - Include Terraform lock file in `.gitignore` ##### why - Get clean Bridgecrew badge - Correct confusing error - Ensure lock files are not checked into GitHub ##### note The PR can and should be merged into `master` to update README and Bridgecrew without triggering a new release/version. These changes have no effect on the actual module in use and a release will create unnecessary ripple effects. However, merging to `master` will update the README and badges, so is worthwhile, and the changes will move forward into the next release.Properly output descriptors of chained modules @Nuru (#133)
##### what - Properly output descriptors of chained modules ##### why - Bug fix; implement intended behaviorConfiguration
📅 Schedule: At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Renovate will not automatically rebase this PR, because other commits have been found.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
- If you want to rebase/retry this PR, check this box.
This PR has been generated by WhiteSource Renovate. View repository job log here.
Contributors
Assets 2
v0.12.1
🤖 Automatic Updates
Update Terraform cloudposse/label/null to v0.24.1 @renovate (#26)
This PR contains the following updates:
| Package | Type | Update | Change |
|---|---|---|---|
| cloudposse/label/null (source) | terraform | minor | 0.22.1 -> 0.24.1 |
Release Notes
cloudposse/terraform-null-label
v0.24.1
Allow control of letter case of outputs @SweetOps (#107)
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.
- You can set
label_key_caseto one ofupper,lower, ortitle, which will result in generatedtagnames in the corresponding case:NAME,name, orName. For backwards compatibility,titleis the default - You can set
label_value_caseto one ofupper,lower,title, ornone, which will result in output label values in the corresponding case (withnonemeaning no case conversion of any kind will be done, though the labels will still be subject toregex_replace_chars). The case converted labels will show up not just in the module output of the labels themselves, but also in thetagvalues and in theidstring.
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 = "".
Include updates to exports/context.tf @Nuru (#122 and #123)
##### what - Include updates to `exports/context.tf` - Update README with features and compatibilty - Add validation for `id_length_limit` ##### why - The `exports/context.tf` is what gets distributed and needs to be in sync - Replace outdated information - Was not validated earlier because validators are not supported in TF 0.12 but now we are dropping support for TF 0.12 and so we can add validatorsRestore backward compatibility with v0.22.1 and earlier @Nuru (#121)
##### what - Restore backward compatibility with v0.22.1 and earlier - Allow setting of `label_key_case` and `label_value_case` by vars, not just by context attributes. ##### why - Allow interoperability of old and new modules - Normally, root modules make settings via individual variables, not by setting an entire context block.Incorporates and closes #120
v0.24.0
Restore backward compatibility with v0.22.1 and earlier @Nuru (#121)
##### what - Restore backward compatibility with v0.22.1 and earlier - Allow setting of `label_key_case` and `label_value_case` by vars, not just by context attributes. ##### why - Allow interoperability of old and new modules - Normally, root modules make settings via individual variables, not by setting an entire context block.Incorporates and closes #120
Allow control of letter case of outputs @SweetOps (#107)
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.
- You can set
label_key_caseto one ofupper,lower, ortitle, which will result in generatedtagnames in the corresponding case:NAME,name, orName. For backwards compatibility,titleis the default - You can set
label_value_caseto one ofupper,lower,title, ornone, which will result in output label values in the corresponding case (withnonemeaning no case conversion of any kind will be done, though the labels will still be subject toregex_replace_chars). The case converted labels will show up not just in the module output of the labels themselves, but also in thetagvalues and in theidstring.
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.23.0
Known issues
- Does not interoperate with earlier versions of
null-label. The canonicalcontext = module.this.contextfails ifmodule.this.contextis an older version context.tfdoes not incorporatevar.label_key_caseandvar.label_value_caseinto themodule.thisobject, preventing those variables from taking effect in the root module'smodule.this.
feat: add support for setting letter case of context tags @SweetOps (#107)
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.
- You can set
label_key_caseto one ofupper,lower, ortitle, which will result in generatedtagnames in the corresponding case:NAME,name, orName. For backwards compatibility,titleis the default - You can set
label_value_caseto one ofupper,lower,title, ornone, which will result in output label values in the corresponding case (withnonemeaning no case conversion of any kind will be done, though the labels will still be subject toregex_replace_chars). The case converted labels will show up not just in the module output of the labels themselves, but also in thetagvalues and in theidstring.
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.12.0
context.tf updated to v0.24.1, minimum required Terraform version bumped to 0.13.0 when needed, readme updated @maximmi (#25)
what
- update context.tf to v0.24.1
- minimum required Terraform version bumped to 0.13.0
- readme updated, Bridgecrew compliance badges added
why
- It allows for setting the letter case of tag names and labels, back compatibility with context v0.22.0 and below
- we have dropped support for Terraform 0.12
- To be able see and fix the recommendations from Bridgecrew so we can position our modules as standards compliant
v0.11.1
🤖 Automatic Updates
Update context.tf @cloudpossebot (#22)
what
This is an auto-generated PR that updates the context.tf file to the latest version from cloudposse/terraform-null-label
why
To support all the features of the context interface.
v0.11.0
minimum required Terraform version bumped to 0.13.0, context.tf updated, readme updated @maximmi (#24)
what
- update context.tf to v0.23.0
- minimum required Terraform version bumped to 0.13.0
- readme updated, Bridgecrew compliance badges added
why
- It allows for setting the letter case of tag names and labels
- we have dropped support for Terraform 0.12
- To be able see and fix the recommendations from Bridgecrew so we can position our modules as standards compliant
v0.10.1
🤖 Automatic Updates
Update README.md and docs @cloudpossebot (#23)
what
This is an auto-generated PR that updates the README.md and docs
why
To have most recent changes of README.md and doc from origin templates