Clarify if multiple `runners.autoscaler.policy` elements are supported or not with `docker-autoscaler` executor
Problem to solve
Clarify if multiple runners.autoscaler.policy
elements are supported or not with docker-autoscaler
executor
Further details
With the following settings in config.toml
:
[[runners.autoscaler.policy]]
idle_count = 1
idle_time = "30m0s"
periods = ["* 8-15 * * mon-fri"]
[[runners.autoscaler.policy]]
idle_count = 0
idle_time = "0s"
periods = ["* * * * *"]
...I seem to get no servers created when the runner is idle, despite the local time matching the first periods
specification.
In the
[runners.machine]
settings, you can add multiple[[runners.machine.autoscaling]]
sections, each one with its ownIdleCount
,IdleTime
,Periods
andTimezone
properties. A section should be defined for each configuration, proceeding in order from the most general scenario to the most specific scenario.All sections are parsed. The last one to match the current time is active. If none match, the values from the root of
[runners.machine]
are used.
Proposal
Make it clear in the documentation how this works, and ideally support the same semantics with the docker-autoscaler
executor as was previously available.