Open
Description
What kind of contribution is this issue about?
MMv1-based resource
Details
Twice this week I've worked on bugs (#21893 and #21026, the latter of which also implicates #12944, #13217, and #16478) that were caused by inconsistent usage of region and location where product.yaml used one and one or more resources used the other. At a minimum some process (the compiler maybe?) could check URL patterns to confirm they all use the same identifier, and that it matches a field declared in each resources' parameters.
What's particularly annoying is that in both cases our integration tests passed because region and location are set at the provider level, masking the problem.
References
No response