Deprecate TerraformJSON feature flag #12341
Merged
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 breaks out portions of #12322 into separate PRs. Terraform's JSON support doesn't support provider aliases which means we cant use TerraformManagedFiles with it. This PR adds an error check ensuring they aren't used concurrently.
Given that we intend to eventually enable TerraformManagedFiles unconditionally and that TerraformJSON was implemented as a stop-gap until we had native HCL2 support for Terraform 0.12, it makes more sense to deprecate and eventually remove the TerraformJSON feature flag.
This also removes the TerraformJSON integration test. The test would need to disable TerraformManagedFiles which is pretty invasive to our integration test setup (the
expectedFileNames
would need to exclude all of theaws_s3_bucket_object
s) . Given that its deprecated and would be the only reason for such complexity, I opted to just remove the test altogether.