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

Update legacy URL alias developer guide #176164

Closed
jeramysoucy opened this issue Feb 2, 2024 · 1 comment · Fixed by #199969
Closed

Update legacy URL alias developer guide #176164

jeramysoucy opened this issue Feb 2, 2024 · 1 comment · Fixed by #199969
Assignees
Labels
docs Feature:Security/Sharing Saved Objects Platform Security - Sharing Saved Objects feature Team:Security Team focused on: Auth, Users, Roles, Spaces, Audit Logging, and more!

Comments

@jeramysoucy
Copy link
Contributor

jeramysoucy commented Feb 2, 2024

doc: docs/developer/advanced/legacy-url-aliases.asciidoc

"This doc was specifically crafted to support migration from 7.x to 8.0 where the migration from single-namespace to multi-namespace happened, and when Kibana automatically created these legacy URL aliases to not break user's "markdown links" and browser bookmarks."

The doc should be updated to clarify when legacy URL aliases are generated. Which is in two cases:

  1. During migration, when an object's namespace type is being converted from single-namespace to a multi-namespace type. If the object resides in a non-default space, it gets a new ID and a legacy URL alias is generated.
  2. During copy/import of saved objects, when any object requires a new ID AND compatibilityMode is enabled (see Support generating legacy URL aliases for objects that change IDs during import. #149021)
@jeramysoucy jeramysoucy added Team:Security Team focused on: Auth, Users, Roles, Spaces, Audit Logging, and more! docs Feature:Security/Sharing Saved Objects Platform Security - Sharing Saved Objects feature labels Feb 2, 2024
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-security (Team:Security)

@jeramysoucy jeramysoucy self-assigned this Nov 12, 2024
jeramysoucy added a commit that referenced this issue Nov 14, 2024
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.
CAWilson94 pushed a commit to CAWilson94/kibana that referenced this issue Nov 18, 2024
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.
CAWilson94 pushed a commit to CAWilson94/kibana that referenced this issue Nov 18, 2024
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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs Feature:Security/Sharing Saved Objects Platform Security - Sharing Saved Objects feature Team:Security Team focused on: Auth, Users, Roles, Spaces, Audit Logging, and more!
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants