chore(deps): update terraform cloudposse/ecs-codepipeline/aws to v0.21.0 - autoclosed #86
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
0.19.0
->0.21.0
Release Notes
cloudposse/terraform-aws-ecs-codepipeline
v0.21.0
Compare Source
Support TF 0.12 with pinned GitHub provider 3.0.0 @Nuru (#64)
#### what - Support TF 0.12 with pinned GitHub provider 3.0.0 - Temporarily revert TF 0.13 requirements #### why - Dependent modules were broken because of GitHub provider issues. Fix them before abandoning TF 0.12 support #### references https://github.com//issues/63v0.20.2
Compare Source
🤖 Automatic Updates
Update Terraform cloudposse/label/null to v0.24.1 @renovate (#57)
This PR contains the following updates:
0.22.1
->0.24.1
Release Notes
cloudposse/terraform-null-label
##### [`v0.24.1`](https://togithub.com/cloudposse/terraform-null-label/releases/0.24.1)Compare Source
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
, namelynamespace
,environment
,stage
,name
, andattributes
. For every non-empty label, a corresponding tag name is generated. Fornamespace
,environment
,stage
, the output is the formatted, normalized input. (By "normalized" we mean that it goes throughregex_replace_chars
.), Forattributes
, 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 thedelimiter
(defaults to hyphen). Forname
, which is special, the output is the same asid
, which is the joining of the labels in the order specified bylabel_order
and separated bydelimiter
.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 defaultlabel_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 intest/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 settinglabel_value_case = "title"
anddelimiter = ""
.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
Compare Source
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
, namelynamespace
,environment
,stage
,name
, andattributes
. For every non-empty label, a corresponding tag name is generated. Fornamespace
,environment
,stage
, the output is the formatted, normalized input. (By "normalized" we mean that it goes throughregex_replace_chars
.), Forattributes
, 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 thedelimiter
(defaults to hyphen). Forname
, which is special, the output is the same asid
, which is the joining of the labels in the order specified bylabel_order
and separated bydelimiter
.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 defaultlabel_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 intest/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 settinglabel_value_case = "title"
anddelimiter = ""
.Compare Source
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
, namelynamespace
,environment
,stage
,name
, andattributes
. For every non-empty label, a corresponding tag name is generated. Fornamespace
,environment
,stage
, the output is the formatted, normalized input. (By "normalized" we mean that it goes throughregex_replace_chars
.), Forattributes
, 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 thedelimiter
(defaults to hyphen). Forname
, which is special, the output is the same asid
, which is the joining of the labels in the order specified bylabel_order
and separated bydelimiter
.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 defaultlabel_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 intest/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 settinglabel_value_case = "title"
anddelimiter = ""
.v0.20.1
Compare Source
🤖 Automatic Updates
Update Terraform cloudposse/codebuild/aws to v0.31.0 @renovate (#61)
This PR contains the following updates:
0.30.1
->0.31.0
Release Notes
cloudposse/terraform-aws-codebuild
##### [`v0.31.0`](https://togithub.com/cloudposse/terraform-aws-codebuild/releases/0.31.0)Compare Source
minimum required Terraform version bumped to 0.13.0, context.tf updated, readme updated @​maximmi (#​82)
##### 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 compliantv0.20.0
Compare Source
minimum required Terraform version bumped to 0.13.0, context.tf updated, readme updated @maximmi (#60)
#### 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 compliantv0.19.3
Compare Source
🤖 Automatic Updates
Update Terraform cloudposse/codebuild/aws to v0.30.1 @renovate (#59)
This PR contains the following updates:
0.30.0
->0.30.1
Release Notes
cloudposse/terraform-aws-codebuild
##### [`v0.30.1`](https://togithub.com/cloudposse/terraform-aws-codebuild/releases/0.30.1)Compare Source
🤖 Automatic Updates
Update README.md and docs @​cloudpossebot (#​81)
##### 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 templatesv0.19.2
Compare Source
🤖 Automatic Updates
Update Terraform cloudposse/codebuild/aws to v0.30.0 @renovate (#56)
This PR contains the following updates:
0.28.0
->0.30.0
Release Notes
cloudposse/terraform-aws-codebuild
##### [`v0.30.0`](https://togithub.com/cloudposse/terraform-aws-codebuild/releases/0.30.0)Compare Source
mfa_delete removed due to issue in terraform @​maximmi (#​79)
##### what * `mfa_delete` removed * Bridgecrew check `Ensure S3 bucket has MFA delete enabled` skipped ##### why * Because terraform doesn't support this argument to be toggled (https://github.com/hashicorp/terraform-provider-aws/issues/629). * To satisfy Bridgecrew compliance scan ##### references * https://github.com/hashicorp/terraform-provider-aws/issues/629Compare Source
readme updated, BridgeCrew compliance checks fixes, code cleaned @​maximmi (#​75)
##### what * BridgeCrew compliance checks fix * readme updated * default behaviour changed: `S3 bucket MFA delete` enabled by default * default behaviour changed: `S3 Bucket Versioning` enabled by default * default behaviour changed: `Encryption of the S3 bucket` enabled by default ##### why * To be able to position our modules as standards compliant * stay in sync with code * To comply BridgeCrew check ##### references * https://docs.bridgecrew.io/docs/s3_16-enable-versioning * https://docs.bridgecrew.io/docs/s3_13-enable-logging * https://docs.bridgecrew.io/docs/s3_14-data-encrypted-at-restv0.19.1
Compare Source
🤖 Automatic Updates
Update Terraform cloudposse/codebuild/aws to v0.28.0 @renovate (#55)
This PR contains the following updates:
0.27.0
->0.28.0
Release Notes
cloudposse/terraform-aws-codebuild
##### [`v0.28.0`](https://togithub.com/cloudposse/terraform-aws-codebuild/releases/0.28.0)Compare Source
Terraform 0.14 upgrade @​maximmi (#​74)
##### what - Upgrade to support Terraform 0.14 and bring up to current Cloud Posse standard ##### why - Support Terraform 0.14Renovate configuration
📅 Schedule: At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻️ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by WhiteSource Renovate. View repository job log here.