Skip to content
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

Documentation page for nested deployment scoping rules #13617

Closed
jeskew opened this issue Mar 14, 2024 · 1 comment
Closed

Documentation page for nested deployment scoping rules #13617

jeskew opened this issue Mar 14, 2024 · 1 comment
Assignees
Labels
documentation Improvements or additions to documentation
Milestone

Comments

@jeskew
Copy link
Contributor

jeskew commented Mar 14, 2024

In #13612, a user asks if there is any documentation page describing what scopes can deploy to other scopes. The closest I could find was that in each page describing a particular deployment scope, there is a section on deploying to a different scope from that scope (e.g., deploying from RG -> other RG, subscription, or tenant scope, deploying from subscription to other subscription, RG, or tenant scope, deploying from MG -> other MG, subscription, RG or tenant scope, and deploying from tenant -> MG, subscription, or RG scope. As far as I can tell, the only forbidden scope transitions are from RG -> MG or from subscription -> MG, but we don't state that explicitly anywhere.

Should we have a dedicated page on which scope transition are allowed and which are disallowed? Or at least call out in the RG and subscription scope pages that MG-scoped deployments are forbidden?

@jeskew jeskew added the documentation Improvements or additions to documentation label Mar 14, 2024
@stephaniezyen stephaniezyen added this to the v0.27 milestone Mar 20, 2024
@mumian
Copy link
Contributor

mumian commented Mar 26, 2024

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
Status: Done
Development

No branches or pull requests

4 participants