Configure Cloud SQL in GA provider to use v1 API endpoint

[nika-pr]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request.
• Please do not leave +1 or me too comments, they generate extra noise for issue followers and do not help prioritize the request.
• If you are interested in working on this issue or have submitted a pull request, please leave a comment.
• If an issue is assigned to a user, that user is claiming responsibility for the issue.
• Customers working with a Google Technical Account Manager or Customer Engineer can ask them to reach out internally to expedite investigation and resolution of this issue.

Issue

The GA Google Cloud SQL Terraform provider (hashicorp/google) was found using a beta API endpoint (v1beta4) instead of the expected GA v1 API. Unsure if this is intentional. It may be a breaking change to promote it to the v1 endpoint.

Terraform Version & Provider Version(s)

Terraform v1.10.5
on linux_amd64

• provider registry.terraform.io/hashicorp/google v6.32.0
• provider registry.terraform.io/hashicorp/google-beta v6.32.0

Affected Resource(s)

google_sql_*

Terraform Configuration

N/A

Debug Output

N/A

Expected Behavior

N/A

Actual Behavior

N/A

Steps to reproduce

N/A

Important Factoids

This isn't a classic bug report but I still feel this is the best category for this issue.

As I was debugging issues I was having with google_sql_ resources, I discovered that the provider is currently configured to use the v1beta4 Cloud SQL API, rather than the v1 API when using the main hashicorp/google provider.

Both APIs seem to have the same methods available to them, however without deeper knowledge of their implementations, I can't make an assessment as to whether this change would break something for existing users.

Could the Cloud SQL service team take a look?

References

https://github.com/GoogleCloudPlatform/magic-modules/pull/13782/files

b/414856433

[ggtisc]

Hi @nika-pr

As the name suggests, the beta provider is used for new features in development, unlike the normal provider. If both apparently have the same features, it is possible that internally they have timely changes, so this is not considered a bug.

[nika-pr]

Please take a look at the linked PR then, I was sent here from the review there.

[ScottSuarez]

Hi @nika-pr

As the name suggests, the beta provider is used for new features in development, unlike the normal provider. If both apparently have the same features, it is possible that internally they have timely changes, so this is not considered a bug.

Hi @ggtisc, this ticket is stating that the GA provider is using the beta endpoint. They are unsure if that it intentional. This may be a breaking change. I would be good to make the service team at least aware of this in case they need to change it.

[ScottSuarez]

Also to clarify this is a product level change and would effect all resources in that product..

• google_sql_database_instance
• google_sql_database_instances
• google_sql_source_representation_instance
• google_sql_tiers
• google_sql_ca_certs
• google_sql_ssl_cert
• google_sql_backup_run
• google_sql_database_instance_latest_recovery_time
• google_sql_user
• google_sql_database
• google_sql_databases

The change's blast radius will be quite large and span multiple product teams. But I think we should call attention to it just in case this is not intentional. If they want/need to change this then we can open discussion on when to do so (likely 7.0 release in August).

[ggtisc]

Thanks Scott, I'm adding the label to complete the forward process according to our conversation

[harshika18]

Despite the 'beta' designation, v1beta4 is not a separate or less stable endpoint. It is exactly identical to v1, and transitioning to v1 is safe and will not cause compatibility issues.