MicrosoftDocs
Clarify routing rules order in documentation for container apps rule based routing
Added a note to clarify that the order of routing rules matter in the configuration.
@simonbjorzen-ts : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.
![prmerger-automator[bot] avatar](https://avatars.githubusercontent.com/u/22479449?v=4 "Published by a pub.dev verified publisher"){kind=small}
Learn Build status updates of commit 667152f:
:warning: Validation status: warnings
| File | Status | Preview URL | Details |
|---|---|---|---|
| articles/container-apps/rule-based-routing.md | :warning:Warning | Details |
articles/container-apps/rule-based-routing.md
-
Line 142, Column 1: [Warning: code-block-indented - See documentation]
Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```).
For more details, please refer to the build report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
![learn-build-service-prod[bot] avatar](https://avatars.githubusercontent.com/in/237442?v=4 "Published by a pub.dev verified publisher"){kind=small}
Learn Build status updates of commit a105dd3:
:warning: Validation status: warnings
| File | Status | Preview URL | Details |
|---|---|---|---|
| articles/container-apps/rule-based-routing.md | :warning:Warning | Details |
articles/container-apps/rule-based-routing.md
-
Line 141, Column 1: [Warning: code-block-indented - See documentation]
Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```).
For more details, please refer to the build report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
@craigshoemaker
Can you review the proposed changes?
IMPORTANT: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged" @MicrosoftDocs/public-repo-pr-review-team
