Add support for Pub/Sub schema evolution

[irfanhabib]

Checklist

• [X] I did not find a related open enhancement request.
• [X] I understand that enhancement requests filed in the GitHub repository are by default low priority.
• [X] If this request is time-sensitive, I have submitted a corresponding issue with GCP support.

Describe the feature or resource

GCP recently launched Cloud Pub/Sub schema evolution. This feature currently is not supported in config-connector, as schema revisions cannot be specified when creating a topic.

Currently only a schemaRef can be specified as documented here. To support this feature we additionally need to set the firstRevisionId and lastRevisionId (as documented here

Are there plans to add support for this?

Additional information

https://cloud.google.com/config-connector/docs/reference/resource-docs/pubsub/pubsubtopic#schema

Importance

This is currently a blocker for us as we use config-connector to manage our GCP resources.

[diviner524]

@irfanhabib This Config Connector resource is implemented based on Terraform Provider. This means the support for firstRevisionId and lastRevisionId will eventually be reflected in Config Connector after these two fields are supported in Terraform Provider.

https://registry.terraform.io/providers/hashicorp/google-beta/latest/docs/resources/pubsub_topic

If this is a blocker for you please consider submitting a GCP support case so we can work with internal partner teams and expedite the process.