Updates minimum terraform version to 1.0 #11650
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
r0mant
approved these changes
Apr 1, 2022
webvictim
approved these changes
Apr 1, 2022
marcoandredinis
added a commit
that referenced
this pull request
Apr 1, 2022
Most of the changes are related to the strictness of TF v0.12 https://www.terraform.io/language/upgrade-guides/0-12 > Due to the design of the configuration language decoder in > Terraform v0.11 and earlier, it was in many cases possible to > interchange the argument syntax (with =) and the block syntax > (with just braces) when dealing with map arguments vs. nested > blocks. However, this led to some subtle bugs and limitations, > so Terraform v0.12 now requires consistent usage of argument > syntax for arguments and nested block syntax for nested blocks. This commit validates both examples against Terraform 1 The min terraform version is going to be updated to 1.0.0 #11650 Fixes #11652
marcoandredinis
added a commit
that referenced
this pull request
Apr 4, 2022
Most of the changes are related to the strictness of TF v0.12 https://www.terraform.io/language/upgrade-guides/0-12 > Due to the design of the configuration language decoder in > Terraform v0.11 and earlier, it was in many cases possible to > interchange the argument syntax (with =) and the block syntax > (with just braces) when dealing with map arguments vs. nested > blocks. However, this led to some subtle bugs and limitations, > so Terraform v0.12 now requires consistent usage of argument > syntax for arguments and nested block syntax for nested blocks. This commit validates both examples against Terraform 1 The min terraform version is going to be updated to 1.0.0 #11650 Fixes #11652
marcoandredinis
added a commit
that referenced
this pull request
Apr 5, 2022
Most of the changes are related to the strictness of TF v0.12 https://www.terraform.io/language/upgrade-guides/0-12 > Due to the design of the configuration language decoder in > Terraform v0.11 and earlier, it was in many cases possible to > interchange the argument syntax (with =) and the block syntax > (with just braces) when dealing with map arguments vs. nested > blocks. However, this led to some subtle bugs and limitations, > so Terraform v0.12 now requires consistent usage of argument > syntax for arguments and nested block syntax for nested blocks. This commit validates both examples against Terraform 1 The min terraform version is going to be updated to 1.0.0 #11650 Fixes #11652
marcoandredinis
added a commit
that referenced
this pull request
Apr 6, 2022
Most of the changes are related to the strictness of TF v0.12 https://www.terraform.io/language/upgrade-guides/0-12 > Due to the design of the configuration language decoder in > Terraform v0.11 and earlier, it was in many cases possible to > interchange the argument syntax (with =) and the block syntax > (with just braces) when dealing with map arguments vs. nested > blocks. However, this led to some subtle bugs and limitations, > so Terraform v0.12 now requires consistent usage of argument > syntax for arguments and nested block syntax for nested blocks. This commit validates both examples against Terraform 1 The min terraform version is going to be updated to 1.0.0 #11650 Fixes #11652
marcoandredinis
added a commit
that referenced
this pull request
Apr 14, 2022
Most of the changes are related to the strictness of TF v0.12 https://www.terraform.io/language/upgrade-guides/0-12 > Due to the design of the configuration language decoder in > Terraform v0.11 and earlier, it was in many cases possible to > interchange the argument syntax (with =) and the block syntax > (with just braces) when dealing with map arguments vs. nested > blocks. However, this led to some subtle bugs and limitations, > so Terraform v0.12 now requires consistent usage of argument > syntax for arguments and nested block syntax for nested blocks. This commit validates both examples against Terraform 1 The min terraform version is going to be updated to 1.0.0 #11650 Fixes #11652
marcoandredinis
added a commit
that referenced
this pull request
Apr 15, 2022
Most of the changes are related to the strictness of TF v0.12 https://www.terraform.io/language/upgrade-guides/0-12 > Due to the design of the configuration language decoder in > Terraform v0.11 and earlier, it was in many cases possible to > interchange the argument syntax (with =) and the block syntax > (with just braces) when dealing with map arguments vs. nested > blocks. However, this led to some subtle bugs and limitations, > so Terraform v0.12 now requires consistent usage of argument > syntax for arguments and nested block syntax for nested blocks. This commit validates both examples against Terraform 1 The min terraform version is going to be updated to 1.0.0 #11650 Fixes #11652
marcoandredinis
added a commit
that referenced
this pull request
Apr 15, 2022
Most of the changes are related to the strictness of TF v0.12 https://www.terraform.io/language/upgrade-guides/0-12 > Due to the design of the configuration language decoder in > Terraform v0.11 and earlier, it was in many cases possible to > interchange the argument syntax (with =) and the block syntax > (with just braces) when dealing with map arguments vs. nested > blocks. However, this led to some subtle bugs and limitations, > so Terraform v0.12 now requires consistent usage of argument > syntax for arguments and nested block syntax for nested blocks. This commit validates both examples against Terraform 1 The min terraform version is going to be updated to 1.0.0 #11650 Fixes #11652
marcoandredinis
added a commit
that referenced
this pull request
Apr 15, 2022
Most of the changes are related to the strictness of TF v0.12 https://www.terraform.io/language/upgrade-guides/0-12 > Due to the design of the configuration language decoder in > Terraform v0.11 and earlier, it was in many cases possible to > interchange the argument syntax (with =) and the block syntax > (with just braces) when dealing with map arguments vs. nested > blocks. However, this led to some subtle bugs and limitations, > so Terraform v0.12 now requires consistent usage of argument > syntax for arguments and nested block syntax for nested blocks. This commit validates both examples against Terraform 1 The min terraform version is going to be updated to 1.0.0 #11650 Fixes #11652
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No description provided.