google_pubsub_schema can't be updated in place

[marcdif]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request.
• Please do not leave +1 or me too comments, they generate extra noise for issue followers and do not help prioritize the request.
• If you are interested in working on this issue or have submitted a pull request, please leave a comment.
• If an issue is assigned to the modular-magician user, it is either in the process of being autogenerated, or is planned to be autogenerated soon. If an issue is assigned to a user, that user is claiming responsibility for the issue. If an issue is assigned to hashibot, a community member has claimed the issue already.

Terraform Version

Terraform v1.1.0
on windows_amd64

• provider registry.terraform.io/hashicorp/google v4.3.0

Affected Resource(s)

• google_pubsub_schema

Terraform Configuration Files

This bug involves modifying the config file.

Before changing:

resource "google_pubsub_schema" "test_schema" {
  project = "demo-project-id"
  name    = "test-schema"
  type    = "AVRO"
  definition = "{\n  \"type\" : \"record\",\n  \"name\" : \"Avro\",\n  \"fields\" : [\n    {\n      \"name\" : \"test\",\n      \"type\" : \"int\"\n    }  ]\n}\n"
}

After changing:

resource "google_pubsub_schema" "test_schema" {
  project = "demo-project-id"
  name    = "test-schema"
  type    = "AVRO"
  definition = "{\n  \"type\" : \"record\",\n  \"name\" : \"Avro\",\n  \"fields\" : [\n    {\n      \"name\" : \"anothertest\",\n      \"type\" : \"string\"\n    }  ]\n}\n"
}

Debug Output

https://gist.github.com/marcdif/11e4b1afe4e2a9dd0ed84b009aee5234

Panic Output

Expected Behavior

Pub/Sub Schemas don't support being updated - they must be destroyed and recreated.

Actual Behavior

Terraform attempts to update-in-place the schema resource using an HTTP PUT request, which is not a valid method for this endpoint.

Steps to Reproduce

1. terraform apply with original config - Terraform will create a new schema with the provided definition.
2. terraform apply with updated config - Terraform will attempt to update the existing schema instead of destroying and recreating a new schema.

Important Factoids

N/A

References

• Feature/add pubsub schema resource #9116

[github-actions]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.