-
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
Improve docs for unknown saved object types #125253
Conversation
…ved object types"" This reverts commit 580d61d.
💚 Build Succeeded
History
To update your PR or re-run it, just comment with: |
Pinging @elastic/kibana-core (Team:Core) |
be39cb4
to
03c762c
Compare
@@ -4,8 +4,8 @@ | |||
|
|||
Each time you upgrade {kib}, an upgrade migration is performed to ensure that all <<managing-saved-objects,saved objects>> are compatible with the new version. | |||
|
|||
NOTE: To help you prepare for the upgrade to 7.0.0, 6.7.0 includes an https://www.elastic.co/guide/en/kibana/6.7/upgrade-assistant.html[*Upgrade Assistant*]. | |||
To access the assistant, go to *Management > 7.0 Upgrade Assistant*. | |||
NOTE: To help you prepare for the upgrade to 8.0.0, 7.17.0 includes an https://www.elastic.co/guide/en/kibana/7.17/upgrade-assistant.html[*Upgrade Assistant*]. |
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.
Is this note needed? Given the edits, it says the same thing as the first paragraph of the file. Instead, you could put the link to Upgrade Assistant in the first paragraph.
@@ -1,8 +1,8 @@ | |||
[[upgrade-standard]] | |||
=== Standard upgrade |
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.
This content is no long in the doc.
You might also want to look at Upgrade Kibana in the Installation and Upgrade Guide. This doc contains a note about saved object migrations.
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.
As discussed offline there's a discrepancy in our docs between 7.x and 8.x and the structure isn't optimal for 8.x but I will address that in a follow-up
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.
Co-authored-by: gchaps <[email protected]> Co-authored-by: Christiane (Tina) Heiligers <[email protected]>
Co-authored-by: gchaps <[email protected]>
💚 Build Succeeded
History
To update your PR or re-run it, just comment with: |
* Revert "Revert "Docs for preventing migrations failing for unknown saved object types"" This reverts commit 580d61d. * Fix links and versions for note to use UA * Migration docs: remove content related to 6.x versions * Upgrade docs, remove content for upgrading from v4/v5 * Link to 7.17 upgrade assistant * Apply suggestions from code review Co-authored-by: gchaps <[email protected]> Co-authored-by: Christiane (Tina) Heiligers <[email protected]> * Update docs/setup/upgrade/upgrade-migrations.asciidoc Co-authored-by: gchaps <[email protected]> Co-authored-by: gchaps <[email protected]> Co-authored-by: Christiane (Tina) Heiligers <[email protected]> (cherry picked from commit f3b01b6)
* Revert "Revert "Docs for preventing migrations failing for unknown saved object types"" This reverts commit 580d61d. * Fix links and versions for note to use UA * Migration docs: remove content related to 6.x versions * Upgrade docs, remove content for upgrading from v4/v5 * Link to 7.17 upgrade assistant * Apply suggestions from code review Co-authored-by: gchaps <[email protected]> Co-authored-by: Christiane (Tina) Heiligers <[email protected]> * Update docs/setup/upgrade/upgrade-migrations.asciidoc Co-authored-by: gchaps <[email protected]> Co-authored-by: gchaps <[email protected]> Co-authored-by: Christiane (Tina) Heiligers <[email protected]> (cherry picked from commit f3b01b6)
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
* Revert "Revert "Docs for preventing migrations failing for unknown saved object types"" This reverts commit 580d61d. * Fix links and versions for note to use UA * Migration docs: remove content related to 6.x versions * Upgrade docs, remove content for upgrading from v4/v5 * Link to 7.17 upgrade assistant * Apply suggestions from code review Co-authored-by: gchaps <[email protected]> Co-authored-by: Christiane (Tina) Heiligers <[email protected]> * Update docs/setup/upgrade/upgrade-migrations.asciidoc Co-authored-by: gchaps <[email protected]> Co-authored-by: gchaps <[email protected]> Co-authored-by: Christiane (Tina) Heiligers <[email protected]> (cherry picked from commit f3b01b6) Co-authored-by: Rudolf Meijering <[email protected]>
* Revert "Revert "Docs for preventing migrations failing for unknown saved object types"" This reverts commit 580d61d. * Fix links and versions for note to use UA * Migration docs: remove content related to 6.x versions * Upgrade docs, remove content for upgrading from v4/v5 * Link to 7.17 upgrade assistant * Apply suggestions from code review Co-authored-by: gchaps <[email protected]> Co-authored-by: Christiane (Tina) Heiligers <[email protected]> * Update docs/setup/upgrade/upgrade-migrations.asciidoc Co-authored-by: gchaps <[email protected]> Co-authored-by: gchaps <[email protected]> Co-authored-by: Christiane (Tina) Heiligers <[email protected]> (cherry picked from commit f3b01b6) Co-authored-by: Rudolf Meijering <[email protected]>
Summary
Expand 8.0 docs to explain the new behaviour from #118300
Checklist
Delete any items that are not applicable to this PR.
Risk Matrix
Delete this section if it is not applicable to this PR.
Before closing this PR, invite QA, stakeholders, and other developers to identify risks that should be tested prior to the change/feature release.
When forming the risk matrix, consider some of the following examples and how they may potentially impact the change:
For maintainers