You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 the 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 the issue is assigned to a user, that user is claiming responsibility for the issue. If the issue is assigned to "hashibot", a community member has claimed the issue already.
Some solutions which aren't running in GKE, however, are managed through terraform. One usecase is to create a subscription to an existing topic for a legacy application.
There doesn't, however, seem to be any data sources for pubsub topics or the other pubsub resources either.
I would like a data source that permits creating a subscription to a topic which isn't managed by terraform. Once at it, it might be a good idea to create data sources for the other pubsub resources as well.
Defining the topic both in config connector and as a resource in terraform doesn't seem like a good idea, since one should probably keep the two in sync in order to avoid conflicts.
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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 [email protected]. Thanks!
ghost
locked as resolved and limited conversation to collaborators
Nov 6, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Community Note
Description
We're creating some pubsub topics by using gke config connector(https://cloud.google.com/config-connector/docs/overview). This allows us to apply applications and their dependencies through kubernetes manifests.
Some solutions which aren't running in GKE, however, are managed through terraform. One usecase is to create a subscription to an existing topic for a legacy application.
There doesn't, however, seem to be any data sources for pubsub topics or the other pubsub resources either.
I would like a data source that permits creating a subscription to a topic which isn't managed by terraform. Once at it, it might be a good idea to create data sources for the other pubsub resources as well.
Defining the topic both in config connector and as a resource in terraform doesn't seem like a good idea, since one should probably keep the two in sync in order to avoid conflicts.
New or Affected Resource(s)
Potential Terraform Configuration
New or Affected Resource(s)
Potential Terraform Configuration
References
The text was updated successfully, but these errors were encountered: