Terraform module to provision a VPC peering across multiple VPCs in different accounts by using multiple providers
APACHE-2.0 License
Bot releases are visible (Hide)
for_each
ternary, as it disables assume_role
on enabled = false, which blocks teardownlocal.enabled
ternary causes no provider to be present on enabled = false, preventing teardownPublished by cloudpossebot over 2 years ago
Change all references to git.io/build-harness
into cloudposse.tools/build-harness
, since git.io
redirects will stop working on April 29th, 2022.
aws_subnet_ids
was replaced with aws_subnet
for requester. This was already implemented for accepter.aws_subnet_ids
has been deprecated and will be removed.Published by cloudpossebot over 2 years ago
Published by cloudpossebot over 2 years ago
Published by cloudpossebot almost 3 years ago
N/A
Published by cloudpossebot almost 3 years ago
accepter_enabled
variablePublished by cloudpossebot almost 3 years ago
This is an auto-generated PR that updates the context.tf
file to the latest version from cloudposse/terraform-null-label
To support all the features of the context
interface.
Published by cloudpossebot almost 3 years ago
This PR contains the following updates:
Package | Type | Update | Change |
---|---|---|---|
cloudposse/label/null (source) | module | minor |
0.24.1 -> 0.25.0
|
v0.25.0
π 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.
This PR has been generated by WhiteSource Renovate. View repository job log here.
Published by cloudpossebot over 3 years ago
add_attribute_tag
that will control creation of additional attribute accepted
for accepted and requster
for requesterThis 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
Published by cloudpossebot over 3 years ago
Introduces a bug #45 in failed attempt to fix #30 . No other changes to module itself. Use v0.14.0 until the next release.
accepter
, GitHub actions, LICENSE, READMEPublished by cloudpossebot over 3 years ago
Published by cloudpossebot over 3 years ago
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.
closes https://github.com/cloudposse/terraform-aws-vpc-peering-multi-account/issues/7
Published by cloudpossebot over 3 years ago
changed from ceil to floor
Published by cloudpossebot over 3 years ago
Published by cloudpossebot over 3 years ago
This is an auto-generated PR that updates the context.tf
file to the latest version from cloudposse/terraform-null-label
To support all the features of the context
interface.
Published by cloudpossebot over 3 years ago
This PR contains the following updates:
Package | Type | Update | Change |
---|---|---|---|
cloudposse/label/null (source) | terraform | patch |
0.24.0 -> 0.24.1
|
v0.24.1
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
.
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 defaultlabel_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 id
s in Pascal case by setting label_value_case = "title"
and delimiter = ""
.
Incorporates and closes #β120
Published by cloudpossebot over 3 years ago
This PR contains the following updates:
Package | Type | Update | Change |
---|---|---|---|
cloudposse/label/null (source) | terraform | minor |
0.22.1 -> 0.24.0
|
v0.24.0
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
.
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 defaultlabel_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 id
s in Pascal case by setting label_value_case = "title"
and delimiter = ""
.
v0.23.0
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
.
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 defaultlabel_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 id
s in Pascal case by setting label_value_case = "title"
and delimiter = ""
.
Published by cloudpossebot over 3 years ago
Published by cloudpossebot over 3 years ago
fix link to terraform-aws-vpc-peering
- it was pointing to terraform-aws-vpc
Published by cloudpossebot almost 4 years ago
This PR contains the following updates:
Package | Type | Update | Change |
---|---|---|---|
cloudposse/label/null (source) | terraform | minor |
0.21.0 -> 0.22.1
|
v0.22.1
v0.22.0
Breaking change: This release updates minimum Terraform version requirement to 0.12.26