-
Notifications
You must be signed in to change notification settings - Fork 138
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Consolidate spoke network module creation #493
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Benefit/Result/Outcome
So that changes are applied universally to all spokes when changes are made and reduce the likelihood of introducing errors or variance between spokes.
Description
Today, we have a module declaration for each of the spoke resource groups, networks, policy assignments, logging activities, and security center enrollments, like this:
missionlz/src/bicep/mlz.bicep
Lines 18 to 46 in b74db11
That's a lot of duplication and surface area and risk that changes could differ for each spoke.
Instead, we could use Bicep's loop function to declare those modules just once and provision them the same way for each spoke like this:
missionlz/src/bicep/mlz.bicep
Lines 17 to 25 in 78fe8c7
Acceptance Criteria
The text was updated successfully, but these errors were encountered: