-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support pubsub schema updates #13997
Support pubsub schema updates #13997
Comments
@rileykarson: would pull requests to get this feature upstream be welcome? At my workplace we are making use of this provider to manage schemas and would love to have the possibility of evolving them. |
I will be making the updates needed for this. |
Hi ! I also need this issue resolved not only to support newest pub/sub schema evolution feature but also essentially because the terraform import command ignores the definition field, thus detecting unplanned changes. So, it is currently unusable for my use case. Steps I used to reproduce:
terraform import -var-file=$HOME/.../src/environments/production.tfvars module.my_module.google_pubsub_schema.records_schema projects/prod-project-xxx/schemas/records-schema
resource "google_pubsub_schema" "records_schema" { timeouts {} KO 1: The definition field is ignored. To validate I check the pub sub schema in GCloud { In the end I cannot import the full pub/sub schema ; this issue would allow me to add a revision which may also fix it. Thanks! |
Ah- I see there's a community PR, let's let that play out. |
Hi! I'm really glad this is being worked on, I need this for my current workflow. I see that the PR has been merged. How do I opt-in to this new behavior? I am still getting full-replacement by Terraform when I change the schema. Edit: Oh, likely need a new release of terraform-provider-google eh, Ill wait! |
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. |
Community Note
Description
PubSub recently added support for pubsub schema revisions -- Release Notice
Right now changing the a pubsub schema is a destructive action (even adding a new field which is a backwards compatible change typically). With the new feature, you can make those changes without having to recreate the pubsub topic.
New or Affected Resource(s)
Potential Terraform Configuration
Separate Resource
Built into google_pubsub_schema
I do not really have a preference, I just want to be able to evolve schemas without destroying my topic.
References
The text was updated successfully, but these errors were encountered: