-
Notifications
You must be signed in to change notification settings - Fork 608
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
Upgrade to Compute Engine Beta API #1478
Comments
// @omaray |
It should be on the list of stuff for us to do, yep. I'll let @omaray decide the priority, but my vote is "not very important" right now due to the impending ability to auto-generate (and the fact that this surface is enormous....) |
Sounds good. We had a feature request come up that is solved in the beta (#1470)... is it okay to gradually introduce support for the beta API, or best to do it all at once? |
That's tricky. I'd recommend avoiding a mix-and-match approach as it makes
things complicated (what if someone wants to enable the old API but isn't
OK with enabling features in another -- I don't want our answer to be "it
works but you have to enable the Beta API!")
|
Yes, Compute is not high priority right now. I need to confirm a couple of items before we can auto-generate the whole surface - but that's the end goal. Stay tuned. |
Added this to our API Implementation Tracker: #1338 |
It looks like a new GCE API is coming to town: https://cloud.google.com/compute/docs/reference/beta/
@jgeewax should we move our support from
v1
tobeta
?The text was updated successfully, but these errors were encountered: