-
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
Updating preconfigured connector name #211927
Updating preconfigured connector name #211927
Conversation
Pinging @elastic/fleet (Team:Fleet) |
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.
security engineering productivity changes LGTM
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.
Fleet changes LGTM 🚀
d4d80a0
to
757a1bd
Compare
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
stateful-local: works as described in the Testing Instructions
serverless-local: I do no know what additional config is needed for it to show up
@elasticmachine merge upstream |
8810b30
to
e1213b9
Compare
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
@YulNaumenko removed |
💚 Build Succeeded
Metrics [docs]
History
|
Starting backport for target branches: 8.18, 8.x, 9.0 https://github.com/elastic/kibana/actions/runs/13529243457 |
💔 All backports failed
Manual backportTo create the backport manually run:
Questions ?Please refer to the Backport tool documentation |
## Summary Update Preconfigured connector name to `Elastic LLM`. <img width="1504" alt="Screenshot 2025-02-20 at 11 29 02 AM" src="https://github.com/user-attachments/assets/aa0a32f7-f1b2-4496-8c2e-7773f017c153" /> ### ES3 Testing instruction No additional config needed. Once run in local machine, the changes should reflect automatically. ### ESS instructions In `kibana.dev.yml` file, add ``` # xpack.actions.preconfigured: Elastic-LLM: name: Elastic LLM actionTypeId: .inference exposeConfig: true config: provider: 'elastic' taskType: 'chat_completion' inferenceId: '.rainbow-sprinkles-elastic' providerConfig: model_id: 'rainbow-sprinkles' ``` and the preconfigured endpoint with updated name should be visible. ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [X] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios (cherry picked from commit 0e02a32) # Conflicts: # config/serverless.yml # x-pack/solutions/security/plugins/security_solution/public/management/cypress/tasks/insights.ts
## Summary Update Preconfigured connector name to `Elastic LLM`. <img width="1504" alt="Screenshot 2025-02-20 at 11 29 02 AM" src="https://github.com/user-attachments/assets/aa0a32f7-f1b2-4496-8c2e-7773f017c153" /> ### ES3 Testing instruction No additional config needed. Once run in local machine, the changes should reflect automatically. ### ESS instructions In `kibana.dev.yml` file, add ``` # xpack.actions.preconfigured: Elastic-LLM: name: Elastic LLM actionTypeId: .inference exposeConfig: true config: provider: 'elastic' taskType: 'chat_completion' inferenceId: '.rainbow-sprinkles-elastic' providerConfig: model_id: 'rainbow-sprinkles' ``` and the preconfigured endpoint with updated name should be visible. ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [X] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios (cherry picked from commit 0e02a32) # Conflicts: # config/serverless.yml # x-pack/solutions/security/plugins/security_solution/public/management/cypress/tasks/insights.ts
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
## Summary Update Preconfigured connector name to `Elastic LLM`. <img width="1504" alt="Screenshot 2025-02-20 at 11 29 02 AM" src="https://github.com/user-attachments/assets/aa0a32f7-f1b2-4496-8c2e-7773f017c153" /> ### ES3 Testing instruction No additional config needed. Once run in local machine, the changes should reflect automatically. ### ESS instructions In `kibana.dev.yml` file, add ``` # xpack.actions.preconfigured: Elastic-LLM: name: Elastic LLM actionTypeId: .inference exposeConfig: true config: provider: 'elastic' taskType: 'chat_completion' inferenceId: '.rainbow-sprinkles-elastic' providerConfig: model_id: 'rainbow-sprinkles' ``` and the preconfigured endpoint with updated name should be visible. ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [X] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios (cherry picked from commit 0e02a32) # Conflicts: # config/serverless.yml # x-pack/solutions/security/plugins/security_solution/public/management/cypress/tasks/insights.ts
Summary
Update Preconfigured connector name to
Elastic LLM
.ES3 Testing instruction
No additional config needed. Once run in local machine, the changes should reflect automatically.
ESS instructions
In
kibana.dev.yml
file, addand the preconfigured endpoint with updated name should be visible.
Checklist
Check the PR satisfies following conditions.
Reviewers should verify this PR satisfies this list as well.