Tomáš Kapin

@andriipatsula - please reassign this issue (and any other Roslyn / GenAPI based issues) to the new epic. - please update the description with what is the goal of this...

There are few other docs relevant to this: * [ImageFactoryCli README.md](https://dev.azure.com/dnceng/internal/_git/dotnet-helix-machines?path=%2Fsrc%2FImageFactoryCli%2FREADME.md&version=GBmain&_a=contents) * [VS2022 Upgrade Schedule](https://dev.azure.com/dnceng/internal/_wiki/wikis/DNCEng%20Services%20Wiki/899/VS2022-Upgrade-Schedule) * [OSOB Rollout](https://dev.azure.com/dnceng/internal/_wiki/wikis/DNCEng%20Services%20Wiki/561/-Needs-Updating-OSOB-rollout)

This will take ~2-3 weeks, let's convert it into a full epic.

Rotated the `github` secret as follows: * Elevated rights (JIT) for the dotnet org * Renewed the github secrets defined in the `arcade-services` repo by: ```powershell .\.dotnet\dotnet.exe secret-manager synchronize --skip-untracked...

Validated by triggering subscription for arcade to arcade-services. ```powershell darc trigger-subscriptions --ids a3e4e495-e424-4274-a65b-08dbe6b87e03 ```

Also triggered a [dotnet-arcade-services-weekly](https://dev.azure.com/dnceng/internal/_build?definitionId=993&_a=summary) pipeline run to validate and rotate the remaining secrets.

Followup for fixing incorrect links in secrets manager: https://github.com/dotnet/dnceng/issues/1913

Waiting for the arcade-services rollout to be sure. After that, delete the old certificate and client tokens from the int, local and prod maestro GH apps.

Yes, I just want to wait a bity more time till all the urgent operations things settle down. I believe the risk is very low, but still, there's no urgency...

We shouldn't delete the LoadBalancer until #3131 is solved as the Load Balancer might be needed to connect to the Service Fabric Explorer. Toi minimize the security risk, the Load...