Clarify routing rules order in documentation for container apps rule based routing #127947
Conversation
Added note about the order of routing rules in configuration.
|
@simonbjorzen-ts : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
|
Learn Build status updates of commit 667152f:
|
| File | Status | Preview URL | Details |
|---|---|---|---|
| articles/container-apps/rule-based-routing.md | 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 status updates of commit a105dd3:
|
| File | Status | Preview URL | Details |
|---|---|---|---|
| articles/container-apps/rule-based-routing.md | 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.
|
Can you review the proposed changes? IMPORTANT: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
prmerger-automator
bot
added
the
aq-pr-triaged
There was a problem hiding this comment.
Pull request overview
This PR adds documentation to clarify the importance of routing rule order in Azure Container Apps configuration. The change emphasizes that more specific path prefixes must be placed before less specific ones to ensure correct routing behavior.
Key changes:
- Added a NOTE block explaining that routing rule order is significant
- Provided an example showing how
/api/v1should come before/apito prevent incorrect matching
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| This configuration defines two routing rules for HTTP traffic. | ||
| > [!NOTE] | ||
| > The order of the routing rules matter. |
There was a problem hiding this comment.
Corrected grammar: 'matter' should be 'matters' to agree with the singular subject 'order'.
| > The order of the routing rules matter. | |
| > The order of the routing rules matters. |
3 participants
Added a note to clarify that the order of routing rules matter in the configuration.