Terraform-provider-google: Allow access to alpha GCP features
Community Note
- 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.
Description
There are often features and products that are released to alpha or EAP channels in GCP that are currently not able to be used from the terraform-provider-google. A little while ago we split the provider to allow for management per resource to beta features and endpoints via the terraform-google-provider-beta. Unfortunately some of the alpha programs are closed alphas it is not possible to take exactly the same approach to make an alpha provider. However it would be great to allow people to use alpha functionality in some capacity.
New or Affected Resource(s)
- google_alpha
References
Issues that are waiting for alpha support
- #4589
- #2605
- #4128
chrisst
All 2 comments
I'll start by saying this is a bit of a sneaky enhancement request because this is something that I've already been working on. But I am hoping to use this issue for a couple of different things:
- A place to post updates as to what we support and how to use it.
- A opportunity to solicit feedback on how people are using public alpha features to help us shape our roadmap
In regards to the first point - we are starting a pilot program for supporting alpha endpoints. In it's current iteration there is no distinction between open and closed alpha products so everything is treated as "private". This means I can't publish the provider externally but if you get in contact with your account manager they can get you access to the alpha provider. This is an alpha process for supporting alpha APIs so please understand it's not going to be advisable for use in production systems.
Quick caveat - Please keep discussion limited to public feature's only. If you want to discuss closed alpha products you should reach out to your account manager.
chrisst
on 20 Mar 2020
I would love to have this! <3
sharkymcdongles
on 4 Aug 2020
Related issues
wmuizelaar
路
4Comments
gilberthdez
路
3Comments
nthypes
路
4Comments
kaifresh
路
4Comments
mumblez
路
4Comments
Most helpful comment
I'll start by saying this is a bit of a sneaky enhancement request because this is something that I've already been working on. But I am hoping to use this issue for a couple of different things:
In regards to the first point - we are starting a pilot program for supporting alpha endpoints. In it's current iteration there is no distinction between open and closed alpha products so everything is treated as "private". This means I can't publish the provider externally but if you get in contact with your account manager they can get you access to the alpha provider. This is an alpha process for supporting alpha APIs so please understand it's not going to be advisable for use in production systems.
Quick caveat - Please keep discussion limited to public feature's only. If you want to discuss closed alpha products you should reach out to your account manager.