terraform-aws-vpc-peering-multi-account

what

• Remove of enabled part of the for_each ternary, as it disables assume_role on enabled = false, which blocks teardown

why

• local.enabled ternary causes no provider to be present on enabled = false, preventing teardown

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

🚀 Enhancements

what

• Data source aws_subnet_ids was replaced with aws_subnet for requester. This was already implemented for accepter.

why

• aws_subnet_ids has been deprecated and will be removed.

references

• https://registry.terraform.io/providers/hashicorp/aws/latest/docs/data-sources/subnet_ids

what

• Reverts PR #44 which introduced a bug when using default routing table

references

• Fixes #45
• Reopens https://github.com/cloudposse/terraform-aws-vpc-peering-multi-account/issues/30

what

• Adds configurable timeouts for AWS route creation and deletion

why

• Route creation and deletion can take longer than the provider defaults of 2m (creation) and 5m (deletion)

references

• Default timeouts set as they are in the provider, see https://registry.terraform.io/providers/hashicorp/aws/3.69.0/docs/resources/route#timeouts.
• Already implemented for terraform-aws-dynamic-subnets, this PR does the same for this module.

🚀 Enhancements

what

• Disable provider role assumption if enabled is false

why

• Allow enabled = false

references

N/A

what

• Add accepter_enabled variable

why

• Allow provisioning only the requester side of the peering connection
• Useful in cases where the accepter side of the connection is managed manually

🤖 Automatic Updates

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.

🤖 Automatic Updates

This PR contains the following updates:

Release Notes

v0.25.0

Compare Source

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, check this box.

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

what

• add variable add_attribute_tag that will control creation of additional attribute accepted for accepted and requster for requester

why

This module can be used for creating cross-account and same account vpc peering. The case si next: if use dynamic aws creds in loop, but different attribute tag for accepted and the requester will conflict with each other for same account vpc peering. Also some time its not needed to add any additional attributes

Introduces a bug #45 in failed attempt to fix #30 . No other changes to module itself. Use v0.14.0 until the next release.

what

• Update accepter, GitHub actions, LICENSE, README

why

• Keep up to date

related

• Closes #30 (update: does not really fix #30)
• Closes #31

what

• Adds AWS credentials variables into providers ( access key id, secret access key, session token)

why

• I have a use case of using Hashicorp Vault to fetch AWS credentials, i need a way to pass these fetched credentials into the module.

🚀 Enhancements

what

• Allow user to pass in optional profile to be used when assuming the specified role.

why

• As stated in the issue, if you normally configure profile in your aws provider block, plan will fail with the following message. This is because the default credentials don't have permission to assume the specified role.

Refreshing Terraform state in-memory prior to plan...
The refreshed state will be used to calculate this plan, but will not be
persisted to local or remote state storage.


Error: error configuring Terraform AWS Provider: IAM Role (arn:aws:iam::XXXX:role/vpc-peering-role) cannot be assumed.

There are a number of possible causes of this - the most common are:
  * The credentials used in order to assume the role are invalid
  * The credentials do not have appropriate permission to assume the role
  * The role ARN is not valid

Error: NoCredentialProviders: no valid providers in chain. Deprecated.
	For verbose messaging see aws.Config.CredentialsChainVerboseErrors

Also, there was a question of whether or not passing in an empty string would be okay for the AWS provider and it seems to work fine.

references

closes https://github.com/cloudposse/terraform-aws-vpc-peering-multi-account/issues/7

changed from ceil to floor

what

• when acceptor vpc has two cidr ranges, this will not work, the range of index starts from 0 to a number, not 1 to a number

why

• fix a bug

🤖 Automatic Updates

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

🤖 Automatic Updates

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.

🤖 Automatic Updates

This PR contains the following updates:

Release Notes

v0.24.1

Compare Source

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 = "".

Incorporates and closes #​120

🤖 Automatic Updates

This PR contains the following updates:

Release Notes

v0.24.0

Compare Source

Incorporates and closes #​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.

• 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

Compare Source

• 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_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 = "".

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

🚀 Enhancements

fix link to terraform-aws-vpc-peering - it was pointing to terraform-aws-vpc

🤖 Automatic Updates

This PR contains the following updates:

Release Notes

v0.22.1

Compare Source

v0.22.0

Compare Source

Breaking change: This release updates minimum Terraform version requirement to 0.12.26