Skip to content
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

Remove long form name behavior for pubsub subscriptions #4508

Closed
paddycarver opened this issue Sep 19, 2019 · 6 comments
Closed

Remove long form name behavior for pubsub subscriptions #4508

paddycarver opened this issue Sep 19, 2019 · 6 comments
Assignees
Milestone

Comments

@paddycarver
Copy link
Contributor

I'm not sure on the background of this one, but it came up in our discussion of 3.0.0 goals. I believe you can currently specify two versions of the pubsub subscription name, and the long one is undesirable for some reason, and so we want to stop supporting it. @danawillow, assigning this to you so you can assign it to Cameron when they get commit access.

@rileykarson
Copy link
Collaborator

rileykarson commented Oct 21, 2019

I forget the exact context, but we have custom code to allow specifying something- I think the name- as either the shortname or long name. We kept it for BC reasons when MM-ifying the resource, but we can remove some of that behaviour (and the underlying custom code) in 3.0.0.

Edit: Actually, I think the field was topic. See hashicorp/terraform-provider-google-beta#432 (comment)

@danawillow
Copy link
Contributor

topic is currently doing compareSelfLinkOrResourceName which seems perfectly reasonable for it to do. name is comparePubsubSubscriptionBasename which seems like the actual one to get rid of (and instead treat it like the other newer-style APIs where the name field is always short). Does that sound like what you were thinking, @rileykarson?

@rileykarson
Copy link
Collaborator

Ah- yep, I think that was it.

@danawillow
Copy link
Contributor

Cool. Since @c2thorn has plenty of other things on his plate right now, I'm going to go ahead and take this since it's pretty quick.

@rileykarson
Copy link
Collaborator

Closed in linked issue ("Fixes: " doesn't work in non-primary branches)

@ghost
Copy link

ghost commented Dec 6, 2019

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 ghost locked and limited conversation to collaborators Dec 6, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants