-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Update legacy url aliases developer documentation #199969
Update legacy url aliases developer documentation #199969
Conversation
A documentation preview will be available soon. Request a new doc build by commenting
If your PR continues to fail for an unknown reason, the doc build pipeline may be broken. Elastic employees can check the pipeline status here. |
💚 Build Succeeded
History
|
Pinging @elastic/kibana-security (Team:Security) |
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.
Looks good, thanks!
Closes elastic#176164 ## Summary Updates the legacy URL aliases developer documentation to cover the two applicable scenarios where legacy URL aliases would be generated. Formerly, the document was only concerned with saved object namespace type migrations, but aliases can now also be generated when copying or importing saved objects.
Closes elastic#176164 ## Summary Updates the legacy URL aliases developer documentation to cover the two applicable scenarios where legacy URL aliases would be generated. Formerly, the document was only concerned with saved object namespace type migrations, but aliases can now also be generated when copying or importing saved objects.
Closes #176164
Summary
Updates the legacy URL aliases developer documentation to cover the two applicable scenarios where legacy URL aliases would be generated. Formerly, the document was only concerned with saved object namespace type migrations, but aliases can now also be generated when copying or importing saved objects.