Update Kibana URLs in doc link service#219657
Conversation
|
Pinging @elastic/kibana-docs (Team:Docs) |
🎉 Snyk checks have passed. No issues have been found so far.✅ security/snyk check is complete. No issues have been found. (View Details) ✅ license/snyk check is complete. No issues have been found. (View Details) |
davismcphee
left a comment
There was a problem hiding this comment.
Data Discovery snapshot change LGTM
There was a problem hiding this comment.
Refactored this test a little with a try..finally and update the expected text to something not dependent on the doc link.
|
Starting backport for target branches: 9.0 https://github.com/elastic/kibana/actions/runs/14844096204 |
💛 Build succeeded, but was flaky
Failed CI StepsMetrics [docs]Async chunks
Page load bundle
History
|
💔 All backports failed
Manual backportTo create the backport manually run: Questions ?Please refer to the Backport tool documentation |
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
Co-authored-by: Jean-Louis Leysens <jloleysens@gmail.com> (cherry picked from commit be57bf7)
# Backport This will backport the following commits from `main` to `9.0`: - [Update Kibana URLs in doc link service (#219657)](#219657) The following additional command was required to fix a jest failure: ``` yarn test:jest -u x-pack/platform/plugins/private/upgrade_assistant/public/application/components/es_deprecations/deprecation_types/reindex/flyout/checklist_step.test.tsx ``` <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Lisa Cawley","email":"lcawley@elastic.co"},"sourceCommit":{"committedDate":"2025-05-05T19:03:09Z","message":"Update Kibana URLs in doc link service (#219657)\n\nCo-authored-by: Jean-Louis Leysens <jloleysens@gmail.com>","sha":"be57bf7c814c957837b11eb1a362e440dcbb108c","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Docs","release_note:skip","backport:version","v9.1.0","v9.0.1"],"title":"Update Kibana URLs in doc link service","number":219657,"url":"https://github.com/elastic/kibana/pull/219657","mergeCommit":{"message":"Update Kibana URLs in doc link service (#219657)\n\nCo-authored-by: Jean-Louis Leysens <jloleysens@gmail.com>","sha":"be57bf7c814c957837b11eb1a362e440dcbb108c"}},"sourceBranch":"main","suggestedTargetBranches":["9.0"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/219657","number":219657,"mergeCommit":{"message":"Update Kibana URLs in doc link service (#219657)\n\nCo-authored-by: Jean-Louis Leysens <jloleysens@gmail.com>","sha":"be57bf7c814c957837b11eb1a362e440dcbb108c"}},{"branch":"9.0","label":"v9.0.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> --------- Co-authored-by: Jean-Louis Leysens <jloleysens@gmail.com>
Co-authored-by: Jean-Louis Leysens <jloleysens@gmail.com>
Co-authored-by: Jean-Louis Leysens <jloleysens@gmail.com>
Summary
Relates to #217722
This PR:
kibana,management,scriptedFields,upgradeAssistant,indexPatterns,playground,reporting,kibanaUpgradeSavedObjects,upgrade,console,runtimeFields,date,spaces,settings, andtelemetrysections of the Kibana doc link service.console.serverlessGuideentry since it's no longer different thanconsole.guide.public_base_url.tsx.The jest tests are resolved with the following commands:
Checklist
Check the PR satisfies following conditions.
Reviewers should verify this PR satisfies this list as well.
release_note:breakinglabel should be applied in these situations.release_note:*label is applied per the guidelinesIdentify risks
Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss.
Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging.