shemau

Results 16 comments of shemau

I wonder, and this is speculation, if [name](https://github.com/IBM-Cloud/terraform-provider-ibm/blob/1b0fbb07f510ec3e255b20efa521d307c6148c94/ibm/service/codeengine/resource_ibm_code_engine_secret.go#L79) should be both `Optional` and `Computed`, since it is contained in a optional map.

The entire error message is as above. For mongo it is ```hcl Planning failed. Terraform encountered an error while generating this plan. ╷ │ Error: 1 error occurred: │ *...

```hcl 2024-04-09T09:30:13.732+0100 [INFO] provider.terraform-provider-ibm_v1.64.0: 2024/04/09 09:30:13 [Debug] Response: HTTP/2.0 200 OK Cache-Control: no-store Cf-Cache-Status: DYNAMIC Cf-Ray: 871922449e0e71fa-LHR Content-Security-Policy: frame-ancestors *.bluemix.net *.compose.fastkit *.cloud.ibm.com cloud.ibm.com Content-Type: application/json; charset=utf-8 Date: Tue, 09 Apr...

Since the error appeared to related to mongodbee, which might reasonably be enterprise edition, I tried again with `plan` set to `standard`. This time it passed. So the error is...

For `databases-for-enterprisedb` the error is ```hcl {"errors":{"deployment.host_flavor":["enterprisedb is not available on multitenant"]}}: timestamp=2024-04-09T10:28:08.837+0100 2024-04-09T10:28:08.838+0100 [ERROR] provider.terraform-provider-ibm_v1.64.0: Response contains error diagnostic: tf_req_id=b260591d-07d4-53e9-dbae-0895053af2e0 @module=sdk.proto diagnostic_detail= diagnostic_severity=ERROR diagnostic_summary="1 error occurred: * Unprocessable Entity...

I have re-created this issue on Mac OSX. Above I made the assumption that it was not stored in the state file, but that may be inaccurate. terraform.tfstate includes: ```hcl...

Whilst the terraform plan shows ```hcl Terraform used the selected providers to generate the following execution plan. Resource actions are indicated with the following symbols: ~ update in-place Terraform will...

The same error is reported ``` │ Error: Provider produced inconsistent result after apply │ │ When applying changes to module.cbr_zone_schematics.ibm_cbr_zone.cbr_zone, │ provider "provider[\"registry.terraform.io/ibm-cloud/ibm\"]" produced an │ unexpected new value:...

@zhenwan my take is that causality is the other way around. At 06:12:08 during an apply the error reported here is observed. At 06:12:13 a retry occurs (a new/second terraform...