Add deprecation message for generated beta fields.

[modular-magician]

/cc @danawillow

[danawillow]

For #2143.

Marking as a WIP because I don't want to submit this until we're definitely sure this is what we're doing, but at least for now I wouldn't mind some feedback on wording.

[danawillow]

Actually, a better reason for this being a WIP is that some of these fields/resources have reached GA now, and should be marked as such.

[paddycarver]

I'd ideally like to get a guide page up on the website explaining the multi-provider situation, so we can link to it from the deprecation message. I think we should also use the Resource.DeprecationMessage property when entire resources are getting deprecated, instead of setting it on each field.

I think

Use terraform-provider-google-beta to continue using it.

Makes sense to us, but to a user it may be confusing. Something like

Use the $RESOURCE resource in the terraform-provider-google-beta provider to continue using it. See https://terraform.io/docs/provider/google/guides/provider-versions.html for more details on beta {field/resource}s.

may give some more context? The parts I think are important in that:

• calling out that terraform-provider-google-beta is a different provider
• directing them to the resource to use--yes, they should have the same name, but I think it helps underscore that the providers aren't all-in, you can do them on a resource-by-resource basis
• there's a link to some documentation explaining how to use the other provider, because the provider = "google-beta" hack won't be intuitive at first.

[bluemalkin]

It would be good if the CHANGELOG documentation would instruct people how to update their existing states... coming from a previous version of the provider.

e.g. Warning: google_container_node_pool.api: "region": [DEPRECATED] This field is in beta and will be removed from this provider. Use it in the the google-beta provider instead. See https://terraform.io/docs/providers/google/provider_versions.html for more details.

So I go and remove region attribute and now terraform wants force resource re-creation !

[paddycarver]

Did you try using it with the google-beta provider?

[bluemalkin]

@paddycarver I did but I do not want to switch to the beta provider that is my point

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 hashibot-feedback@hashicorp.com. Thanks!