Open luckeyca opened 1 year ago
Thank you for reporting the issue. We observed the affected resources are not provided in the description or it's incorrect. We request you to add it in issue description as mentioned in below format. Example: affected_resources = oci_core_instance , oci_core_instances
If it's not related to any particular resource then mention affected resource as terraform. Example: affected_resources = terraform
As this works through automation, request you to follow exact syntax.
Community Note
Terraform Version and Provider Version
Affected Resource(s)
oci_core_vcn
All. Issue should be at the provider level in general, not specific resource
Terraform Configuration Files
test deployment shell script mimicking ci/cd automated deployment, followed by automated testing with auto-destroy at the #### end. please use this script to reproduce the issue. detailed instruction is in the "step-to-reproduce" section below
test terraform code main.tf (please add a valid parent compartment id for compartment resource and then use the shell script above to deploy):
Debug Output
Panic Output
N/A
Expected Behavior
After terraform apply finishes successfully, all resources reported to be created successfully should actually be created and be queried using cli commands.
Actual Behavior
After terraform apply finishes successfully, using oci cli to query the resources immediately will resulted in empty query results.
Steps to Reproduce
the two variables: vcn_parent_compartment_ocid and internet_gateway_route_table_ocid will randomly shows either valid ocid, or error messages as "query returned empty result....." messages.
This shouldn't be the case as terraform provider always should report the correct resource creation status before exit.
Important Factoids
References