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

instance_termination_action must be set for compute-vm spot instances #778

Merged
merged 6 commits into from
Aug 20, 2022

Conversation

sruffilli
Copy link
Collaborator

google_compute_instance and google_compute_instance_template having provisioning_model = SPOT must have scheduling.instance_termination_action set to either STOP or DELETE.

Even if the field is optional, not having it set triggers the following behaviors:

  • google_compute_instance -> state flapping
  • google_compute_instance_template -> state flapping triggering an error, as update is not supported.

This PR sets scheduling.instance_termination_action=STOP (which is the default).
#777 tracks the ability to optionally customize instance_termination_action

@sruffilli sruffilli requested review from juliocc and ludoo August 20, 2022 15:09
@sruffilli sruffilli changed the title instance_termination_action must be set forcompute-vm spot instances instance_termination_action must be set for compute-vm spot instances Aug 20, 2022
@ludoo
Copy link
Collaborator

ludoo commented Aug 20, 2022

Can you also address #777 here?

modules/compute-vm/main.tf Outdated Show resolved Hide resolved
@sruffilli sruffilli merged commit a29faa7 into master Aug 20, 2022
@sruffilli sruffilli deleted the sruffilli-instance-termination-action branch August 20, 2022 16:37
@ludoo ludoo added on:modules incompatible change Pull request that breaks compatibility with previous version labels Aug 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
incompatible change Pull request that breaks compatibility with previous version on:modules
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants