provider/google: support alpha/beta compute APIs in addition to GA

[hashibot]

This issue was originally opened by @danawillow as hashicorp/terraform#14742. It was migrated here as part of the provider split. The original body of the issue is below.

---

Currently, only features available in the v1 version of the compute API are able to be used in Terraform. This is a general issue for support of alpha and beta APIs as well.

(assigning myself but @rileykarson will be working on this)

[rileykarson]

Given that we've closed out most of the issues in this list, I'm going to close the issue. There are a few issues left outstanding;

• Add support for folders #132 has gone GA 🎆 Feel free to 👍 the issue if it's an important feature for you!
• providers/google: Support for Node Auto-Upgrade in google_container_cluster (GKE) #79 and providers/google: Support for Node Auto-Repair in google_container_cluster (GKE) #80 are both in Container Engine, which only has a single client version.
• Add min_cpu_platform to google_compute_instance resource  #106, Feature Request: Create GPU instances #212, Add support for google_compute_instance IP Aliasing Beta feature #288 are all for google_compute_instance; that resource is being tracked by Add versioned support and Beta features to google_compute_instance #311.
• Feature Request: support rolling updates for google instance group manager. #51, provider/google-cloud add queue-scaling support to autoscaling_policy in resource google_compute_autoscaler #91 are both in Alpha. As with all of our issues; add a 👍 if it's important to you, and feel free to bump the issue when it has gone Beta!

[davidquarles]

@rileykarson Forgive me, I'm new here, but is the container/v1beta1 API an extremely recent addition, or are you saying multi-version support for the GKE API won't be supported? Specifically, I'd like to use/add the NodeTaint field to google_container_node_pool, but I'm imagining multi-version API support is a rather intricate prerequisite.

If multi-version support for the GKE client is desirable, does it merit opening a new/separate issue? Any insight is appreciated. Thanks!

[rileykarson]

Hi @davidquarles!

We created this issue to track multi-version support for just the compute API, but that had more to do with most/all of the alpha/beta feature requests being against compute at the time, and so that we could consolidate information about supporting multiple versions of those APIs in one place instead of having parts of it live in separate issues.

I would recommend filing an issue against google_container_node_pool to support NodeTaint, and to add a note in the issue body that the feature is only present at v1beta1 and not v1.

You're right that the GKE API will need to have versioned support added! Adding NodeTaint support will be a bit more involved than if it was in v1/v1beta1 was already supported by the container API. That being said, if you have a feature request for anything in GCP that the Google Provider doesn't support, regardless of the implementation details, you should file an issue against it/ 👍 it if it already exists! The team often determines what to work/focus on based on demand in the GitHub issues.

[ghost]

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!