Releases: cloudposse/terraform-aws-sns-lambda-notify-slack
v0.5.5
🤖 Automatic Updates
Update Terraform terraform-aws-modules/notify-slack/aws to 4.18 @renovate (#23)
This PR contains the following updates:
Package | Type | Update | Change |
---|---|---|---|
terraform-aws-modules/notify-slack/aws (source) | module | minor | 4.12 -> 4.18 |
Release Notes
terraform-aws-modules/terraform-aws-notify-slack
v4.18.0
- feat: Added support for GuardDuty Findings format (#143)
v4.17.0
- feat: Allow custom attachement (#123)
v4.16.0
- feat: add support for nested messages (#142)
v4.15.0
- chore: Remove check boxes that don't render properly in module doc (#140)
- chore: update CI/CD to use stable
terraform-docs
release artifact and discoverable Apache2.0 license (#138)
v4.14.0
- feat: Updated code to support Terraform 0.15 (#136)
- chore: update documentation and pin
terraform_docs
version to avoid future changes (#134)
v4.13.0
- fix: use the current aws partition (#133)
- chore: align ci-cd static checks to use individual minimum Terraform versions (#131)
- fix: Remove data resource for sns topic to avoid race condition (#81)
- chore: add ci-cd workflow for pre-commit checks (#128)
- feat: Improve slack message formatting for generic messages (#124)
- chore: update documentation based on latest
terraform-docs
which includes module and resource sections (#126) - feat: add support for GovCloud URLs (#114)
- feat: Allow Lambda function to be VPC bound (#122)
- feat: Updated version of terraform-aws-lambda module to 1.28.0 (#119)
- feat: Updated version of Terraform AWS Lambda module to support multiple copies (#117)
- fix: Typo on subscription_filter_policy variable (#113)
- docs: Added a note about using with Terraform Cloud Agents (#108)
- feat: allow reuse of existing lambda_role (#85)
- fix: Fix regression with aws_cloudwatch_log_group resource after upgrade of AWS provider 3.0 (#106)
- docs: Updated version of module to use for Terraform 0.12 users
- fix: Updated version requirements to be Terraform 0.13 only (#101)
- feat: Updated Lambda module to work with Terraform 0.13 (#99)
- fix: Bump version of lambda module that supports Terraform 13 and AWS Provider 3.x (#96)
Configuration
📅 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, click this checkbox.
This PR has been generated by WhiteSource Renovate. View repository job log here.
v0.5.4
🤖 Automatic Updates
Update Terraform cloudposse/label/null to v0.25.0 @renovate (#26)
This PR contains the following updates:
Package | Type | Update | Change |
---|---|---|---|
cloudposse/label/null (source) | module | minor | 0.22.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 behaviorv0.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_case
to one ofupper
,lower
, ortitle
, which will result in generatedtag
names in the corresponding case:NAME
,name
, orName
. For backwards compatibility,title
is the default - You can set
label_value_case
to one ofupper
,lower
,title
, ornone
, which will result in output label values in the corresponding case (withnone
meaning 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 thetag
values and in theid
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 = ""
.
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
The input regex_replace_chars
specifies a regular expression, and characters matching it are removed
from labels/id elements. Prior to this release, if the delimiter
itself matched the regular expression,
then the delimiter would be removed from the attributes
portion of the id
. This was not a problem
for most users, since the default delimiter was -
(dash) and the default regex allowed dashes, but
if you customized the delimiter and/or regex, this could affect you.
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_case
to one ofupper
,lower
, ortitle
, which will result in generatedtag
names in the corresponding case:NAME
,name
, orName
. For backwards compatibility,title
is the default - You can set
label_value_case
to one ofupper
,lower
,title
, ornone
, which will result in output label values in the corresponding case (withnone
meaning 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 thetag
values and in theid
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
Known issues
- Does not interoperate with earlier versions of
null-label
. The canonicalcontext = module.this.context
fails ifmodule.this.context
is an older version context.tf
does not incor...
v0.5.3
🤖 Automatic Updates
Update Terraform terraform-aws-modules/notify-slack/aws to 4.12 @renovate (#22)
This PR contains the following updates:
Package | Type | Update | Change |
---|---|---|---|
terraform-aws-modules/notify-slack/aws (source) | terraform | minor | 4.11 -> 4.12 |
Release Notes
terraform-aws-modules/terraform-aws-notify-slack
v4.12.0
v0.5.2
🤖 Automatic Updates
Update Terraform terraform-aws-modules/notify-slack/aws to 4.11 @renovate (#18)
This PR contains the following updates:
Package | Type | Update | Change |
---|---|---|---|
terraform-aws-modules/notify-slack/aws (source) | terraform | minor | 4.0 -> 4.11 |
Release Notes
terraform-aws-modules/terraform-aws-notify-slack
v4.11.0
- feat: Improve slack message formatting for generic messages (#124)
v4.10.0
- chore: update documentation based on latest
terraform-docs
which includes module and resource sections (#126)
v4.9.0
- feat: add support for GovCloud URLs (#114)
v4.8.0
- feat: Allow Lambda function to be VPC bound (#122)
v4.7.0
- feat: Updated version of terraform-aws-lambda module to 1.28.0 (#119)
v4.6.0
- feat: Updated version of Terraform AWS Lambda module to support multiple copies (#117)
v4.5.0
- fix: Typo on subscription_filter_policy variable (#113)
v4.4.0
- docs: Added a note about using with Terraform Cloud Agents (#108)
v4.3.0
- feat: allow reuse of existing lambda_role (#85)
v4.2.0
- fix: Fix regression with aws_cloudwatch_log_group resource after upgrade of AWS provider 3.0 (#106)
- docs: Updated version of module to use for Terraform 0.12 users
- fix: Updated version requirements to be Terraform 0.13 only (#101)
- feat: Updated Lambda module to work with Terraform 0.13 (#99)
- fix: Bump version of lambda module that supports Terraform 13 and AWS Provider 3.x (#96)
v4.1.0
- fix: Updated version requirements to be Terraform 0.13 only (#101)
v0.5.1
🤖 Automatic Updates
Update context.tf @cloudpossebot (#20)
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.5.0
0.4.0: Updates to ChatOps - Automated commit (#12)
## 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
0.3.0 Convert to TF 0.12. Add Codefresh test pipeline
what
- Port module to Terraform 0.12
- Pin all providers
- Add Codefresh badge to point to the test pipeline in
terraform-modules
project - Update README
- Add missing outputs
why
- Module currently does not work with 0.12. Much easier syntax
terraform-modules
project contains pipelines for all terraform modules
Regenerate README.md
what
- Regenerate
README.md
why
- Previous version of build-harness has some typos
Fix readme
what
- Add
README.yaml
why
- Standardize README