You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
resource"tfe_workspace_run""runs" {
for_each=var.workspacesworkspace_id=tfe_workspace.workspace[each.key].iddynamic"apply" {
for_each=each.value.queue_all_runs==false?toset([]) :toset([1]) # apply if queue_all_runs is null or truecontent {
manual_confirm=falsewait_for_run=trueretry_attempts=5retry_backoff_min=5
}
}
destroy {
manual_confirm=falsewait_for_run=trueretry_attempts=3retry_backoff_min=10
}
}
Debug Output
See screenshot
Expected Behavior
After removing the resource from the configuration the run settings should be removed from the workspace without altering the workspace resources
Actual Behavior
a destroy plan is queued in the workspace and apply is stuck for several minutes and end with an error message, see screenshot.
Additional Context
we applied tfe_workspace_run on around 80 existing workspaces, 2 succeeded (after a long time, +1 hour), 8 got stuck at applying and the other workspaces got queued, pending apply. All plans were successful. The queued and applying runs had to be cancelled through the run api.
When removing the runs on the 2 workspaces where it succeeded we observed this behaviour.
The text was updated successfully, but these errors were encountered:
Terraform Cloud/Enterprise version
Terraform Cloud Plus
Terraform version
Terraform Configuration Files
Debug Output
See screenshot
Expected Behavior
After removing the resource from the configuration the run settings should be removed from the workspace without altering the workspace resources
Actual Behavior
a destroy plan is queued in the workspace and apply is stuck for several minutes and end with an error message, see screenshot.
Additional Context
we applied tfe_workspace_run on around 80 existing workspaces, 2 succeeded (after a long time, +1 hour), 8 got stuck at applying and the other workspaces got queued, pending apply. All plans were successful. The queued and applying runs had to be cancelled through the run api.
When removing the runs on the 2 workspaces where it succeeded we observed this behaviour.
The text was updated successfully, but these errors were encountered: