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
This means that if we want to force a redeployment of all queues for emergency situations such as dotnet/arcade#13774, we need to make changes to important queue specific information, make a silly change to the ARM template, or delete the label from every resource group.
We should add a mechanism to force the deployment of all queues and scale sets, ignoring the existing deployment labels.
Release Note Category
Feature changes/additions
Bug fixes
Internal Infrastructure Improvements
Release Note Description
The text was updated successfully, but these errors were encountered:
When we finish deploying a VM scale set, we add a label to the resource group where the scale set resource is located. the value of this label is computed by this algorithm: https://dnceng.visualstudio.com/internal/_git/dotnet-helix-machines?path=/src/DeployQueues/QueueManager.cs&version=GBmain&line=847&lineEnd=848&lineStartColumn=1&lineEndColumn=1&lineStyle=plain&_a=contents
This means that if we want to force a redeployment of all queues for emergency situations such as dotnet/arcade#13774, we need to make changes to important queue specific information, make a silly change to the ARM template, or delete the label from every resource group.
We should add a mechanism to force the deployment of all queues and scale sets, ignoring the existing deployment labels.
Release Note Category
Release Note Description
The text was updated successfully, but these errors were encountered: