Cloud SQL disk_size and disk_autoresize documentation is misleading

[pjo256]

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 the modular-magician user, it is either in the process of being autogenerated, or is planned to be autogenerated soon. If an issue is assigned to a user, that user is claiming responsibility for the issue. If an issue is assigned to hashibot, a community member has claimed the issue already.

Description

The documentation for disk_size and disk_autoresize in https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/sql_database_instance#disk_size seem to indicate that they are mutually exclusive (disk_size - "If you want to set this field, set disk_autoresize to false."). However in GCP, it's possible to enable both on a Cloud SQL instance -

Affected Resource(s)

• google_sql_database_instance

[pjo256]

I'll have a pull request up later this afternoon in https://github.com/GoogleCloudPlatform/magic-modules to address this

[github-actions[bot]]

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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.