-
Notifications
You must be signed in to change notification settings - Fork 21.8k
Add migrating between resources section #127497
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
base: main
Are you sure you want to change the base?
Conversation
@maciejporebski : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR adds documentation to explain the behavior and limitations when migrating custom domains between Azure Static Web Apps instances, specifically addressing the constraint that domains can only be bound to one resource per slice.
- Adds a new section explaining domain binding limitations between Static Web Apps instances
- Provides guidance on identifying which slice a resource belongs to
- Offers solutions for migrating domains between instances in the same slice
Co-authored-by: Copilot <[email protected]>
Learn Build status updates of commit d22a886: ✅ Validation status: passed
For more details, please refer to the build report. |
Learn Build status updates of commit 0057091: ✅ Validation status: passed
For more details, please refer to the build report. |
Can you review the proposed changes? Important: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
Add a section to cover behaviour experienced when attempting to bind the same hostname to multiple SWA resources.