ovh/terraform-provider-ovh

Describe the bug When trying to create a postgres cluster (business 2 nodes), OVH returns error message that provides zero meaningful information: "OVHcloud API error (status code 404): Client::NotFound::NoMatchingCompute: "no compute matches your expectations, please refer to the availability endpoint" Terraform Version Terraform v1.16.0 OVH Terraform Provider Version 2.19.0 Affected Resource(s) Please list the resources as a list, for example: ovh_cloud_project_database Terraform Configuration Files resource "ovh_cloud_project_database" "postgres" { service_name = var.service_name description = "${var.name}-postgres" engine = "postgresql" version = var.postgres_version plan = var.postgres_plan flavor = var.postgres_flavor dynamic "nodes" { for_each = range(local.postgres_node_count) content { region = var.region #network_id = var.network_id #subnet_id = var.subnet_id } } backup_regions = var.backup_regions backup_time = var.backup_time maintenance_time

Describe the bug When a ovh_cloud_project_kube Cluster resource is deleted outside of TF, but still exists in the tfstate, the cluster is correctly accounted for in the planning, the ovh_cloud_project_kube_iprestrictions however become a destroy/create, which tries to destroy the restriction on the not anymore existing cluster, which correctly results in an HTTP 404, but then causes the job to fail. It should rather: Conclude the ip restriction is already gone, when the cluster is gone Consider a 404 = destroyed for resources Terraform Version OpenTofu v1.11.8 on linux_amd64 OVH Terraform Provider Version v2.19.0 Affected Resource(s) Please list the resources as a list, for example: ovh_cloud_project_kube ovh_cloud_project_kube_iprestrictions Expected Behavior Apply job skips destruction of old, non existing iprestriction and just creates a new one on the newly created cluster Actual Behavior Provider tries destroying a non existing iprestriction resource and fails on HTTP 404 Step