Prepare for version 1.20

[johngmyers]

No description provided.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: johngmyers

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [johngmyers]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[hakman]

Looks fine to me. @rifelpet, maybe you want to take a look also.

[rifelpet]

The 1.19 release notes currently mention that only Terraform-0.12 will be removed, it doesn't mention that TerraformJSON will be removed, so we'd need to keep target_0_11.go and the MinimalJSON integration test unless we decide to also deprecate and remove TerraformJSON.

[johngmyers]

@rifelpet TerraformJSON does nothing unless Terraform-0.12 is off. So it doesn't make sense to keep TerraformJSON as a no-op. And I see no reason to require a deprecation notice for a feature flag that defaults off.

[rifelpet]

I was thinking TerraformJSON would imply the current TerraformJSON,-Terraform-0.12 behavior but -Terraform-0.12 on its own would no longer be valid. #9940 implements much of this so it might be better to defer those changes to that PR. I agree that removing a feature flag that defaults to off shouldn't require a deprecation notice but it might still be helpful to get user feedback, given that the Terraform JSON output is still a valid use-case for Terraform 0.12+.

[johngmyers]

I created #10106 to effect that change in the TerraformJSON semantics.

[rifelpet]

I believe this is ready for a rebase and merge.

[rifelpet]

/lgtm