Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): update terraform cloudposse/ecs-codepipeline/aws to v0.21.0 - autoclosed #86

Closed

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 26, 2021

WhiteSource Renovate

This PR contains the following updates:

Package Type Update Change
cloudposse/ecs-codepipeline/aws (source) terraform minor 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/63

v0.20.2

Compare Source

🤖 Automatic Updates

Update Terraform cloudposse/label/null to v0.24.1 @​renovate (#​57)

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`](https://togithub.com/cloudposse/terraform-null-label/releases/0.24.1)

Compare Source

Allow control of letter case of outputs @​&#​8203;SweetOps (#&#​8203;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 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 default
  • You can set label_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 = "".

Include updates to exports/context.tf @​&#​8203;Nuru (#&#​8203;122 and #&#​8203;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 validators
Restore backward compatibility with v0.22.1 and earlier @​&#​8203;Nuru (#&#​8203;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 #&#​8203;120

##### [`v0.24.0`](https://togithub.com/cloudposse/terraform-null-label/releases/0.24.0)

Compare Source

Restore backward compatibility with v0.22.1 and earlier @​&#​8203;Nuru (#&#​8203;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 #&#​8203;120

Allow control of letter case of outputs @​&#​8203;SweetOps (#&#​8203;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 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 default
  • You can set label_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.23.0`](https://togithub.com/cloudposse/terraform-null-label/releases/0.23.0)

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, 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 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 default
  • You can set label_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.20.1

Compare Source

🤖 Automatic Updates

Update Terraform cloudposse/codebuild/aws to v0.31.0 @​renovate (#​61)

This PR contains the following updates:

Package Type Update Change
cloudposse/codebuild/aws (source) terraform minor 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 @​&#​8203;maximmi (#&#​8203;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 compliant

v0.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 compliant

v0.19.3

Compare Source

🤖 Automatic Updates

Update Terraform cloudposse/codebuild/aws to v0.30.1 @​renovate (#​59)

This PR contains the following updates:

Package Type Update Change
cloudposse/codebuild/aws (source) terraform patch 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 @​&#​8203;cloudpossebot (#&#​8203;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 templates

v0.19.2

Compare Source

🤖 Automatic Updates

Update Terraform cloudposse/codebuild/aws to v0.30.0 @​renovate (#​56)

This PR contains the following updates:

Package Type Update Change
cloudposse/codebuild/aws (source) terraform minor 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 @​&#​8203;maximmi (#&#​8203;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/629
##### [`v0.29.0`](https://togithub.com/cloudposse/terraform-aws-codebuild/releases/0.29.0)

Compare Source

readme updated, BridgeCrew compliance checks fixes, code cleaned @​&#​8203;maximmi (#&#​8203;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-rest

v0.19.1

Compare Source

🤖 Automatic Updates

Update Terraform cloudposse/codebuild/aws to v0.28.0 @​renovate (#​55)

This PR contains the following updates:

Package Type Update Change
cloudposse/codebuild/aws (source) terraform minor 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 @​&#​8203;maximmi (#&#​8203;74) ##### what - Upgrade to support Terraform 0.14 and bring up to current Cloud Posse standard ##### why - Support Terraform 0.14

Renovate 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.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by WhiteSource Renovate. View repository job log here.

@renovate renovate bot requested review from a team as code owners January 26, 2021 00:15
@renovate renovate bot requested review from adamcrews and joe-niland and removed request for a team January 26, 2021 00:15
@renovate renovate bot added the auto-update This PR was automatically generated label Jan 26, 2021
@renovate renovate bot changed the title chore(deps): update terraform cloudposse/ecs-codepipeline/aws to v0.19.1 chore(deps): update terraform cloudposse/ecs-codepipeline/aws to v0.19.2 Jan 29, 2021
@renovate renovate bot force-pushed the renovate/cloudposse-ecs-codepipeline-aws-0.x branch from 0deff05 to fa2584a Compare January 29, 2021 06:21
@renovate renovate bot changed the title chore(deps): update terraform cloudposse/ecs-codepipeline/aws to v0.19.2 chore(deps): update terraform cloudposse/ecs-codepipeline/aws to v0.19.3 Feb 3, 2021
@renovate renovate bot force-pushed the renovate/cloudposse-ecs-codepipeline-aws-0.x branch 2 times, most recently from 3881c9b to 222e80c Compare February 4, 2021 07:34
@renovate renovate bot changed the title chore(deps): update terraform cloudposse/ecs-codepipeline/aws to v0.19.3 chore(deps): update terraform cloudposse/ecs-codepipeline/aws to v0.20.0 Feb 4, 2021
@renovate renovate bot force-pushed the renovate/cloudposse-ecs-codepipeline-aws-0.x branch from 222e80c to 9a0f695 Compare February 4, 2021 08:04
@renovate renovate bot changed the title chore(deps): update terraform cloudposse/ecs-codepipeline/aws to v0.20.0 chore(deps): update terraform cloudposse/ecs-codepipeline/aws to v0.20.1 Feb 4, 2021
@renovate renovate bot force-pushed the renovate/cloudposse-ecs-codepipeline-aws-0.x branch from 9a0f695 to ca3823c Compare February 4, 2021 10:23
@renovate renovate bot changed the title chore(deps): update terraform cloudposse/ecs-codepipeline/aws to v0.20.1 chore(deps): update terraform cloudposse/ecs-codepipeline/aws to v0.20.2 Feb 4, 2021
@renovate renovate bot force-pushed the renovate/cloudposse-ecs-codepipeline-aws-0.x branch from ca3823c to 377179b Compare February 5, 2021 03:51
@renovate renovate bot changed the title chore(deps): update terraform cloudposse/ecs-codepipeline/aws to v0.20.2 chore(deps): update terraform cloudposse/ecs-codepipeline/aws to v0.21.0 Feb 5, 2021
@renovate renovate bot changed the title chore(deps): update terraform cloudposse/ecs-codepipeline/aws to v0.21.0 chore(deps): update terraform cloudposse/ecs-codepipeline/aws to v0.21.0 - autoclosed Feb 5, 2021
@renovate renovate bot closed this Feb 5, 2021
@renovate renovate bot deleted the renovate/cloudposse-ecs-codepipeline-aws-0.x branch February 5, 2021 05:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
auto-update This PR was automatically generated
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant