Cheng Lu

I think this bug might be long before 1.5.0 because there were tons of the rate limiting errors in my logs dated on July 31st which was the oldest I...

also tested this issue happens to any compartment created under the root compartment as well. And I can confirm this is not a permission issue by taking off and re-applying...

Trace Log: ``` 2022-09-23T10:02:05.862-0400 [INFO] Terraform version: 1.3.0 2022-09-23T10:02:05.862-0400 [DEBUG] using github.com/hashicorp/go-tfe v1.9.0 2022-09-23T10:02:05.862-0400 [DEBUG] using github.com/hashicorp/hcl/v2 v2.14.0 2022-09-23T10:02:05.862-0400 [DEBUG] using github.com/hashicorp/terraform-config-inspect v0.0.0-20210209133302-4fd17a0faac2 2022-09-23T10:02:05.862-0400 [DEBUG] using github.com/hashicorp/terraform-svchost v0.0.0-20200729002733-f050f53b9734 2022-09-23T10:02:05.862-0400 [DEBUG]...

ok. looks I missed the enable_delete = true in the compartment resource block. So the bug is that terraform should NOT report the destroy as successful and should error out...

It will be great to have this idempotency check feature as it's being around for long time for kitchen ansible and terratest. Definitely need an option to opt-out as some...

The following workaround works too and it would be great to integrate this into the code so that we don't have to write the test case for each test module...

got the same issue on alpine docker image. ruby version is 3.2.2. inspec-bin version 5.21.29 installed fine, but 5.22.3 failed with dependency error.