Open worldspawn opened 9 months ago
Looks like AgentPool
is actually an azure-native resource; I think this behavior is all specific to azure so moving the issue there.
To clarify, it looks like you're able to create the autoscaling AgentPool
by just setting EnableAutoScaling
, but when you update an AgentPool
that was created with EnableAutoScaling = false
, you have to set both EnableAutoScaling
and Type = AgentPoolType.VirtualMachineScaleSets
for it to update correct?
What happened?
Trying to create an AgentPool where
EnableAutoScaling
is true. MaxCount, MinCount are set. Pulumi fails withExample
Output of
pulumi about
Additional context
Specifying all 3 values is accepted on create:
Then set EnableAutoScaling to false
Fails with
So if we remove MinCount and MaxCount
Succeeds. Now a not-auto-scaled pool with 0 instances. Lets go back to auto scaling:
Fails with
Hmm... lets set that then
And it works. I didn't need to set this when I created the resource as an auto-scaling agent pool and need to when changing from non auto to auto. I get the sense the provider has done "something" for me when I created the resource and that same something is not happening in this update scenario.
Contributing
Vote on this issue by adding a 👍 reaction. To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).