Why is ACR not parameter

[ghost]

The process here is to create ACR then to create a cluster in the same raid group, and the code assumes the ACR was build in the ACR step and its name is known. for many use cases, the ACR may be pre-existing. Is this simply that no one has yet spent the time to pass the ACR as a parameter or is there some more fundamental reason why these need to be in the same resource group?

[ckittel]

Great question @dharvey-adv360. This walkthrough is not designed to be integrated into your own existing resources -- but instead an "end to end on-rails" experience. We've minimized the parameters to only those that cannot be clearly deduced from prior rail-bound steps. Your final IaC templates will likely be much more "flexible" than then ones listed here, accounting for your pre-existing resources (instead of creating them) in their existing locations (instead of assuming resource group or even subscription locations).

Adding too many parameters (especially when most people are staying "on the rails" adds to the noise and introduces additional points of failure along the way (due to typos, etc). The learning objective is the end architecture, and there are some pickups along the way as well. But integration into existing resources wasn't a primary goal of this learning journey.