-
Notifications
You must be signed in to change notification settings - Fork 85
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
demo: add Azure remote demo #295
Conversation
demo/remote/azure/terraform/modules/azure-hashistack/templates/azure_autoscaler.nomad
Outdated
Show resolved
Hide resolved
@jrasell any ideas on how to make Terraform destroy the jobs first? As it is, Terraform will destroy the VMs first and then try to to destroy the jobs, but it will timeout. I tried the new |
@lgfa29 I would expect the fact the jobs module has a requirement on an output of the cluster module to create the correct dependancy chain. Failing that and providing we use TF 0.13, again I would expect it to create the correct dependancy chain between the two modules. Lets look at this online later, hopefully we can figure out a nice solution other than having to do targeted destroys. |
2c5bc2a
to
cad861c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
💯 🏆 🥇
This PR adds cluster scaling demo on Azure using the a VMSS instance. It follows a new folder structure to better organize files per cloud provider. A following PR will adapt the AWS demo to the same structure.
It also updates the provider version constraint in the
shared-nomad-jobs
module so we can usedepends_on
between thehashistack_cluster
andhashistack_jobs
. Without this explicit dependency, Terraform would try to destroy the jobs after the cluster is already gone.