Description

Add a client-side deletion_protection attribute to the ovh_cloud_project resource. When set to true, Terraform will refuse to destroy the resource, preventing accidental deletion of public cloud projects. Users must explicitly set deletion_protection = false and run terraform apply before the resource can be destroyed.

This is a client-side only implementation since the OVH API does not support deletion protection. The value is stored in Terraform state, so it also protects against removal of the resource block from the configuration — unlike Terraform's built-in prevent_destroy lifecycle meta-argument, which only blocks terraform destroy but does not prevent deletion when the resource block is removed from the config.

Fixes #1269

Type of change

• New feature (non-breaking change which adds functionality)

How Has This Been Tested?

• Test A: go test ./ovh/ -run TestResourceCloudProjectDelete_deletionProtection -v

Unit test that verifies:

1. deletion_protection = true blocks deletion with an appropriate error message
2. deletion_protection = false passes the guard and proceeds to the API call

Additionally, manual testing was performed with a real cloud project:

1. Applied with deletion_protection = true
2. Confirmed terraform destroy fails with error
3. Changed to deletion_protection = false, ran terraform apply
4. Confirmed terraform destroy proceeds

Test Configuration:

• Terraform version: Terraform v1.14.3
• Existing HCL configuration used:

resource "ovh_cloud_project" "my_cloud_project" {
  ovh_subsidiary = "FR"
  description    = "my cloud project"

  deletion_protection = true

  plan {
    duration     = "P1M"
    plan_code    = "project.2018"
    pricing_mode = "default"
  }
}

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings or issues
• I have added acceptance tests that prove my fix is effective or that my feature works
• New and existing acceptance tests pass locally with my changes
• I ran successfully go mod vendor if I added or modify go.mod file