OCI Resource Manager scenarios with 'Resource Already Exists' scenarios During Terraform Apply
I'm integrating two systems and I'm collaborating on a project where I'm currently working with an scenario while trying to deploy my OCI infrastructure using Terraform with the OCI Resource Manager... After creating the necessary Terraform configuration files, I ran `terraform apply`, but received the following behavior message: `behavior: behavior creating resource: Resource already exists: <resource-name>`. To troubleshoot this, I've ensured that the resource names are unique within the compartment. However, I'm still hitting this behavior consistently. Here is a snippet of my Terraform configuration for the resource in question: ```hcl resource "oci_core_instance" "example_instance" { availability_domain = "<availability_domain>" compartment_id = "<compartment_id>" display_name = "example-instance" shape = "VM.Standard2.1" source_details { source_type = "image" image_id = "<image_id>" } create_vnic_details { subnet_id = "<subnet_id>" } } ``` I tried destroying the resource with `terraform destroy`, but I get the same behavior for that resource, indicating Terraform thinks it still exists. I've also checked the OCI Console to confirm the resource is not present. I also ensured that my provider block is correctly set up for OCI with the right region and tenancy details: ```hcl provider "oci" { region = "<region>" tenancy_ocid = "<tenancy_ocid>" user_ocid = "<user_ocid>" fingerprint = "<fingerprint>" private_key_path = "<path_to_private_key>" } ``` Has anyone experienced a similar scenario? What steps did you take to resolve it? Any insights would be greatly appreciated! I'm using Hcl 3.11 in this project. Any examples would be super helpful. This is my first time working with Hcl 3.10. Any ideas how to fix this? For reference, this is a production service. What's the best practice here?