# Backport
This will backport the following commits from `main` to `8.x`:
- [[Connectors] Allow pre-configured connectors to opt-in to exposing
their config by setting `exposeConfig`
(#207654)](https://github.com/elastic/kibana/pull/207654)
<!--- Backport version: 9.4.3 -->
### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)
<!--BACKPORT [{"author":{"name":"Yuliia
Naumenko","email":"jo.naumenko@gmail.com"},"sourceCommit":{"committedDate":"2025-01-22T18:51:16Z","message":"[Connectors]
Allow pre-configured connectors to opt-in to exposing their config by
setting `exposeConfig` (#207654)\n\nResolves #206433\r\n\r\nAdded
optional `exposeConfig` field to the `preconfiguredActionSchema`\r\nto
allow return the configuration for the pre-configured
connectors,\r\nwhich set this value as `true`.\r\nThis change is
completely backward compatible, because this field is\r\noptional and
all the connectors, which don't have the value will remain\r\nto work
the same way as before the change (won't return the
config).\r\n\r\nChanged get and getAll methods of the ActionsClient to
reflect opt-in\r\nconfig based on the set `exposeConfig`
value.","sha":"c15674f6d1e670b4210e31031ed93a8c95fdba3b","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:enhancement","v9.0.0","backport:version","8.18
candidate","v8.18.0"],"title":"[Connectors] Allow pre-configured
connectors to opt-in to exposing their config by setting
`exposeConfig`","number":207654,"url":"https://github.com/elastic/kibana/pull/207654","mergeCommit":{"message":"[Connectors]
Allow pre-configured connectors to opt-in to exposing their config by
setting `exposeConfig` (#207654)\n\nResolves #206433\r\n\r\nAdded
optional `exposeConfig` field to the `preconfiguredActionSchema`\r\nto
allow return the configuration for the pre-configured
connectors,\r\nwhich set this value as `true`.\r\nThis change is
completely backward compatible, because this field is\r\noptional and
all the connectors, which don't have the value will remain\r\nto work
the same way as before the change (won't return the
config).\r\n\r\nChanged get and getAll methods of the ActionsClient to
reflect opt-in\r\nconfig based on the set `exposeConfig`
value.","sha":"c15674f6d1e670b4210e31031ed93a8c95fdba3b"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/207654","number":207654,"mergeCommit":{"message":"[Connectors]
Allow pre-configured connectors to opt-in to exposing their config by
setting `exposeConfig` (#207654)\n\nResolves #206433\r\n\r\nAdded
optional `exposeConfig` field to the `preconfiguredActionSchema`\r\nto
allow return the configuration for the pre-configured
connectors,\r\nwhich set this value as `true`.\r\nThis change is
completely backward compatible, because this field is\r\noptional and
all the connectors, which don't have the value will remain\r\nto work
the same way as before the change (won't return the
config).\r\n\r\nChanged get and getAll methods of the ActionsClient to
reflect opt-in\r\nconfig based on the set `exposeConfig`
value.","sha":"c15674f6d1e670b4210e31031ed93a8c95fdba3b"}},{"branch":"8.x","label":"v8.18.0","branchLabelMappingKey":"^v8.18.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->
Co-authored-by: Yuliia Naumenko <jo.naumenko@gmail.com>
# Backport
This will backport the following commits from `main` to `8.x`:
- [Removes tech preview label from cases connectors doc
(#206351)](https://github.com/elastic/kibana/pull/206351)
<!--- Backport version: 9.4.3 -->
### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)
<!--BACKPORT [{"author":{"name":"Janeen Mikell
Roberts","email":"57149392+jmikell821@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-01-14T14:38:50Z","message":"Removes
tech preview label from cases connectors doc (#206351)\n\nThe [cases and
connection
action\r\nfeature](https://www.elastic.co/guide/en/kibana/8.17/cases-action-type.html)\r\nwas
GA'd in `8.17`. This PR removes the tech preview label
(once\r\nbackported to
`8.17`).","sha":"c2e90222cc2a81f230e1b2c564de9870dc551be3","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:prev-minor","backport:8.17"],"title":"Removes
tech preview label from cases connectors
doc","number":206351,"url":"https://github.com/elastic/kibana/pull/206351","mergeCommit":{"message":"Removes
tech preview label from cases connectors doc (#206351)\n\nThe [cases and
connection
action\r\nfeature](https://www.elastic.co/guide/en/kibana/8.17/cases-action-type.html)\r\nwas
GA'd in `8.17`. This PR removes the tech preview label
(once\r\nbackported to
`8.17`).","sha":"c2e90222cc2a81f230e1b2c564de9870dc551be3"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/206351","number":206351,"mergeCommit":{"message":"Removes
tech preview label from cases connectors doc (#206351)\n\nThe [cases and
connection
action\r\nfeature](https://www.elastic.co/guide/en/kibana/8.17/cases-action-type.html)\r\nwas
GA'd in `8.17`. This PR removes the tech preview label
(once\r\nbackported to
`8.17`).","sha":"c2e90222cc2a81f230e1b2c564de9870dc551be3"}}]}]
BACKPORT-->
Co-authored-by: Janeen Mikell Roberts <57149392+jmikell821@users.noreply.github.com>
# Backport
This will backport the following commits from `main` to `8.x`:
- [[Docs] Update nav instructions and sample data installation to
accommodate for the solution views
(#199163)](https://github.com/elastic/kibana/pull/199163)
<!--- Backport version: 9.4.3 -->
### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)
<!--BACKPORT
[{"author":{"name":"florent-leborgne","email":"florent.leborgne@elastic.co"},"sourceCommit":{"committedDate":"2024-11-08T10:10:32Z","message":"[Docs]
Update nav instructions and sample data installation to accommodate for
the solution views (#199163)\n\nThis PR:\r\n- updates navigation
instructions to accommodate for the navigation\r\nchanges related to
solution views.\r\n- updates instructions for adding sample data to rely
on the\r\nintegrations page instead of the home page, that only exists
with the\r\nclassic solution view\r\n- updates references to the home
page to avoid confusing users using one\r\nof the new solution
views\r\n\r\nCloses:
https://github.com/elastic/platform-docs-team/issues/529\r\nCloses:
https://github.com/elastic/platform-docs-team/issues/540","sha":"8e7fb7a77e2399e3e946bbba0462517fd7dad0f7","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Docs","release_note:skip","v9.0.0","docs","v8.16.0","backport:version","v8.17.0"],"title":"[Docs]
Update nav instructions and sample data installation to accommodate for
the solution
views","number":199163,"url":"https://github.com/elastic/kibana/pull/199163","mergeCommit":{"message":"[Docs]
Update nav instructions and sample data installation to accommodate for
the solution views (#199163)\n\nThis PR:\r\n- updates navigation
instructions to accommodate for the navigation\r\nchanges related to
solution views.\r\n- updates instructions for adding sample data to rely
on the\r\nintegrations page instead of the home page, that only exists
with the\r\nclassic solution view\r\n- updates references to the home
page to avoid confusing users using one\r\nof the new solution
views\r\n\r\nCloses:
https://github.com/elastic/platform-docs-team/issues/529\r\nCloses:
https://github.com/elastic/platform-docs-team/issues/540","sha":"8e7fb7a77e2399e3e946bbba0462517fd7dad0f7"}},"sourceBranch":"main","suggestedTargetBranches":["8.16","8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/199163","number":199163,"mergeCommit":{"message":"[Docs]
Update nav instructions and sample data installation to accommodate for
the solution views (#199163)\n\nThis PR:\r\n- updates navigation
instructions to accommodate for the navigation\r\nchanges related to
solution views.\r\n- updates instructions for adding sample data to rely
on the\r\nintegrations page instead of the home page, that only exists
with the\r\nclassic solution view\r\n- updates references to the home
page to avoid confusing users using one\r\nof the new solution
views\r\n\r\nCloses:
https://github.com/elastic/platform-docs-team/issues/529\r\nCloses:
https://github.com/elastic/platform-docs-team/issues/540","sha":"8e7fb7a77e2399e3e946bbba0462517fd7dad0f7"}},{"branch":"8.16","label":"v8.16.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.x","label":"v8.17.0","branchLabelMappingKey":"^v8.17.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->
Co-authored-by: florent-leborgne <florent.leborgne@elastic.co>
# Backport
This will backport the following commits from `main` to `8.x`:
- [[Response Ops][Connectors] Refactor Jira Connector to use latest API
only (#197787)](https://github.com/elastic/kibana/pull/197787)
<!--- Backport version: 9.4.3 -->
### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)
<!--BACKPORT [{"author":{"name":"Julian
Gernun","email":"17549662+jcger@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-11-07T10:47:29Z","message":"[Response
Ops][Connectors] Refactor Jira Connector to use latest API only
(#197787)\n\n## Summary\r\n\r\nJira Cloud and Datacenter work using the
same API urls. In this PR we\r\nremove the calls to the capabilities API
which was being used to know\r\nthe API url we needed to hit\r\n\r\nTo
test it:\r\n- Create Jira Cloud and Datacenter connectors\r\n- Test all
use cases related to them\r\n\r\nRelated to
https://github.com/elastic/kibana/issues/189017\r\n\r\n## Research
Work\r\n\r\n**getCapabilities, createIncident and getIncident** are
always the same,\r\ntherefore ignored for the rest of this
document\r\n\r\n- getCapabilities: `/rest/capabilities`\r\n-
createIncident: `/rest/api/2/issue`\r\n- getIncident:
`/rest/api/2/issue`\r\n\r\n## API links\r\n\r\n-
Cloud:\r\nhttps://developer.atlassian.com/cloud/jira/platform/rest/v2/intro/#version\r\n-
DC:
https://docs.atlassian.com/software/jira/docs/api/REST/9.17.0/\r\n\r\n###
Expected API urls based on the API links\r\n\r\n- Get issue
types\r\n\r\n- Cloud: `GET
/rest/api/2/issue/createmeta/{projectIdOrKey}/issuetypes`\r\n -
DC:`GET /rest/api/2/issue/createmeta/{projectIdOrKey}/issuetypes`\r\n\r\n-
Get fields by issue type\r\n- Cloud:
`GET\r\n/rest/api/2/issue/createmeta/{projectIdOrKey}/issuetypes/{issueTypeId}`\r\n-
DC:\r\n`GET /rest/api/2/issue/createmeta/{projectIdOrKey}/issuetypes/{issueTypeId}`\r\n\r\n###
API we hit\r\n\r\n- Get issue types\r\n\r\n- Cloud
`GET\r\n/rest/api/2/issue/createmeta?projectKeys=ROC&expand=projects.issuetypes.fields`\r\n(variable
name we are using is `getIssueTypesOldAPIURL`)\r\n- DC `GET
/rest/api/2/issue/createmeta/RES/issuetypes` (variable name
is\r\n`getIssueTypesUrl`)\r\n\r\n- Get fields by issue type\r\n- Cloud
`GET\r\n/rest/api/2/issue/createmeta?projectKeys=ROC&issuetypeIds={issueTypeId}&expand=projects.issuetypes.fields`\r\n(variable
name is `getIssueTypeFieldsOldAPIURL`)\r\n- DC `GET
/rest/api/2/issue/createmeta/RES/issuetypes/{issueTypeId}`\r\n(variable
name is `getIssueTypeFieldsUrl`)\r\n\r\n#### Analysed use cases to
retrieve API urls we hit\r\n\r\n- created a case with JIRA Cloud as
Connector\r\n- did a connector test with JIRA Cloud as connector\r\n-
created a case with JIRA DC as connector\r\n- did a connector test with
JIRA DC as connector\r\n\r\n### Conclusions\r\n\r\n- We are not using
the right endpoints for Cloud, we should update them\r\nto use the same
endpoints.\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine
<elasticmachine@users.noreply.github.com>\r\nCo-authored-by: Christos
Nasikas <christos.nasikas@elastic.co>\r\nCo-authored-by: adcoelho
<antonio.coelho@elastic.co>\r\nCo-authored-by: Antonio
<antoniodcoelho@gmail.com>\r\nCo-authored-by: Lisa Cawley
<lcawley@elastic.co>","sha":"953d877df04ce5d9b1c736e7da4d775febebfb68","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:ResponseOps","v9.0.0","backport:prev-minor","v8.17.0"],"title":"[Response
Ops][Connectors] Refactor Jira Connector to use latest API
only","number":197787,"url":"https://github.com/elastic/kibana/pull/197787","mergeCommit":{"message":"[Response
Ops][Connectors] Refactor Jira Connector to use latest API only
(#197787)\n\n## Summary\r\n\r\nJira Cloud and Datacenter work using the
same API urls. In this PR we\r\nremove the calls to the capabilities API
which was being used to know\r\nthe API url we needed to hit\r\n\r\nTo
test it:\r\n- Create Jira Cloud and Datacenter connectors\r\n- Test all
use cases related to them\r\n\r\nRelated to
https://github.com/elastic/kibana/issues/189017\r\n\r\n## Research
Work\r\n\r\n**getCapabilities, createIncident and getIncident** are
always the same,\r\ntherefore ignored for the rest of this
document\r\n\r\n- getCapabilities: `/rest/capabilities`\r\n-
createIncident: `/rest/api/2/issue`\r\n- getIncident:
`/rest/api/2/issue`\r\n\r\n## API links\r\n\r\n-
Cloud:\r\nhttps://developer.atlassian.com/cloud/jira/platform/rest/v2/intro/#version\r\n-
DC:
https://docs.atlassian.com/software/jira/docs/api/REST/9.17.0/\r\n\r\n###
Expected API urls based on the API links\r\n\r\n- Get issue
types\r\n\r\n- Cloud: `GET
/rest/api/2/issue/createmeta/{projectIdOrKey}/issuetypes`\r\n -
DC:`GET /rest/api/2/issue/createmeta/{projectIdOrKey}/issuetypes`\r\n\r\n-
Get fields by issue type\r\n- Cloud:
`GET\r\n/rest/api/2/issue/createmeta/{projectIdOrKey}/issuetypes/{issueTypeId}`\r\n-
DC:\r\n`GET /rest/api/2/issue/createmeta/{projectIdOrKey}/issuetypes/{issueTypeId}`\r\n\r\n###
API we hit\r\n\r\n- Get issue types\r\n\r\n- Cloud
`GET\r\n/rest/api/2/issue/createmeta?projectKeys=ROC&expand=projects.issuetypes.fields`\r\n(variable
name we are using is `getIssueTypesOldAPIURL`)\r\n- DC `GET
/rest/api/2/issue/createmeta/RES/issuetypes` (variable name
is\r\n`getIssueTypesUrl`)\r\n\r\n- Get fields by issue type\r\n- Cloud
`GET\r\n/rest/api/2/issue/createmeta?projectKeys=ROC&issuetypeIds={issueTypeId}&expand=projects.issuetypes.fields`\r\n(variable
name is `getIssueTypeFieldsOldAPIURL`)\r\n- DC `GET
/rest/api/2/issue/createmeta/RES/issuetypes/{issueTypeId}`\r\n(variable
name is `getIssueTypeFieldsUrl`)\r\n\r\n#### Analysed use cases to
retrieve API urls we hit\r\n\r\n- created a case with JIRA Cloud as
Connector\r\n- did a connector test with JIRA Cloud as connector\r\n-
created a case with JIRA DC as connector\r\n- did a connector test with
JIRA DC as connector\r\n\r\n### Conclusions\r\n\r\n- We are not using
the right endpoints for Cloud, we should update them\r\nto use the same
endpoints.\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine
<elasticmachine@users.noreply.github.com>\r\nCo-authored-by: Christos
Nasikas <christos.nasikas@elastic.co>\r\nCo-authored-by: adcoelho
<antonio.coelho@elastic.co>\r\nCo-authored-by: Antonio
<antoniodcoelho@gmail.com>\r\nCo-authored-by: Lisa Cawley
<lcawley@elastic.co>","sha":"953d877df04ce5d9b1c736e7da4d775febebfb68"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/197787","number":197787,"mergeCommit":{"message":"[Response
Ops][Connectors] Refactor Jira Connector to use latest API only
(#197787)\n\n## Summary\r\n\r\nJira Cloud and Datacenter work using the
same API urls. In this PR we\r\nremove the calls to the capabilities API
which was being used to know\r\nthe API url we needed to hit\r\n\r\nTo
test it:\r\n- Create Jira Cloud and Datacenter connectors\r\n- Test all
use cases related to them\r\n\r\nRelated to
https://github.com/elastic/kibana/issues/189017\r\n\r\n## Research
Work\r\n\r\n**getCapabilities, createIncident and getIncident** are
always the same,\r\ntherefore ignored for the rest of this
document\r\n\r\n- getCapabilities: `/rest/capabilities`\r\n-
createIncident: `/rest/api/2/issue`\r\n- getIncident:
`/rest/api/2/issue`\r\n\r\n## API links\r\n\r\n-
Cloud:\r\nhttps://developer.atlassian.com/cloud/jira/platform/rest/v2/intro/#version\r\n-
DC:
https://docs.atlassian.com/software/jira/docs/api/REST/9.17.0/\r\n\r\n###
Expected API urls based on the API links\r\n\r\n- Get issue
types\r\n\r\n- Cloud: `GET
/rest/api/2/issue/createmeta/{projectIdOrKey}/issuetypes`\r\n -
DC:`GET /rest/api/2/issue/createmeta/{projectIdOrKey}/issuetypes`\r\n\r\n-
Get fields by issue type\r\n- Cloud:
`GET\r\n/rest/api/2/issue/createmeta/{projectIdOrKey}/issuetypes/{issueTypeId}`\r\n-
DC:\r\n`GET /rest/api/2/issue/createmeta/{projectIdOrKey}/issuetypes/{issueTypeId}`\r\n\r\n###
API we hit\r\n\r\n- Get issue types\r\n\r\n- Cloud
`GET\r\n/rest/api/2/issue/createmeta?projectKeys=ROC&expand=projects.issuetypes.fields`\r\n(variable
name we are using is `getIssueTypesOldAPIURL`)\r\n- DC `GET
/rest/api/2/issue/createmeta/RES/issuetypes` (variable name
is\r\n`getIssueTypesUrl`)\r\n\r\n- Get fields by issue type\r\n- Cloud
`GET\r\n/rest/api/2/issue/createmeta?projectKeys=ROC&issuetypeIds={issueTypeId}&expand=projects.issuetypes.fields`\r\n(variable
name is `getIssueTypeFieldsOldAPIURL`)\r\n- DC `GET
/rest/api/2/issue/createmeta/RES/issuetypes/{issueTypeId}`\r\n(variable
name is `getIssueTypeFieldsUrl`)\r\n\r\n#### Analysed use cases to
retrieve API urls we hit\r\n\r\n- created a case with JIRA Cloud as
Connector\r\n- did a connector test with JIRA Cloud as connector\r\n-
created a case with JIRA DC as connector\r\n- did a connector test with
JIRA DC as connector\r\n\r\n### Conclusions\r\n\r\n- We are not using
the right endpoints for Cloud, we should update them\r\nto use the same
endpoints.\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine
<elasticmachine@users.noreply.github.com>\r\nCo-authored-by: Christos
Nasikas <christos.nasikas@elastic.co>\r\nCo-authored-by: adcoelho
<antonio.coelho@elastic.co>\r\nCo-authored-by: Antonio
<antoniodcoelho@gmail.com>\r\nCo-authored-by: Lisa Cawley
<lcawley@elastic.co>","sha":"953d877df04ce5d9b1c736e7da4d775febebfb68"}},{"branch":"8.x","label":"v8.17.0","branchLabelMappingKey":"^v8.17.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->
Co-authored-by: Julian Gernun <17549662+jcger@users.noreply.github.com>
# Backport
This will backport the following commits from `main` to `8.x`:
- [[DOCS] Fine-tunes inference connector and action docs
(#198345)](https://github.com/elastic/kibana/pull/198345)
<!--- Backport version: 9.4.3 -->
### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)
<!--BACKPORT [{"author":{"name":"István Zoltán
Szabó","email":"szabosteve@gmail.com"},"sourceCommit":{"committedDate":"2024-10-30T16:12:53Z","message":"[DOCS]
Fine-tunes inference connector and action docs
(#198345)","sha":"dc8322a46f51a2e12fa0eafee1dad365e5adffb5","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Docs","release_note:skip","v9.0.0","docs","v8.16.0","backport:version","v8.17.0"],"title":"[DOCS]
Fine-tunes inference connector and action
docs","number":198345,"url":"https://github.com/elastic/kibana/pull/198345","mergeCommit":{"message":"[DOCS]
Fine-tunes inference connector and action docs
(#198345)","sha":"dc8322a46f51a2e12fa0eafee1dad365e5adffb5"}},"sourceBranch":"main","suggestedTargetBranches":["8.16","8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/198345","number":198345,"mergeCommit":{"message":"[DOCS]
Fine-tunes inference connector and action docs
(#198345)","sha":"dc8322a46f51a2e12fa0eafee1dad365e5adffb5"}},{"branch":"8.16","label":"v8.16.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.x","label":"v8.17.0","branchLabelMappingKey":"^v8.17.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->
Co-authored-by: István Zoltán Szabó <szabosteve@gmail.com>
# Backport
This will backport the following commits from `main` to `8.x`:
- [[Connectors][GenAI] Inference Service Kibana connector
(#189027)](https://github.com/elastic/kibana/pull/189027)
<!--- Backport version: 9.4.3 -->
### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)
<!--BACKPORT [{"author":{"name":"Yuliia
Naumenko","email":"jo.naumenko@gmail.com"},"sourceCommit":{"committedDate":"2024-10-13T20:39:09Z","message":"[Connectors][GenAI]
Inference Service Kibana connector (#189027)\n\n## Summary\r\nResolves
https://github.com/elastic/kibana/issues/188043\r\n\r\nThis PR adds new
connector which is define integration with Elastic\r\nInference Endpoint
via
[Inference\r\nAPIs](https://www.elastic.co/guide/en/elasticsearch/reference/current/inference-apis.html)\r\nThe
lifecycle of the Inference Endpoint are managed by the
connector\r\nregistered handlers:\r\n\r\n- `preSaveHook`
-\r\n[create](https://www.elastic.co/guide/en/elasticsearch/reference/current/put-inference-api.html)\r\nnew
Inference Endpoint in the connector create mode (`isEdit ===
false`)\r\nand\r\n[delete](https://www.elastic.co/guide/en/elasticsearch/reference/current/delete-inference-api.html)+[create](https://www.elastic.co/guide/en/elasticsearch/reference/current/put-inference-api.html)\r\nin
the connector edit mode (`isEdit === true`)\r\n- `postSaveHook` - check
if the connector SO was created/updated and if\r\nnot removes Inference
Endpoint from preSaveHook\r\n- `postDeleteHook`
-\r\n[delete](https://www.elastic.co/guide/en/elasticsearch/reference/current/delete-inference-api.html)\r\nInference
Endpoint if connector was deleted.\r\n\r\nIn the Kibana Stack Management
Connectors, its represented with the new\r\ncard (Technical preview
badge):\r\n\r\n<img width=\"1261\" alt=\"Screenshot 2024-09-27 at 2 11
12 PM\"\r\nsrc=\"https://github.com/user-attachments/assets/dcbcce1f-06e7-4d08-8b77-0ba4105354f8\">\r\n\r\nTo
simplify the future integration with AI Assistants, the
Connector\r\nconsists from the two main UI parts: provider selector and
required\r\nprovider settings, which will be always displayed\r\n<img
width=\"862\" alt=\"Screenshot 2024-10-07 at 7 59
09 AM\"\r\nsrc=\"https://github.com/user-attachments/assets/87bae493-c642-479e-b28f-6150354608dd\">\r\n\r\nand
Additional options, which contains optional provider settings
and\r\nTask Type configuration:\r\n\r\n<img width=\"861\"
alt=\"Screenshot 2024-10-07 at 8 00
15 AM\"\r\nsrc=\"https://github.com/user-attachments/assets/2341c034-6198-4731-8ce7-e22e6c6fb20f\">\r\n\r\n\r\nsubActions
corresponds to the different taskTypes Inference API\r\nsupports. Each
of the task type has its own Inference Perform params.\r\nCurrently
added:\r\n\r\n- completion & completionStream\r\n- rerank\r\n-
text_embedding\r\n- sparse_embedding\r\n\r\nFollow up work:\r\n\r\n1.
Collapse/expand Additional options, when the connector
flyout/modal\r\nhas AI Assistant as a context (path through the
extending context\r\nimplementation on the connector framework
level)\r\n2. Add support for additional params for Completion subAction
to be able\r\nto path functions\r\n3. Add support for tokens usage
Dashboard, when inference API will\r\ninclude the used tokens count in
the response\r\n4. Add functionality and UX for migration from existing
specific AI\r\nconnectors to the Inference connector with proper
provider and\r\ncompletion task\r\n5. Integrate Connector with the AI
Assistants\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by:
István Zoltán Szabó <istvan.szabo@elastic.co>\r\nCo-authored-by: Liam
Thompson
<32779855+leemthompo@users.noreply.github.com>\r\nCo-authored-by: Steph
Milovic
<stephanie.milovic@elastic.co>","sha":"288d41d61ec2389b2e8856da75fd0f3107f9c484","branchLabelMapping":{"^v9.0.0$":"main","^v8.16.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["v9.0.0","release_note:feature","Feature:Actions/ConnectorTypes","8.16
candidate","v8.16.0","backport:version"],"title":"[Connectors][GenAI]
Inference Service Kibana
connector","number":189027,"url":"https://github.com/elastic/kibana/pull/189027","mergeCommit":{"message":"[Connectors][GenAI]
Inference Service Kibana connector (#189027)\n\n## Summary\r\nResolves
https://github.com/elastic/kibana/issues/188043\r\n\r\nThis PR adds new
connector which is define integration with Elastic\r\nInference Endpoint
via
[Inference\r\nAPIs](https://www.elastic.co/guide/en/elasticsearch/reference/current/inference-apis.html)\r\nThe
lifecycle of the Inference Endpoint are managed by the
connector\r\nregistered handlers:\r\n\r\n- `preSaveHook`
-\r\n[create](https://www.elastic.co/guide/en/elasticsearch/reference/current/put-inference-api.html)\r\nnew
Inference Endpoint in the connector create mode (`isEdit ===
false`)\r\nand\r\n[delete](https://www.elastic.co/guide/en/elasticsearch/reference/current/delete-inference-api.html)+[create](https://www.elastic.co/guide/en/elasticsearch/reference/current/put-inference-api.html)\r\nin
the connector edit mode (`isEdit === true`)\r\n- `postSaveHook` - check
if the connector SO was created/updated and if\r\nnot removes Inference
Endpoint from preSaveHook\r\n- `postDeleteHook`
-\r\n[delete](https://www.elastic.co/guide/en/elasticsearch/reference/current/delete-inference-api.html)\r\nInference
Endpoint if connector was deleted.\r\n\r\nIn the Kibana Stack Management
Connectors, its represented with the new\r\ncard (Technical preview
badge):\r\n\r\n<img width=\"1261\" alt=\"Screenshot 2024-09-27 at 2 11
12 PM\"\r\nsrc=\"https://github.com/user-attachments/assets/dcbcce1f-06e7-4d08-8b77-0ba4105354f8\">\r\n\r\nTo
simplify the future integration with AI Assistants, the
Connector\r\nconsists from the two main UI parts: provider selector and
required\r\nprovider settings, which will be always displayed\r\n<img
width=\"862\" alt=\"Screenshot 2024-10-07 at 7 59
09 AM\"\r\nsrc=\"https://github.com/user-attachments/assets/87bae493-c642-479e-b28f-6150354608dd\">\r\n\r\nand
Additional options, which contains optional provider settings
and\r\nTask Type configuration:\r\n\r\n<img width=\"861\"
alt=\"Screenshot 2024-10-07 at 8 00
15 AM\"\r\nsrc=\"https://github.com/user-attachments/assets/2341c034-6198-4731-8ce7-e22e6c6fb20f\">\r\n\r\n\r\nsubActions
corresponds to the different taskTypes Inference API\r\nsupports. Each
of the task type has its own Inference Perform params.\r\nCurrently
added:\r\n\r\n- completion & completionStream\r\n- rerank\r\n-
text_embedding\r\n- sparse_embedding\r\n\r\nFollow up work:\r\n\r\n1.
Collapse/expand Additional options, when the connector
flyout/modal\r\nhas AI Assistant as a context (path through the
extending context\r\nimplementation on the connector framework
level)\r\n2. Add support for additional params for Completion subAction
to be able\r\nto path functions\r\n3. Add support for tokens usage
Dashboard, when inference API will\r\ninclude the used tokens count in
the response\r\n4. Add functionality and UX for migration from existing
specific AI\r\nconnectors to the Inference connector with proper
provider and\r\ncompletion task\r\n5. Integrate Connector with the AI
Assistants\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by:
István Zoltán Szabó <istvan.szabo@elastic.co>\r\nCo-authored-by: Liam
Thompson
<32779855+leemthompo@users.noreply.github.com>\r\nCo-authored-by: Steph
Milovic
<stephanie.milovic@elastic.co>","sha":"288d41d61ec2389b2e8856da75fd0f3107f9c484"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/189027","number":189027,"mergeCommit":{"message":"[Connectors][GenAI]
Inference Service Kibana connector (#189027)\n\n## Summary\r\nResolves
https://github.com/elastic/kibana/issues/188043\r\n\r\nThis PR adds new
connector which is define integration with Elastic\r\nInference Endpoint
via
[Inference\r\nAPIs](https://www.elastic.co/guide/en/elasticsearch/reference/current/inference-apis.html)\r\nThe
lifecycle of the Inference Endpoint are managed by the
connector\r\nregistered handlers:\r\n\r\n- `preSaveHook`
-\r\n[create](https://www.elastic.co/guide/en/elasticsearch/reference/current/put-inference-api.html)\r\nnew
Inference Endpoint in the connector create mode (`isEdit ===
false`)\r\nand\r\n[delete](https://www.elastic.co/guide/en/elasticsearch/reference/current/delete-inference-api.html)+[create](https://www.elastic.co/guide/en/elasticsearch/reference/current/put-inference-api.html)\r\nin
the connector edit mode (`isEdit === true`)\r\n- `postSaveHook` - check
if the connector SO was created/updated and if\r\nnot removes Inference
Endpoint from preSaveHook\r\n- `postDeleteHook`
-\r\n[delete](https://www.elastic.co/guide/en/elasticsearch/reference/current/delete-inference-api.html)\r\nInference
Endpoint if connector was deleted.\r\n\r\nIn the Kibana Stack Management
Connectors, its represented with the new\r\ncard (Technical preview
badge):\r\n\r\n<img width=\"1261\" alt=\"Screenshot 2024-09-27 at 2 11
12 PM\"\r\nsrc=\"https://github.com/user-attachments/assets/dcbcce1f-06e7-4d08-8b77-0ba4105354f8\">\r\n\r\nTo
simplify the future integration with AI Assistants, the
Connector\r\nconsists from the two main UI parts: provider selector and
required\r\nprovider settings, which will be always displayed\r\n<img
width=\"862\" alt=\"Screenshot 2024-10-07 at 7 59
09 AM\"\r\nsrc=\"https://github.com/user-attachments/assets/87bae493-c642-479e-b28f-6150354608dd\">\r\n\r\nand
Additional options, which contains optional provider settings
and\r\nTask Type configuration:\r\n\r\n<img width=\"861\"
alt=\"Screenshot 2024-10-07 at 8 00
15 AM\"\r\nsrc=\"https://github.com/user-attachments/assets/2341c034-6198-4731-8ce7-e22e6c6fb20f\">\r\n\r\n\r\nsubActions
corresponds to the different taskTypes Inference API\r\nsupports. Each
of the task type has its own Inference Perform params.\r\nCurrently
added:\r\n\r\n- completion & completionStream\r\n- rerank\r\n-
text_embedding\r\n- sparse_embedding\r\n\r\nFollow up work:\r\n\r\n1.
Collapse/expand Additional options, when the connector
flyout/modal\r\nhas AI Assistant as a context (path through the
extending context\r\nimplementation on the connector framework
level)\r\n2. Add support for additional params for Completion subAction
to be able\r\nto path functions\r\n3. Add support for tokens usage
Dashboard, when inference API will\r\ninclude the used tokens count in
the response\r\n4. Add functionality and UX for migration from existing
specific AI\r\nconnectors to the Inference connector with proper
provider and\r\ncompletion task\r\n5. Integrate Connector with the AI
Assistants\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by:
István Zoltán Szabó <istvan.szabo@elastic.co>\r\nCo-authored-by: Liam
Thompson
<32779855+leemthompo@users.noreply.github.com>\r\nCo-authored-by: Steph
Milovic
<stephanie.milovic@elastic.co>","sha":"288d41d61ec2389b2e8856da75fd0f3107f9c484"}},{"branch":"8.x","label":"v8.16.0","branchLabelMappingKey":"^v8.16.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->
Co-authored-by: Yuliia Naumenko <jo.naumenko@gmail.com>
# Backport
This will backport the following commits from `main` to `8.x`:
- [[Gemini Connector] Bump Default model to
`gemini-1.5-pro-002`
(#195320)](https://github.com/elastic/kibana/pull/195320)
<!--- Backport version: 9.4.3 -->
### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)
<!--BACKPORT [{"author":{"name":"Steph
Milovic","email":"stephanie.milovic@elastic.co"},"sourceCommit":{"committedDate":"2024-10-08T14:52:51Z","message":"[Gemini
Connector] Bump Default model to `gemini-1.5-pro-002`
(#195320)","sha":"2873cbca2008b68486bb8439a3035f759be0ebce","branchLabelMapping":{"^v9.0.0$":"main","^v8.16.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:prev-minor","Team:Security
Generative AI","v8.16.0"],"title":"[Gemini Connector] Bump Default model
to
`gemini-1.5-pro-002`","number":195320,"url":"https://github.com/elastic/kibana/pull/195320","mergeCommit":{"message":"[Gemini
Connector] Bump Default model to `gemini-1.5-pro-002`
(#195320)","sha":"2873cbca2008b68486bb8439a3035f759be0ebce"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/195320","number":195320,"mergeCommit":{"message":"[Gemini
Connector] Bump Default model to `gemini-1.5-pro-002`
(#195320)","sha":"2873cbca2008b68486bb8439a3035f759be0ebce"}},{"branch":"8.x","label":"v8.16.0","branchLabelMappingKey":"^v8.16.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->
Co-authored-by: Steph Milovic <stephanie.milovic@elastic.co>
# Backport
This will backport the following commits from `main` to `8.x`:
- [[DOCS] Additional fields in ServiceNow ITSM and SecOps connectors
(#195122)](https://github.com/elastic/kibana/pull/195122)
<!--- Backport version: 9.4.3 -->
### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)
<!--BACKPORT [{"author":{"name":"Lisa
Cawley","email":"lcawley@elastic.co"},"sourceCommit":{"committedDate":"2024-10-07T16:17:10Z","message":"[DOCS]
Additional fields in ServiceNow ITSM and SecOps connectors
(#195122)","sha":"3b70d999150210f3915243837d9a4796e77f36a1","branchLabelMapping":{"^v9.0.0$":"main","^v8.16.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:ResponseOps","v9.0.0","docs","Feature:Actions/ConnectorTypes","v8.16.0","backport:version","v8.15.3"],"title":"[DOCS]
Additional fields in ServiceNow ITSM and SecOps
connectors","number":195122,"url":"https://github.com/elastic/kibana/pull/195122","mergeCommit":{"message":"[DOCS]
Additional fields in ServiceNow ITSM and SecOps connectors
(#195122)","sha":"3b70d999150210f3915243837d9a4796e77f36a1"}},"sourceBranch":"main","suggestedTargetBranches":["8.x","8.15"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/195122","number":195122,"mergeCommit":{"message":"[DOCS]
Additional fields in ServiceNow ITSM and SecOps connectors
(#195122)","sha":"3b70d999150210f3915243837d9a4796e77f36a1"}},{"branch":"8.x","label":"v8.16.0","branchLabelMappingKey":"^v8.16.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.15","label":"v8.15.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->
Co-authored-by: Lisa Cawley <lcawley@elastic.co>
# Backport
This will backport the following commits from `main` to `8.x`:
- [[DOCS] Add TheHive connector to case settings
(#193802)](https://github.com/elastic/kibana/pull/193802)
<!--- Backport version: 9.4.3 -->
### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)
<!--BACKPORT [{"author":{"name":"Lisa
Cawley","email":"lcawley@elastic.co"},"sourceCommit":{"committedDate":"2024-10-01T00:33:31Z","message":"[DOCS]
Add TheHive connector to case settings
(#193802)","sha":"5ed0426ef6657af24437d1931fc99c7094dc1e35","branchLabelMapping":{"^v9.0.0$":"main","^v8.16.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:ResponseOps","v9.0.0","docs","Feature:Cases","v8.16.0","backport:version"],"title":"[DOCS]
Add TheHive connector to case
settings","number":193802,"url":"https://github.com/elastic/kibana/pull/193802","mergeCommit":{"message":"[DOCS]
Add TheHive connector to case settings
(#193802)","sha":"5ed0426ef6657af24437d1931fc99c7094dc1e35"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/193802","number":193802,"mergeCommit":{"message":"[DOCS]
Add TheHive connector to case settings
(#193802)","sha":"5ed0426ef6657af24437d1931fc99c7094dc1e35"}},{"branch":"8.x","label":"v8.16.0","branchLabelMappingKey":"^v8.16.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->
Co-authored-by: Lisa Cawley <lcawley@elastic.co>
## Summary
Adds reference documentation about the Obs AI Assistant connector
(requested in #181282)
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
~This PR still needs work (tests, mainly), so keeping it in draft for
now, but feel free to take it for a spin.~
Implements Bedrock support, specifically for the Claude models.
Architecturally, this introduces LLM adapters: one for OpenAI (which is
what we already have), and one for Bedrock/Claude. The Bedrock/Claude
adapter does the following things:
- parses data from a SerDe (an AWS concept IIUC) stream using
`@smithy/eventstream-serde-node`.
- Converts function requests and results into XML and back (to some
extent)
- some slight changes to existing functionality to achieve _some_ kind
of baseline performance with Bedrock + Claude.
Generally, GPT seems better at implicit tasks. Claude needs explicit
tasks, otherwise it will take things too literally. For instance, I had
to use a function for generating a title because Claude was too eager to
add explanations. For the `classify_esql` function, I had to add extra
instructions to stop it from requesting information that is not there.
It is prone to generating invalid XML.
---------
Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
