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 #91

Closed
hashibot opened this issue Jun 13, 2017 · 4 comments

Comments

@hashibot
Copy link

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


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

@rileykarson
Copy link
Collaborator

Linking to the general issue for alpha/beta: #93

@oralordos
Copy link

Bumping since it looks like this feature has hit beta now. This would be ideal for my workflow currently, especially with autoscaling down to 0 instances when there is nothing in the queue.

luis-silva pushed a commit to luis-silva/terraform-provider-google that referenced this issue May 21, 2019
<!-- This change is generated by MagicModules. -->
/cc @rileykarson
luis-silva pushed a commit to luis-silva/terraform-provider-google that referenced this issue May 21, 2019
<!-- This change is generated by MagicModules. -->
/cc @rileykarson
@paddycarver
Copy link
Contributor

I'm pretty sure the metric block of the google_compute_autoscaler resource's autoscaling_policy block resolves this issue. If not, please feel free to open a new issue. Thanks!

@ghost
Copy link

ghost commented Mar 28, 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 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 👉 hashibot-feedback@hashicorp.com. Thanks!

@ghost ghost locked and limited conversation to collaborators Mar 28, 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