Add deletion_protection field for oracledatabase resources

[tulika-aakriti]

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.

Description

Update API is not supported yet which leads to deletion and creation of new resource when a user try to update a field, which is default terraform behaviour. We can add a deletion_protection field to warn user regarding the same.

New or Affected Resource(s)

• google_oracle_database_cloud_exadata_infrastructure
• google_oracle_database_autonomous_database
• google_oracle_database_cloud_vm_cluster

Potential Terraform Configuration

References

No response

[tulika-aakriti]

We want to make an exception for this changes i.e. to add deletion_protection field in the resources (google_oracle_database_cloud_exadata_infrastructure, google_oracle_database_autonomous_database, google_oracle_database_cloud_vm_cluster) to be part for weekly release. The update API is not implemented so every update call from tf can lead to accidental deletion of database and there is no way for the customer to restore it. There are no active customers using terraform as we onboarded last week so this breaking change should not affect anyone.

cc- @rileykarson @slevenick