Replies: 1 comment
-
A second thought is - there's no harm in adding it for "Validate" workflow too, as it at least allows us to verify the deploy order in PR before we merge. So I advocate we add it into "Validate" too |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Issue
I'm currently using repo bootstrapped from https://github.com/Azure/AzOps-Accelerator
I had to redeploy some assets, so I added them all back in in bulk to deploy to one resource group. This was achieved by taking 3 templates I had and adding it to a folder. After merging this to
main
, the 3 templates deploy. Unfortunately, the 3 do not deploy necessarily in the sequence I want.I think it would be a good idea to allow custom sorting of templates to deploy within Push. I have tested this by modifying
az-platform-ops/.github/workflows/push.yml
manually, but this is flakey esp with theAzOps - Update
workflow trying to remove it. Plus if it isn't included, there may be a reason for it that I'm keen to learn.PS: I thought this would be great for validate too - but
WhatIf
obviously doesn't work well for this scenario as we can't track deployment of each template and its effect if there is a dependency in the next template. This opens up an issue imo - something may appear to fail validation even though thepush
would succeed because it requires actual deployment of templates in sequence to resolve dependencies properly. I don't know the answer to this (it feels like a damned-if-I-do-damned-if-I-don't situation). Again, open to hear thoughts on thatBeta Was this translation helpful? Give feedback.
All reactions