Skip to content

fix: default Azure dual-pool autoscaling - #659

Open
adamrtalbot wants to merge 1 commit into
masterfrom
agent/fix-azure-dual-pool-autoscale
Open

fix: default Azure dual-pool autoscaling#659
adamrtalbot wants to merge 1 commit into
masterfrom
agent/fix-azure-dual-pool-autoscale

Conversation

@adamrtalbot

@adamrtalbot adamrtalbot commented Aug 7, 2026

Copy link
Copy Markdown
Contributor

Why

Azure Batch Forge dual-pool compute environments omitted headPool.autoScale and workerPool.autoScale when the corresponding disable flags were not supplied. This allowed the resulting pools to behave as fixed-size pools even though the CLI presents autoscaling as the default.

Closes #658.

What

  • Explicitly set autoscaling to true for head and worker pools by default.
  • Preserve --head-no-auto-scale and --worker-no-auto-scale behavior by setting the selected pool to false.
  • Add request-payload coverage for default and explicitly disabled autoscaling.
  • Update the existing dual-pool boot-disk payload expectation.

Impact

Dual-pool VM counts are now serialized as autoscaling maximums by default, matching the CLI help and single-pool behavior. Existing users who pass the disable flags retain fixed-size pools.

Explicitly enable autoscaling for Azure Batch Forge head and worker
pools when their disable flags are omitted.

Closes #658
@adamrtalbot
adamrtalbot marked this pull request as ready for review August 7, 2026 11:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Azure dual-pool autoscale defaults are omitted

1 participant