-
Notifications
You must be signed in to change notification settings - Fork 8.1k
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
[Upgrade Assistant] Doc links point to 7.17 #145092
Comments
The idea, for now, is to point users to the For the future, we can grab this detail from an API but from what I understand there are no plans to put more effort into this until the feature owners (deployment management) pick it back again from the core team. It seems this only needs a docs update: This link seems to be correct but we need to update where it points to. |
Pinging @elastic/kibana-core (Team:Core) |
@Bamieh, I think the link you shared will be fixed if we remove these lines: kibana/docs/redirects.asciidoc Lines 399 to 402 in df1a662
I also found these other places linking to 7.17:
|
…rd-coded 7.17 (elastic#147585) Co-authored-by: Lisa Cawley <lcawley@elastic.co> Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com> Fix elastic#145092 (cherry picked from commit 049d802)
…han hard-coded 7.17 (#147585) (#147780) # Backport This will backport the following commits from `main` to `8.6`: - [Updates upgrade assistant doclinks to point to current rather than hard-coded 7.17 (#147585)](#147585) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Christiane (Tina) Heiligers","email":"christiane.heiligers@elastic.co"},"sourceCommit":{"committedDate":"2022-12-19T16:19:26Z","message":"Updates upgrade assistant doclinks to point to current rather than hard-coded 7.17 (#147585)\n\nCo-authored-by: Lisa Cawley <lcawley@elastic.co>\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>\r\nFix #145092 Assistant","docs","backport:prev-minor","v8.7.0"],"number":147585,"url":"#147585 upgrade assistant doclinks to point to current rather than hard-coded 7.17 (#147585)\n\nCo-authored-by: Lisa Cawley <lcawley@elastic.co>\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>\r\nFix #145092 upgrade assistant doclinks to point to current rather than hard-coded 7.17 (#147585)\n\nCo-authored-by: Lisa Cawley <lcawley@elastic.co>\r\nCo-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>\r\nFix #145092"}}]}] BACKPORT--> Co-authored-by: Christiane (Tina) Heiligers <christiane.heiligers@elastic.co>
…rd-coded 7.17 (elastic#147585) Co-authored-by: Lisa Cawley <lcawley@elastic.co> Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com> Fix elastic#145092
Currently, whenever we refer the user to look at our Upgrade Assistant, we point them to the 7.17 version.
Even more, if we open the
current
version of the docs for Upgrade Assistant, it claims it's been moved to 7.17: https://www.elastic.co/guide/en/kibana/current/upgrade-assistant.htmlIn the scope of enabling it for minor upgrades, we should review the existing links to point to
current
? Or the previous minor?The text was updated successfully, but these errors were encountered: