status check in a multi-region setup
If we have a multi-region setup, West Europe and Sweden Central and they are pointing to the same GitOps repository and folder/kustomization, then by default the status check would look at one of their notifications.
The notifications will be sent using the genre fluxcd (in Azure DevOps) and the name kustomization/apps-dev as an example. If we did this in a multi-region setup, the notification should use a names like kustomization/apps-we-dev and kustomization/apps-sc-dev.
The status check is hard coded to check [group]-[env] right now and wouldn't support checking all of them.
Not an issue right now, but came up as I was working on the gitops-promotion support for azcagit.
The critical bit here is not so much what the branches are called, but more how many fluxes there are out there. I.e, how many Flux reconciliations should the status check wait for? It would be great if we can set this up so you don't need to enumerate your regions in your gitops-promotion.yaml.
@bittrance I think I understand what you mean, but how would we go about that? If one region haven't sent a notification, do we want to fail or succeed the status check?