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

provider/google-cloud add queue-scaling support to autoscaling_policy in resource google_compute_autoscaler #14453

Closed
bmabey opened this issue May 12, 2017 · 4 comments

Comments

@bmabey
Copy link

bmabey commented May 12, 2017

Google Cloud has an alpha feature for autoscaling based on a queue-based workload. Could the google_compute_autoscaler resource be updated so that the autoscaling_policy includes the relevant parameters for queue-based autoscaling?

Here are the docs for the new queue-based scaling feature:
https://cloud.google.com/compute/docs/autoscaler/scaling-queue-based

@danawillow
Copy link
Contributor

Hi @bmabey, thanks for the FR! Right now Terraform doesn't support alpha/beta APIs due to some technical limitations, but we're planning on resolving those within the next few months. In the meantime, leaving this open so others can 👍 the issue if that's something they'd like to see as well.

@bmabey
Copy link
Author

bmabey commented May 18, 2017

Thanks @danawillow. Is there an issue around the alpha/beta support you could point me to?

@danawillow
Copy link
Contributor

There is now: #14742

@ghost
Copy link

ghost commented Apr 9, 2020

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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@ghost ghost locked and limited conversation to collaborators Apr 9, 2020
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

4 participants