Failing test(s): TestAccApigeeEnvironment_apigeeEnvironmentUpdateTest

[zli82016]

Impacted tests

• TestAccApigeeEnvironment_apigeeEnvironmentUpdateTest

Affected Resource(s)

• google_apigee_environment

Failure rates

• 100% since 2024-12-17

Message(s)

resource_apigee_environment_update_test.go:23: Step 3/4 error: After applying this test step, the plan was not empty.
        stdout:
        Terraform used the selected providers to generate the following execution
        plan. Resource actions are indicated with the following symbols:
          ~ update in-place
        Terraform will perform the following actions:
          # google_apigee_environment.apigee_environment will be updated in-place
          ~ resource "google_apigee_environment" "apigee_environment" {
              ~ description       = "Apigee Environment" -> "Updated Apigee Environment Description"
              ~ display_name      = "environment-1" -> "environment-1-updated"
                id                = "organizations/tf-testlf97qcs89p/environments/tf-testlf97qcs89p"
                name              = "tf-testlf97qcs89p"
                # (5 unchanged attributes hidden)
            }
        Plan: 0 to add, 1 to change, 0 to destroy.
    testing_new.go:90: Error running post-test destroy, there may be dangling resources: exit status 1
        Error: Error when reading or editing Environment: googleapi: Error 400: the resource is locked by another operation where environment tf-testlf97qcs89p is being modified by operation: 76ef271b-4d16-4fed-963e-1f291da161f8
        Details:
        [
          {
            "@type": "type.googleapis.com/google.rpc.RequestInfo",
            "requestId": "1831474550039081249"
          }
        ]

Nightly build test history

• here

[zli82016]

Based on the API doc: https://cloud.google.com/apigee/docs/reference/apis/apigee/rest/v1/organizations.environments/update, the update should be made as a PUT, instead of PATCH