point_in_time_recovery_enabled for mssql

[anoopvenkataramana]

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 the 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 the issue is assigned to a user, that user is claiming responsibility for the issue. If the issue is assigned to "hashibot", a community member has claimed the issue already.

Description

We can enable point in time recovery for mssql using gcloud alpha command now
gcloud alpha sql instances patch <name_of_mssql_instance>
--enable-point-in-time-recovery

But we cannot enable this in terraform yet.

If I set point_in_time_recovery_enabled = true
it gives me below error:
│ Error: 1 error occurred:
│ * point_in_time_recovery_enabled is only available for Postgres. You may want to consider using binary_log_enabled instead.

If I enable this outside terraform code, that is by running gcloud command, then terraform will revert back in next run.
I also tried adding lifecycle - ignore_changes on point_in_time_recovery_enabled, but it gives the same error again.

New or Affected Resource(s)

SQLSERVER_2017_STANDARD (SQL server) in GCP SQL

Potential Terraform Configuration

resource "google_sql_database_instance" "sql" {
  name             = "test"
  database_version = "SQLSERVER_2017_STANDARD"

  settings {
    tier = "db-custom-2-4096"

    backup_configuration {
      enabled                        = true
      binary_log_enabled             = true
      point_in_time_recovery_enabled = true
      transaction_log_retention_days = 7
    }
  }
}

[github-actions]

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.