[Inference] Update Feature Settings, External Inference doc links and UI text#265633
Conversation
ApprovabilityVerdict: Needs human review Low-risk changes adding documentation links and updating UI copy text. However, all modified files are owned by other teams (@elastic/docs, @elastic/search-kibana) and the designated code owners should review. You can customize Macroscope's approvability policy. Learn more. |
💛 Build succeeded, but was flaky
Failed CI StepsTest FailuresMetrics [docs]Async chunks
Page load bundle
History
|
| @@ -228,8 +228,7 @@ export const DefaultModelSection: React.FC<Props> = ({ defaultModelSettings }) = | |||
| : i18n.translate( | |||
| 'xpack.searchInferenceEndpoints.settings.defaultModel.allowOtherModels.description', | |||
There was a problem hiding this comment.
Consider a new i18n message id for allowOtherModels help text since the defaultMessage meaning shifted; keeping the old id can leave non-English strings on the old wording. After changing the id, run node scripts/i18n_check --fix.
|
Starting backport for target branches: 9.4 https://github.com/elastic/kibana/actions/runs/25156947156 |
💔 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 |
|
Looks like this PR has a backport PR but it still hasn't been merged. Please merge it ASAP to keep the branches relatively in sync. |
…ks and UI text (#265633) (#266696) # Backport This will backport the following commits from `main` to `9.4`: - [[Inference] Update Feature Settings, External Inference doc links and UI text (#265633)](#265633) <!--- Backport version: 11.0.2 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Lisa Cawley","email":"lcawley@elastic.co"},"sourceCommit":{"committedDate":"2026-04-30T09:03:45Z","message":"[Inference] Update Feature Settings, External Inference doc links and UI text (#265633)","sha":"b26091f5851c0686b52935e753aba0a3c50bd31c","branchLabelMapping":{"^v9.5.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Search","backport:version","v9.4.0","v9.5.0"],"title":"[Inference] Update Feature Settings, External Inference doc links and UI text","number":265633,"url":"https://github.com/elastic/kibana/pull/265633","mergeCommit":{"message":"[Inference] Update Feature Settings, External Inference doc links and UI text (#265633)","sha":"b26091f5851c0686b52935e753aba0a3c50bd31c"}},"sourceBranch":"main","suggestedTargetBranches":["9.4"],"targetPullRequestStates":[{"branch":"9.4","label":"v9.4.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.5.0","branchLabelMappingKey":"^v9.5.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/265633","number":265633,"mergeCommit":{"message":"[Inference] Update Feature Settings, External Inference doc links and UI text (#265633)","sha":"b26091f5851c0686b52935e753aba0a3c50bd31c"}}]}] BACKPORT--> --------- Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
Summary
This PR adds https://www.elastic.co/docs/explore-analyze/ai-features/manage-access-to-ai-assistant to the doc link service and uses it on the Feature Settings page.
Relates to elastic/docs-content#6122
I've also edited one string in that app that seemed unclear.
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 guidelinesbackport:*labels.Identify 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.