-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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
Adding transforms migration guide for 9.0 #117353
Adding transforms migration guide for 9.0 #117353
Conversation
Documentation preview: |
Pinging @elastic/ml-core (Team:ML) |
Pinging @elastic/es-docs (Team:Docs) |
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.
I left a few comments mostly suggesting to use the shared attributes (for example, {transforms} for transforms
) and some suggestions to cut the word count. Otherwise, LGTM, thank you for writing it up!
docs/reference/migration/migrate_9_0/transforms-migration-guide.asciidoc
Outdated
Show resolved
Hide resolved
docs/reference/migration/migrate_9_0/transforms-migration-guide.asciidoc
Outdated
Show resolved
Hide resolved
docs/reference/migration/migrate_9_0/transforms-migration-guide.asciidoc
Outdated
Show resolved
Hide resolved
docs/reference/migration/migrate_9_0/transforms-migration-guide.asciidoc
Outdated
Show resolved
Hide resolved
docs/reference/migration/migrate_9_0/transforms-migration-guide.asciidoc
Outdated
Show resolved
Hide resolved
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.
LGTM!
@elasticmachine merge upstream |
💔 Backport failed
You can use sqren/backport to manually backport by running |
Adding a transforms migration guide for users migrating from 8.18 to 9.0. This guide currently only contains migration steps for updating deprecated transforms roles but we will be updating it over time to include other migration steps for other breaking changes. For now this is being added as a standalone page to be able to provide a link to it to in our deprecation warnings. Later on, we will revisit if we need to link it from any other pages.