Ash
ba8d83a14c
[SecuritySolution][Endpoint] Update serverless roles to include stack connector sub-privilege ( #208155 )
...
## Summary
Adds EDR stack connectors sub-privilege to serverless roles.
### Checklist
Reviewers should verify this PR satisfies this list as well.
- [ ] Any text added follows [EUI's writing
guidelines](https://elastic.github.io/eui/#/guidelines/writing ), uses
sentence case text and includes [i18n
support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md )
- [ ]
[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html )
was added for features that require explanation or tutorials
- [ ] [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
- [ ] If a plugin configuration key changed, check if it needs to be
allowlisted in the cloud and added to the [docker
list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker )
- [ ] This was checked for breaking HTTP API changes, and any breaking
changes have been approved by the breaking-change committee. The
`release_note:breaking` label should be applied in these situations.
- [ ] [Flaky Test
Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1 ) was
used on any tests changed
- [ ] The PR description includes the appropriate Release Notes section,
and the correct `release_note:*` label is applied per the
[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process )
### 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.
- [ ] [See some risk
examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx )
- [ ] ...
2025-01-27 17:40:28 +00:00
Janki Salvi
bbc3944d31
[ResponseOps][Cases] Delete get status deprecated API ( #208208 )
...
## Summary
Resolves https://github.com/elastic/kibana/issues/207341
### Checklist
Check the PR satisfies following conditions.
- [x]
[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html )
was added for features that require explanation or tutorials
- [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
### Release note
Removed deprecated get case status API
---------
Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
2025-01-27 16:21:19 +00:00
Janki Salvi
9291165413
[ResponseOps][Cases] Delete get all user actions API ( #208086 )
...
## Summary
Resolves https://github.com/elastic/kibana/issues/207340
### Checklist
- [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
### Release note
Removed deprecated get user actions API
---------
Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
2025-01-27 12:57:22 +00:00
Elena Stoeva
b08eaa7d5a
[Index Management] Display index mode of data streams depending on logsdb.enabled
cluster setting ( #207131 )
...
Closes https://github.com/elastic/kibana/issues/206126
## Summary
This PR displays a LogsDB index mode for `logs-*-*` data streams and
templates with the `logs-*-*` index pattern if the
`cluster.logsdb.enabled` setting is set to true and as "Standard" if
it's set to false. If the setting is not set, it is false by default in
stateful (and so "Standard" index mode) and true by default in
serverless (and so "LogsDB" index mode).
**How to test:**
In Stateful:
1. Create an index template with a `logs-*-*` index pattern
2. Create a `logs-*-*` data stream: `PUT _data_stream/logs-test-1`
3. Go to Index Management -> Index templates and click on the created
index templates. Verify that the index mode is correct (**NOTE:** In
stateful, the `cluster.logsdb.enabled` setting is `false` by default,
while in serverless it's `true` by default. Therefore, the index mode
should be `Standard` in stateful and `LogsDB` in serverless.
4. Go to Index Management -> Data Streams and find the created data
stream. Verify that the index mode is correct (**NOTE:** In stateful,
the `cluster.logsdb.enabled` setting is `false` by default, while in
serverless it's `true` by default. Therefore, the index mode should be
`Standard` in stateful and `LogsDB` in serverless.
5. In Console, set the `cluster.logsdb.enabled` setting:
```
PUT /_cluster/settings
{
"persistent" : {
"cluster.logsdb.enabled" : true
}
}
```
6. Go to the data stream/templates list and verify that the index mode
of the test data stream/template that we created is displayed as LogsDB
7. Change the cluster setting to `false` and verify that the index mode
is now displayed as Standard.
---------
Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
2025-01-24 21:55:16 +00:00
Janki Salvi
1945ae6e64
[ResponseOps][Cases] Remove get all comments api ( #207926 )
...
## Summary
Resolves https://github.com/elastic/kibana/issues/207339
### Checklist
- [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
### Release note
Removed deprecated get all comments API
---------
Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
2025-01-24 17:06:37 +00:00
Sander Philipse
c6f7416efc
[ES3] Fix onboarding tiles to new design ( #208069 )
...
## Summary
This adapts the onboarding guide for Elasticsearch to:
- use in-page tiles
- remember its guide selection in local storage
- actually switch the code correctly on the start page
https://github.com/user-attachments/assets/9a23b7a6-828a-4d37-a460-975dd526eafe
UPDATED SCREEN RECORDING:
https://github.com/user-attachments/assets/7526f1d5-b85c-4096-85c5-9cf35b1bd757
---------
Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
2025-01-24 16:29:53 +01:00
Tre
d6967b8bce
[SKIP ON MKI] x-pack/test_serverless/../search_source_alert.ts
( #207869 )
...
## Summary
See details: https://github.com/elastic/kibana/issues/207865
2025-01-23 09:12:25 +00:00
Yngrid Coello
511f77c231
[Dataset quality] Failure store support ( #206758 )
...
Closes https://github.com/elastic/logs-dev/issues/183 ,
https://github.com/elastic/logs-dev/issues/184 and
https://github.com/elastic/logs-dev/issues/185 .
## Summary
This PR aims to support failure store in dataset quality page. The
following acceptance criteria items were resolved
### Dataset quality page
- [x] A column for Failed docs is included in the table
- [x] A tooltip is placed in the title of the column
- [x] A % of documents inside Failure store is calculated for every
dataStream
- [x] If % is lesser than 0.0001 but greater than 0 we should show ⚠
symbol next to the ~0 value (as we do with degraded docs)
- [x] Failed docs percentages greater than 0 should link to discover
🎥 Demo
https://github.com/user-attachments/assets/6d9e3f4c-02d9-43ab-88cb-ae70716b05d9
### Dataset details page
- [x] A metric, Failed docs, is included in the Overview panel under
Data set quality. This metric includes the number of documents inside
the failure store for the specific dataStream.
- [x] A tooltip is placed in the title of the Failed docs metric with
message: `The percentage of docs sent to failure store due to an issue
during ingestion.`
- [x] Degraded docs graph section is transformed to Document trends
allowing the users to switch between Degraded docs and Failed docs
trends over time.
- [x] A new chart for failed documents is created with links to
discover/Logs explorer using the right dataView
🎥 Demo
https://github.com/user-attachments/assets/6a3a1f09-2668-4e83-938e-ecdda798c199
### Failed docs ingestion issue flyout
- [x] Whenever documents are found in failure store we should list
Document indexing failed in Quality issues table
- [x] User should be able to expand Document indexing failed and see
more information in the flyout
- [x] The flyout will show Docs count, an aggregation of the number of
documents inside failure store for the selected timeframe
- [x] The flyout will show Last ocurrence, the datetime registered for
the most recent document in the failure store.
- [x] The flyout will contain a section called Error messages where a
list of unique error messages should be shown, exposing Content (error
message) and Type (Error Type).
- [x] Type should contain a tooltip where message (`Error message
category`) explain users how we are categorising the errors.
- [x] Other issues inside Quality issues table will be appended by field
ignored and the field will be shown in bold.
https://github.com/user-attachments/assets/94dc81f0-9720-4596-b256-c9d289cefd94
Note: This PR was reconstructed from
https://github.com/elastic/kibana/pull/199806 which it supersedes.
## How to test
1. Execute `failed_logs` synthtrace scenario
2. Open dataset quality page
## Follow ups
- Enable in serverless
- Deployment agnostic tests cannot be added until we enable this in
serverless
- FTR tests will be added as part of
https://github.com/elastic/logs-dev/issues/182
---------
Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
2025-01-23 09:13:28 +01:00
Cristina Amico
59e81ee2be
[Fleet] Disallow some egress-specific inputs for agentless integrations ( #206074 )
...
Closes https://github.com/elastic/kibana/issues/202091
## Summary
Disallow some egress-specific inputs for agentless integrations.
- In the policy editor, when Setup technology dropdown is set to
Agentless, hide the rendering of configuration for inputs that have type
matching the blocklist and ensure that these inputs are set to `enabled:
false`
- `tcp, udp, winlog, http_endpoint, filestream` should be disabled when
`supports_agentless: true`
- At the API level, throw an error if attempting to enable a disallowed
input type
### Testing
Simulate agentless env with following setup in `kibana.dev.yml`:
```
xpack.cloud.id: 'anything-to-pass-cloud-validation-checks'
xpack.fleet.agentless.enabled: true
xpack.fleet.agentless.api.url: 'https://localhost:8443 '
xpack.fleet.agentless.api.tls.certificate: './config/certs/ess-client.crt'
xpack.fleet.agentless.api.tls.key: './config/certs/ess-client.key'
xpack.fleet.agentless.api.tls.ca: './config/certs/ca.crt'
```
-Apply [this
patch](https://gist.github.com/jen-huang/dfc3e02ceb63976ad54bd1f50c524cb4 )
to prevent attempt to create agentless pod (the agentless policy
creation fails without the patch)
- Install the following test integration, that has a bunch of different
inputs to simulate this specific case and is enabled for agentless (it
shows the setup technology as well)
[agentless_package_links-0.0.2.zip](https://github.com/user-attachments/files/18425895/agentless_package_links-0.0.2.zip )
```
curl -XPOST -H 'content-type: application/zip' -H 'kbn-xsrf: true' http://localhost:5601/YOUR_PATH/api/fleet/epm/packages -u elastic:changeme --data-binary @agentless_package_links-0.0.2.zip
```
- Navigate to the integrations page, find the above integration and test
that switching between agent-based/agentless the enabled inputs change
as follows:
<img width="1288" alt="Screenshot 2025-01-15 at 15 30 28"
src="https://github.com/user-attachments/assets/6abd45d7-1bd8-465a-af29-4c34940b32e3 "
/>
<img width="1072" alt="Screenshot 2025-01-15 at 15 31 18"
src="https://github.com/user-attachments/assets/6957562f-08a6-403a-8725-1a654e443537 "
/>
- Verify that the preview flyout has the correct inputs based on the
selected deployment mode
<img width="863" alt="Screenshot 2025-01-15 at 15 32 19"
src="https://github.com/user-attachments/assets/ceca1f5d-249c-4ee1-9295-6f01ae21fdb4 "
/>
<img width="862" alt="Screenshot 2025-01-15 at 15 33 33"
src="https://github.com/user-attachments/assets/f43562d7-633e-4f0a-bfc1-19e89aef7659 "
/>
- Verify that the api throws an error when attempting to enable any of
the disallowed types
<img width="1774" alt="Screenshot 2025-01-15 at 15 36 03"
src="https://github.com/user-attachments/assets/2b4d24a3-5adc-4ab2-bbad-83b44d348763 "
/>
### Checklist
- [ ] [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
- [ ] The PR description includes the appropriate Release Notes section,
and the correct `release_note:*` label is applied per the
[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process )
---------
Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
2025-01-22 17:21:54 +01:00
Jan Monschke
1b167d9dc2
[SecuritySolution] Breaking out timeline & note privileges ( #201780 )
...
## Summary
Epic: https://github.com/elastic/security-team/issues/7998
In this PR we're breaking out the `timeline` and `notes` features into
their own feature privilege definition. Previously, access to both
features was granted implicitly through the `siem` feature. However, we
found that this level of access control is not sufficient for all
clients who wanted a more fine-grained way to grant access to parts of
security solution.
In order to break out `timeline` and `notes` from `siem`, we had to
deprecate it feature privilege definition for. That is why you'll find
plenty of changes of `siem` to `siemV2` in this PR. We're making use of
the feature privilege's `replacedBy` functionality, allowing for a
seamless migration of deprecated roles.
This means that roles that previously granted `siem.all` are now granted
`siemV2.all`, `timeline.all` and `notes.all` (same for `*.read`).
Existing users are not impacted and should all still have the correct
access. We added tests to make sure this is working as expected.
Alongside the `ui` privileges, this PR also adds dedicated API tags.
Those tags haven been added to the new and previous version of the
privilege definitions to allow for a clean migration:
```mermaid
flowchart LR
subgraph v1
A(siem) --> Y(all)
A --> X(read)
Y -->|api| W(timeline_write / timeline_read / notes_read / notes_write)
X -->|api| V(timeline_read /notes_read)
end
subgraph v2
A-->|replacedBy| C[siemV2]
A-->|replacedBy| E[timeline]
A-->|replacedBy| G[notes]
E --> L(all)
E --> M(read)
L -->|api| N(timeline_write / timeline_read)
M -->|api| P(timeline_read)
G --> Q(all)
G --> I(read)
Q -->|api| R(notes_write / notes_read)
I -->|api| S(notes_read)
end
```
### Visual changes
#### Hidden/disabled elements
Most of the changes are happening "under" the hood and are only
expressed in case a user has a role with `timeline.none` or
`notes.none`. This would hide and/or disable elements that would usually
allow them to interact with either timeline or the notes feature (within
timeline or the event flyout currently).
As an example, this is how the hover actions look for a user with and
without timeline access:
| With timeline access | Without timeline access |
| --- | --- |
| <img width="616" alt="Screenshot 2024-12-18 at 17 22 49"
src="https://github.com/user-attachments/assets/a767fbb5-49c8-422a-817e-23e7fe1f0042 "
/> | <img width="724" alt="Screenshot 2024-12-18 at 17 23 29"
src="https://github.com/user-attachments/assets/3490306a-d1c3-41aa-af5b-05a1dd804b47 "
/> |
#### Roles
Another visible change of this PR is the addition of `Timeline` and
`Notes` in the edit-role screen:
| Before | After |
| ------- | ------ |
| <img width="746" alt="Screenshot 2024-12-12 at 16 31 43"
src="https://github.com/user-attachments/assets/20a80dd4-c214-48a5-8c6e-3dc19c0cbc43 "
/> | <img width="738" alt="Screenshot 2024-12-12 at 16 32 53"
src="https://github.com/user-attachments/assets/afb1eab4-1729-4c4e-9f51-fddabc32b1dd "
/> |
We made sure that for migrated roles that hard `security.all` selected,
this screen correctly shows `security.all`, `timeline.all` and
`notes.all` after the privilege migration.
#### Timeline toast
There are tons of places in security solution where `Investigate / Add
to timeline` are shown. We did our best to disable all of these actions
but there is no guarantee that this PR catches all the places where we
link to timeline (actions). One layer of extra protection is that the
API endpoints don't give access to timelines to users without the
correct privileges. Another one is a Redux middleware that makes sure
timelines cannot be shown in missed cases. The following toast will be
shown instead of the timeline:
<img width="354" alt="Screenshot 2024-12-19 at 10 34 23"
src="https://github.com/user-attachments/assets/1304005e-2753-4268-b6e7-bd7e22d8a1e3 "
/>
### Changes to predefined security roles
All predefined security roles have been updated to grant the new
privileges (in ESS and serverless). In accordance with the migration,
all roles with `siem.all` have been assigned `siemV2.all`,
`timeline.all` and `notes.all` (and `*.read` respectively).
### Checklist
Check the PR satisfies following conditions.
Reviewers should verify this PR satisfies this list as well.
- [x] Any text added follows [EUI's writing
guidelines](https://elastic.github.io/eui/#/guidelines/writing ), uses
sentence case text and includes [i18n
support](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md )
- [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
- [x] This was checked for breaking HTTP API changes, and any breaking
changes have been approved by the breaking-change committee. The
`release_note:breaking` label should be applied in these situations.
---------
Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
Co-authored-by: PhilippeOberti <philippe.oberti@elastic.co>
Co-authored-by: Steph Milovic <stephanie.milovic@elastic.co>
2025-01-20 14:09:16 +01:00
Sander Philipse
63fc1eae9f
[Search] Add a search guide selector to index onboarding ( #206810 )
...
## Summary
This adds a guide selector to the Kibana index management onboarding
experience.
It also fixes a bug where useQuery was causing us to re-render the page
unnecessarily.
<img width="1284" alt="Screenshot 2025-01-15 at 16 11 48"
src="https://github.com/user-attachments/assets/19abe86f-3148-442a-8e1e-8b6b8eeb2ba1 "
/>
### Checklist
Check the PR satisfies following conditions.
Reviewers should verify this PR satisfies this list as well.
- [x] Any text added follows [EUI's writing
guidelines](https://elastic.github.io/eui/#/guidelines/writing ), uses
sentence case text and includes [i18n
support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md )
- [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
- [x] The PR description includes the appropriate Release Notes section,
and the correct `release_note:*` label is applied per the
[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process )
---------
Co-authored-by: Rodney Norris <rodney@tattdcodemonkey.com>
2025-01-17 18:30:50 +00:00
Robert Jaszczurek
9bc2438eed
[ML] Memory Usage and Notifications pages serverless functional tests ( #205898 )
...
Part of: https://github.com/elastic/kibana/issues/201813
- [x] Memory Usage. Check ML entities are filtered according to the
project type.
- [x] Notifications page. Check ML entities are filtered according to
the project type.
2025-01-17 12:22:34 +01:00
Matthias Wilhelm
a04274723e
[Discover] Remove redundant data fetching when hiding/showing the histogram/chart ( #206389 )
...
Since the timerange in Discover of the main request is stable we don't need to trigger a main fetch for all data when the histogram/chart is being hidden/displayed, unless it's necessary to get the data (e.g. when the histogram/chart was hiden when a discover session was being loaded)
2025-01-17 10:49:37 +00:00
Thom Heymann
75e631bd1f
Unskip test ( #206003 )
...
Resolves https://github.com/elastic/kibana/issues/205545
## Summary
Fix flaky test on dataset quality page
---------
Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
2025-01-17 09:59:21 +00:00
Georgiana-Andreea Onoleață
4f59641f3a
[ResponseOps][Cases] Skipped tests no floating promises fixes ( #206718 )
...
Closes https://github.com/elastic/kibana/issues/191185
## Summary
- un-skipped tests in the following modules:
- ` x-pack/test/functional_with_es_ssl/apps/cases/group1/view_case.ts`
-
`x-pack/test_serverless/functional/test_suites/security/ftr/cases/view_case.ts`
-
`x-pack/test_serverless/functional/test_suites/observability/cases/view_case.ts`
2025-01-17 09:25:23 +02:00
Sonia Sanz Vivas
75e1866915
[Index Management] Test LogsDb Index Template Modifications ( #206548 )
...
Part of https://github.com/elastic/kibana/issues/203716
## Summary
This PR introduces a new test case for LogsDB in both Stateful and
Serverless:
> Verify that users can override LogsDB index settings including:
ignore_above, ignore_malformed, ignore_dynamic_beyond_limit, subobjects
and timestamp format.
For modify `subobjects` and `timestamp` format it must be done from the
mappings tab. For `ignore_above`, `ignore_malformed`,
`ignore_dynamic_beyond_limit` the configuration is done in the Settings
tab.
It also introduces a test case only for Stateful
(enableMappingsSourceFieldSection [is
disabled](9c6de6aabc/config/serverless.yml (L112)
)
for serverless)
> Verify that users cannot disable synthetic source for a LogsDB index.
2025-01-17 07:15:23 +01:00
Jeramy Soucy
31cbf2980f
Skips serverless role management tests ( #206824 )
...
## Summary
Recently enabled ES flag in QA (see
https://github.com/elastic/serverless-gitops/pull/6185 ), caused Kibana
to begin rendering predefined roles on the roles management page. This
caused QA test failures. Skipping these tests will eliminate the noise
in the QA test alert channel while we resolve the issue.
Solution will be to make all predefined roles reserved so we can ensure
they are not rendered in Kibana.
cc @wayneseymour
2025-01-15 18:40:01 +00:00
Tre
ac76690449
[SKIP ON MKI] x-pack/test_serverless/functional/test_suites/observability/dataset_quality/dataset_quality_details.ts ( #206735 )
...
## Summary
see details: https://github.com/elastic/kibana/issues/206734
2025-01-15 14:00:39 +00:00
Xavier Mouligneau
1d52062c2c
[CLOUD] Intercept query string ( #204129 )
...
## Summary
This PR in cloud https://github.com/elastic/cloud/pull/135346 is going
to pass an `onboarding_token` query string. I am just trying to
Intercept it and saved it. Therefore solution can streamline the Kibana
onboarding process for trial user.
### Checklist
- [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
---------
Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
2025-01-13 23:09:50 +00:00
Arturo Lidueña
ee6c5bde34
Observability AI Assistant Tests Deployment Agnostic ( #205194 )
...
Closes #192718
## Summary
This PR add a deployment-agnostic testing environment for Observability
AI Assistant tests by unifying the duplicated tests for stateful and
serverless environments. It create the ObservabilityAIAssistantApiClient
to work seamlessly in both environments, enabling a single test to run
across stateful, CI, and MKI.
Initial efforts focus on deduplicating the `conversations.spec.ts` and
`connectors.spec.ts` files, as these already run in all environments.
Move / dedup the tests that exist in stateful and serverless. They run
in serverless CI but not MKI and add the skipMki tag.
`chat.spec.ts`
`complete.spec.ts`
`elasticsearch.spec.ts`
`public_complete.spec.ts`
`alerts.spec.ts`
`knowledge_base_setup.spec.ts`
`knowledge_base_status.spec.ts`
`knowledge_base.spec.ts`
`summarize.ts`
`knowledge_base_user_instructions.spec.ts`
2025-01-13 16:03:51 +01:00
Dzmitry Lemechko
ecf1818608
[kbn-test] export fleet package registry image ( #206234 )
...
## Summary
Should fix TS check error `Project references may not form a circular
graph` by removing `@kbn/test-suites-xpack` from `kbn-scout` dependency
list.
Since dockerImage for Fleet package registry is just a constant, that is
used across different FTR and Scout configurations, it makes sense to
export it from `kbn-test`
2025-01-10 17:44:06 +01:00
Alejandro Fernández Haro
d0abdbdb7e
[ES body
removal] @elastic/search-kibana
( #204876 )
2025-01-10 14:54:23 +00:00
Anton Dosov
64b6a1a5e7
Sustainable Kibana Architecture: Move the rest of shared-ux modules ( #205924 )
...
## Summary
This PR aims at relocating some of the Kibana modules (plugins and
packages) into a new folder structure, according to the _Sustainable
Kibana Architecture_ initiative.
> [!IMPORTANT]
> * We kindly ask you to:
> * Manually fix the errors in the error section below (if there are
any).
> * Search for the `packages[\/\\]` and `plugins[\/\\]` patterns in the
source code (Babel and Eslint config files), and update them
appropriately.
> * Manually review
`.buildkite/scripts/pipelines/pull_request/pipeline.ts` to ensure that
any CI pipeline customizations continue to be correctly applied after
the changed path names
> * Review all of the updated files, specially the `.ts` and `.js` files
listed in the sections below, as some of them contain relative paths
that have been updated.
> * Think of potential impact of the move, including tooling and
configuration files that can be pointing to the relocated modules. E.g.:
> * customised eslint rules
> * docs pointing to source code
> [!NOTE]
> * This PR has been auto-generated.
> * Any manual contributions will be lost if the 'relocate' script is
re-run.
> * Try to obtain the missing reviews / approvals before applying manual
fixes, and/or keep your changes in a .patch / git stash.
> * Please use
[#sustainable_kibana_architecture](https://elastic.slack.com/archives/C07TCKTA22E )
Slack channel for feedback.
Are you trying to rebase this PR to solve merge conflicts? Please follow
the steps describe
[here](https://elastic.slack.com/archives/C07TCKTA22E/p1734019532879269?thread_ts=1734019339.935419&cid=C07TCKTA22E ).
#### 1 plugin(s) are going to be relocated:
| Id | Target folder |
| -- | ------------- |
| `@kbn/url-drilldown-plugin` |
`x-pack/platform/plugins/private/drilldowns/url_drilldown` |
#### 21 packages(s) are going to be relocated:
| Id | Target folder |
| -- | ------------- |
| `@kbn/core-chrome-browser` | `src/core/packages/chrome/browser` |
| `@kbn/deeplinks-shared` |
`src/platform/packages/shared/deeplinks/shared` |
| `@kbn/home-sample-data-card` |
`src/platform/packages/shared/home/sample_data_card` |
| `@kbn/home-sample-data-tab` |
`src/platform/packages/shared/home/sample_data_tab` |
| `@kbn/home-sample-data-types` |
`src/platform/packages/shared/home/sample_data_types` |
| `@kbn/guided-onboarding` |
`src/platform/packages/shared/kbn-guided-onboarding` |
| `@kbn/item-buffer` | `src/platform/packages/private/kbn-item-buffer` |
| `@kbn/management-settings-section-registry` |
`src/platform/packages/shared/kbn-management/settings/section_registry`
|
| `@kbn/management-settings-ids` |
`src/platform/packages/shared/kbn-management/settings/setting_ids` |
| `@kbn/react-mute-legacy-root-warning` |
`src/platform/packages/private/kbn-react-mute-legacy-root-warning` |
| `@kbn/saved-objects-settings` |
`src/platform/packages/private/kbn-saved-objects-settings` |
| `@kbn/react-kibana-context-common` |
`src/platform/packages/shared/react/kibana_context/common` |
| `@kbn/react-kibana-context-render` |
`src/platform/packages/shared/react/kibana_context/render` |
| `@kbn/react-kibana-context-root` |
`src/platform/packages/shared/react/kibana_context/root` |
| `@kbn/react-kibana-context-styled` |
`src/platform/packages/shared/react/kibana_context/styled` |
| `@kbn/react-kibana-context-theme` |
`src/platform/packages/shared/react/kibana_context/theme` |
| `@kbn/react-kibana-mount` |
`src/platform/packages/shared/react/kibana_mount` |
| `@kbn/serverless-project-switcher` |
`src/platform/packages/private/serverless/project_switcher` |
| `@kbn/serverless-common-settings` |
`src/platform/packages/private/serverless/settings/common` |
| `@kbn/serverless-observability-settings` |
`src/platform/packages/shared/serverless/settings/observability_project`
|
| `@kbn/serverless-types` |
`src/platform/packages/private/serverless/types` |
<details >
<summary>Updated relative paths</summary>
```
src/core/packages/chrome/browser/jest.config.js:12
src/core/packages/chrome/browser/tsconfig.json:2
src/core/packages/chrome/browser/tsconfig.type_check.json:2
src/core/packages/chrome/browser/tsconfig.type_check.json:21
src/core/packages/chrome/browser/tsconfig.type_check.json:24
src/core/packages/chrome/browser/tsconfig.type_check.json:27
src/core/packages/chrome/browser/tsconfig.type_check.json:30
src/core/packages/chrome/browser/tsconfig.type_check.json:33
src/core/packages/chrome/browser/tsconfig.type_check.json:36
src/core/packages/chrome/browser/tsconfig.type_check.json:39
src/core/packages/chrome/browser/tsconfig.type_check.json:42
src/core/packages/chrome/browser/tsconfig.type_check.json:45
src/core/packages/chrome/browser/tsconfig.type_check.json:48
src/core/packages/chrome/browser/tsconfig.type_check.json:51
src/core/packages/chrome/browser/tsconfig.type_check.json:54
src/platform/packages/private/kbn-item-buffer/jest.config.js:12
src/platform/packages/private/kbn-item-buffer/tsconfig.json:2
src/platform/packages/private/kbn-react-mute-legacy-root-warning/jest.config.js:12
src/platform/packages/private/kbn-react-mute-legacy-root-warning/tsconfig.json:2
src/platform/packages/private/kbn-saved-objects-settings/jest.config.js:12
src/platform/packages/private/kbn-saved-objects-settings/tsconfig.json:2
src/platform/packages/private/kbn-saved-objects-settings/tsconfig.type_check.json:2
src/platform/packages/private/serverless/project_switcher/jest.config.js:12
src/platform/packages/private/serverless/project_switcher/tsconfig.json:2
src/platform/packages/private/serverless/project_switcher/tsconfig.type_check.json:2
src/platform/packages/private/serverless/project_switcher/tsconfig.type_check.json:23
src/platform/packages/private/serverless/settings/common/tsconfig.json:2
src/platform/packages/private/serverless/settings/common/tsconfig.type_check.json:2
src/platform/packages/private/serverless/settings/common/tsconfig.type_check.json:20
src/platform/packages/private/serverless/types/tsconfig.json:2
src/platform/packages/private/serverless/types/tsconfig.type_check.json:2
src/platform/packages/shared/deeplinks/shared/jest.config.js:12
src/platform/packages/shared/deeplinks/shared/tsconfig.json:2
src/platform/packages/shared/deeplinks/shared/tsconfig.type_check.json:2
src/platform/packages/shared/home/sample_data_card/jest.config.js:12
src/platform/packages/shared/home/sample_data_card/tsconfig.json:2
src/platform/packages/shared/home/sample_data_card/tsconfig.type_check.json:2
src/platform/packages/shared/home/sample_data_card/tsconfig.type_check.json:23
src/platform/packages/shared/home/sample_data_card/tsconfig.type_check.json:29
src/platform/packages/shared/home/sample_data_tab/jest.config.js:12
src/platform/packages/shared/home/sample_data_tab/tsconfig.json:2
src/platform/packages/shared/home/sample_data_tab/tsconfig.type_check.json:2
src/platform/packages/shared/home/sample_data_tab/tsconfig.type_check.json:23
src/platform/packages/shared/home/sample_data_types/jest.config.js:12
src/platform/packages/shared/home/sample_data_types/tsconfig.json:2
src/platform/packages/shared/home/sample_data_types/tsconfig.type_check.json:2
src/platform/packages/shared/kbn-guided-onboarding/jest.config.js:12
src/platform/packages/shared/kbn-guided-onboarding/tsconfig.json:2
src/platform/packages/shared/kbn-guided-onboarding/tsconfig.type_check.json:2
src/platform/packages/shared/kbn-management/settings/section_registry/tsconfig.json:2
src/platform/packages/shared/kbn-management/settings/section_registry/tsconfig.type_check.json:2
src/platform/packages/shared/kbn-management/settings/section_registry/tsconfig.type_check.json:22
src/platform/packages/shared/kbn-management/settings/section_registry/tsconfig.type_check.json:25
src/platform/packages/shared/kbn-management/settings/setting_ids/tsconfig.json:2
src/platform/packages/shared/kbn-management/settings/setting_ids/tsconfig.type_check.json:2
src/platform/packages/shared/react/kibana_context/common/jest.config.js:12
src/platform/packages/shared/react/kibana_context/common/tsconfig.json:2
src/platform/packages/shared/react/kibana_context/common/tsconfig.type_check.json:2
src/platform/packages/shared/react/kibana_context/render/jest.config.js:12
src/platform/packages/shared/react/kibana_context/render/tsconfig.json:2
src/platform/packages/shared/react/kibana_context/render/tsconfig.type_check.json:2
src/platform/packages/shared/react/kibana_context/render/tsconfig.type_check.json:25
src/platform/packages/shared/react/kibana_context/root/jest.config.js:12
src/platform/packages/shared/react/kibana_context/root/tsconfig.json:2
src/platform/packages/shared/react/kibana_context/root/tsconfig.type_check.json:2
src/platform/packages/shared/react/kibana_context/root/tsconfig.type_check.json:22
src/platform/packages/shared/react/kibana_context/root/tsconfig.type_check.json:28
src/platform/packages/shared/react/kibana_context/root/tsconfig.type_check.json:31
src/platform/packages/shared/react/kibana_context/root/tsconfig.type_check.json:34
src/platform/packages/shared/react/kibana_context/root/tsconfig.type_check.json:37
src/platform/packages/shared/react/kibana_context/root/tsconfig.type_check.json:40
src/platform/packages/shared/react/kibana_context/styled/jest.config.js:12
src/platform/packages/shared/react/kibana_context/styled/tsconfig.json:2
src/platform/packages/shared/react/kibana_context/styled/tsconfig.type_check.json:2
src/platform/packages/shared/react/kibana_context/styled/tsconfig.type_check.json:22
src/platform/packages/shared/react/kibana_context/theme/jest.config.js:12
src/platform/packages/shared/react/kibana_context/theme/tsconfig.json:2
src/platform/packages/shared/react/kibana_context/theme/tsconfig.type_check.json:2
src/platform/packages/shared/react/kibana_context/theme/tsconfig.type_check.json:22
src/platform/packages/shared/react/kibana_mount/jest.config.js:12
src/platform/packages/shared/react/kibana_mount/tsconfig.json:2
src/platform/packages/shared/react/kibana_mount/tsconfig.type_check.json:2
src/platform/packages/shared/react/kibana_mount/tsconfig.type_check.json:22
src/platform/packages/shared/react/kibana_mount/tsconfig.type_check.json:25
src/platform/packages/shared/react/kibana_mount/tsconfig.type_check.json:28
src/platform/packages/shared/react/kibana_mount/tsconfig.type_check.json:34
src/platform/packages/shared/serverless/settings/observability_project/tsconfig.json:2
src/platform/packages/shared/serverless/settings/observability_project/tsconfig.type_check.json:2
src/platform/packages/shared/serverless/settings/observability_project/tsconfig.type_check.json:20
x-pack/platform/plugins/private/drilldowns/url_drilldown/tsconfig.json:2
```
</details>
---------
Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
2025-01-10 11:30:37 +00:00
Jedr Blaszyk
542a56b482
[Search serverless / Connectors FTRs] Update test role to developer ( #206067 )
...
## Summary
`viewer` role is not sufficient to call Connector APIs with new change
https://github.com/elastic/elasticsearch/pull/119863
Update the FTR tests to use developer role for testing
2025-01-09 15:45:30 +00:00
Viduni Wickramarachchi
37d7a5efb7
[Obs AI Assistant] Unskip user instructions test ( #205656 ) ( #205897 )
...
Closes https://github.com/elastic/kibana/issues/205656
## Summary
### Problem
There seems to be a race condition and state contamination between tests
in the KB user instructions tests.
### Solution
- Clear knowledge base and conversations after tests
- Remove title interceptor --> we don't need title interception for
these tests
### Checklist
- [x] [Flaky Test
Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1 ) was
used on any tests changed
- [x] The PR description includes the appropriate Release Notes section,
and the correct `release_note:*` label is applied per the
[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process )
2025-01-09 10:01:15 -05:00
Sonia Sanz Vivas
bcdf942b94
Add waitUntilLoadingHasFinished in failing tests ( #205485 )
...
Fixes: https://github.com/elastic/kibana/issues/205535
Fixes: https://github.com/elastic/kibana/issues/205514
Fixes: https://github.com/elastic/kibana/issues/205498
Fixes: https://github.com/elastic/kibana/issues/205464
Fixes: https://github.com/elastic/kibana/issues/205456
Fixes: https://github.com/elastic/kibana/issues/205453
Fixes: https://github.com/elastic/kibana/issues/205450
Fixes: https://github.com/elastic/kibana/issues/205412
Fixes: https://github.com/elastic/kibana/issues/205410
Fixes: https://github.com/elastic/kibana/issues/205401
Fixes: https://github.com/elastic/kibana/issues/205400
Fixes: https://github.com/elastic/kibana/issues/205399
Fixes: https://github.com/elastic/kibana/issues/205350
Fixes: https://github.com/elastic/kibana/issues/205349
Fixes: https://github.com/elastic/kibana/issues/205316
Fixes: https://github.com/elastic/kibana/issues/205288
Fixes: https://github.com/elastic/kibana/issues/205287
## Summary
It seems that the step tabs are not loading fast enough for the tests to
find the expected element in a [bunch of
test](https://github.com/elastic/kibana/issues?q=is%3Aopen%20label%3A%22Team%3AKibana%20Management%22%20label%3A%22failed-test%22%20created%3A%3E%40today-1w%20 ).
This PR attempt to fix it. It also adds the
`data-test-subj="indexModeValue"` tag in `TabSummary` that was missing.
2025-01-08 11:51:34 +01:00
Kibana Machine
7de3514828
skip failing test suite ( #205656 )
2025-01-08 15:11:11 +11:00
Viduni Wickramarachchi
e32ff8e9f3
[Obs AI Assistant] Add knowledge base migration test to the serverless test suite ( #205631 )
...
Closes https://github.com/elastic/kibana/issues/205537
## Summary
The knowledge base migration test suite is missing in serverless. This
PR adds it to the serverless test suite.
- This has a dependancy to https://github.com/elastic/kibana/pull/205194
since we are removing all serverless tests and adding them to DA tests.
- If the DA tests PR gets merged first, I'll refactor this PR to add it
there.
### Checklist
- [ ] [Flaky Test
Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1 ) was
used on any tests changed
- [x] The PR description includes the appropriate Release Notes section,
and the correct `release_note:*` label is applied per the
[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process )
2025-01-07 20:46:51 -05:00
Tre
fbc033c226
[MKI] Fix flaky search source alert test ( #205481 )
...
## Summary
Use settings
[method](c8d46ee949/test/functional/page_objects/settings_page.ts (L648)
)
instead of naive typing.
Naive only because the asterisk at the end of the text box is better
handled in the settings method.
2025-01-07 12:02:39 +00:00
Robert Oskamp
7e82712ab9
Skip serverless AI assistant knowledge base status tests on MKI ( #205678 )
...
## Summary
This PR skips the serverless API integration tests for Observability AI
assistant knowledge base status for MKI runs.
Details in #205677
2025-01-07 11:48:14 +01:00
Konrad Szwarc
2f61892e84
[EDR Workflows] Workflow Insights - RBAC ( #205088 )
...
## Access Control for Endpoint Workflow Insights
This PR adds access control to the Endpoint Workflow Insights
functionality. Both the UI and API are gated based on the following
conditions. If these conditions are not met, the content will not
render, and direct API calls will return errors.
Access Conditions
```
1. Serverless: Requires the Endpoint Complete Tier.
2. ESS: Requires an Enterprise License.
3. User Privileges:
3.1 Endpoint Insights Privilege must be enabled:
3.1.1 Endpoint Insights All: Grants full access.
3.1.2 Endpoint Insights Read:
3.1.2.1 Allows users to view generated insights but prevents triggering new scans.
3.1.2.2 With Trusted Applications privilege: Users can remediate already generated insights.
3.1.2.3 Without Trusted Applications privilege: No actions can be taken.
3.1.3Endpoint Insights None: The section is not rendered.
```
Predefined serverless roles that should include endpoint insights
privilege(as defined
[here](https://github.com/elastic/security-team/issues/11460 )):
- Tier 3 analyst
- Rule Author
- SOC Manager
- Endpoint Operations Analyst
- Endpoint Policy Manager
- Platform Engineer
Once this PR is merged and changes make it to canary release, [this
follow-up
PR](https://github.com/elastic/elasticsearch-controller/pull/816 ) should
be merged.
Note on Testing and Local Setup
To test these changes locally, the `defendInsights` assistant feature
must be enabled. You can do this by updating the following line in the
code: [Enable defendInsights
here](2ae68bdaac/x-pack/platform/packages/shared/kbn-elastic-assistant-common/impl/capabilities/index.ts (L23)
).
Cypress Tests
Cypress tests in this PR are currently skipped because the
`defendInsights` feature is not enabled by default. These tests should
be enabled once the feature is turned on in the main branch. Successful
run with all cypress tests enabled can be found
[here](https://buildkite.com/elastic/kibana-pull-request/builds/262774#0193f3c2-eddd-48b6-9103-fb7338304f15 ).
<details>
<summary>Screenshots</summary>





</details>
---------
Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
2025-01-07 09:33:25 +00:00
Kibana Machine
2fc2019c83
skip failing test suite ( #205545 )
2025-01-07 06:28:28 +11:00
Efe Gürkan YALAMAN
e542fd2370
[Synonyms UI] Synonyms UI base plugin ( #203284 )
...
## Summary
Creates a plugin for Synonyms UI implementation. It is hidden under the
UI flag and config option which is off by default.
```
POST kbn:/internal/kibana/settings/searchSynonyms:synonymsEnabled
{"value": true}
```
Serverless Search:
<img width="379" alt="Screenshot 2024-12-17 at 13 18 02"
src="https://github.com/user-attachments/assets/8c2cb6f0-ce2a-4be6-8605-4f994adeefd7 "
/>
Stack Search
<img width="293" alt="Screenshot 2024-12-17 at 13 21 43"
src="https://github.com/user-attachments/assets/0d61de0e-2cd3-46a6-990f-1f1a70843324 "
/>
### Checklist
Check the PR satisfies following conditions.
Reviewers should verify this PR satisfies this list as well.
- [x] Any text added follows [EUI's writing
guidelines](https://elastic.github.io/eui/#/guidelines/writing ), uses
sentence case text and includes [i18n
support](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md )
- [ ]
[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html )
was added for features that require explanation or tutorials
- [ ] [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
- [x] This was checked for breaking HTTP API changes, and any breaking
changes have been approved by the breaking-change committee. The
`release_note:breaking` label should be applied in these situations.
- [ ] [Flaky Test
Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1 ) was
used on any tests changed
- [x] The PR description includes the appropriate Release Notes section,
and the correct `release_note:*` label is applied per the
[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process )
---------
Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
2025-01-06 19:15:19 +00:00
Robert Oskamp
69cb96654b
Skip serverless AI assistant knowledge base tests on MKI ( #205582 )
...
## Summary
This PR skips the serverless API integration tests for Observability AI
assistant knowledge base for MKI runs.
Details in #205581
2025-01-06 11:07:24 +01:00
Sandra G
b17b10eea1
[Obs AI Assistant] unskip kb user instructions test in serverless ( #205519 )
...
## Summary
Resolves https://github.com/elastic/kibana/issues/192886
- Unskips `knowledge_base_user_instructions.spec.ts` in serverless
- stays skipped in mki due to proxy usage issue
- Duplicates new changes from non serverless
- Removes `skipInMKI` tags for:
`knowledge_base_setup.spec.ts`
`knowledge_base.spec.ts `
`knowledge_base_status.spec.ts`
If https://github.com/elastic/kibana/issues/192718 is merged before
this, I will move `knowledge_base_user_instructions.spec.ts` to
deployment agnostic. Otherwise It can be done in that PR or another.
2025-01-04 16:32:32 -05:00
Kibana Machine
326ca3e2da
skip failing test suite ( #205316 )
2025-01-04 08:41:42 +11:00
Viduni Wickramarachchi
f7b9d15df4
[Obs AI Assistant] Add alerts test to serverless ( #205524 ) ( #205530 )
...
Closes https://github.com/elastic/kibana/issues/205524
## Summary
Adds the alerts.spec to serverless tests. It's skipped in MKI because of
the LLM proxy. There is an open issue for this -
https://github.com/elastic/kibana/issues/192751
### Checklist
- [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
- [x] The PR description includes the appropriate Release Notes section,
and the correct `release_note:*` label is applied per the
[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process )
2025-01-03 16:01:05 -05:00
Thom Heymann
8902f7026c
Remove links to Logs Explorer ( #203685 )
...
Resolves https://github.com/elastic/kibana/issues/182229
## Release Note
Remove Logs Explorer
## Summary
- Removes the Discover/Logs Explorer tabs in the top nav
- Changes all links to Logs Explorer in other applications to Discover
- Removes all APIs exposed by Logs Explorer
Note: This does not remove Logs Explorer from the codebase. There will
be a follow up for that work.
---------
Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
2025-01-03 17:25:13 +00:00
Viduni Wickramarachchi
7d76276d8b
[Obs AI Assistant] Add route privilege tests for Serverless ( #205210 )
...
Closes https://github.com/elastic/kibana/issues/204884
## Summary
This PR adds security and route privilege tests to the serverless test
suite.
### Checklist
- [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
- [x] [Flaky Test
Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1 ) was
used on any tests changed
- [x] The PR description includes the appropriate Release Notes section,
and the correct `release_note:*` label is applied per the
[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process )
2025-01-03 11:17:43 -05:00
Viduni Wickramarachchi
a5909f391f
[Obs AI Assistant] Add tokenCount event to complete event stream in serverless tests ( #205397 )
...
Closes https://github.com/elastic/kibana/issues/203407
https://github.com/elastic/kibana/issues/203408
https://github.com/elastic/kibana/issues/203478
## Summary
### Problem
Some tests in serverless are failing after the migration to the
Inference endpoints. This is due to not emitting the tokenCount event,
which enables successfully closing the stream.
### Solution
Emit the tokenCount event in the serverless tests when the title or
conversation is simulated.
### Checklist
- [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
- [x] The PR description includes the appropriate Release Notes section,
and the correct `release_note:*` label is applied per the
[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process )
2025-01-02 19:24:30 -05:00
Mykola Harmash
db083d17fc
[Onboarding][Firehose] Switch to the latest CloudFormation template ( #204185 )
...
Closes https://github.com/elastic/kibana/issues/203563
Updates the CF template to the latest available version and adjust the
code to use a single Firehose stream created by the new template.
You can use `Elastic Observability` AWS account (available through Okta)
and the latest Kibana deployment from this PR to test the flow.

2025-01-02 05:39:58 -06:00
Sonia Sanz Vivas
34341e5864
Functional test for create a logdb index ( #204788 )
...
Part of https://github.com/elastic/kibana/issues/203716
## Summary
* Functional test for verifying that users can create indices using the
“logsdb” index mode via the Kibana interface (Stateful and serverless).
* Functional test for verifying that users can upgrade a logs data
stream that is using a “standard” index mode to a data stream using
“logsdb” index mode. (Stateful and serverless).
* Functional test for verifying that users can downgrade a data stream
that is using a “logsdb” index mode to a data stream using “standard”
index mode. (Stateful and serverless).
* Functional test for verifying that users can upgrade a data stream
that is using a “time series” index mode to a data stream using “logsdb”
index mode. (Stateful and serverless).
* Functional test for verifying that users can downgrade a data stream
that is using a “logsdb” index mode to a data stream using “time series”
index mode. (Stateful and serverless).
The rollover operation has not been tested since is not expected to
happen automatically. See [this
comment](https://github.com/elastic/kibana/issues/203716#issuecomment-2554491054 ).
2024-12-30 11:39:49 -06:00
Abdul Wahab Zahid
bd9254fe1e
[Dataset Quality] Fix failing es-promotion test on 8.x
( #205188 )
...
Newer builds of ES ingest `event.ingested` and `tags` fields into APM
indices making the Dataset Quality tests fail which rely on ingested
field counts against set number of field limits. The PR addresses this
by explicitly ingesting the fields beforehand.
After the merge to main, the PR will be backported to `8.x` to unblock
es-promotion.
2024-12-30 12:46:49 +01:00
Gerard Soldevila
380a879911
Sustainable Kibana Architecture: Move modules owned by @elastic/search-kibana
( #202837 )
...
## Summary
This PR aims at relocating some of the Kibana modules (plugins and
packages) into a new folder structure, according to the _Sustainable
Kibana Architecture_ initiative.
> [!IMPORTANT]
> * We kindly ask you to:
> * Manually fix the errors in the error section below (if there are
any).
> * Search for the `packages[\/\\]` and `plugins[\/\\]` patterns in the
source code (Babel and Eslint config files), and update them
appropriately.
> * Manually review
`.buildkite/scripts/pipelines/pull_request/pipeline.ts` to ensure that
any CI pipeline customizations continue to be correctly applied after
the changed path names
> * Review all of the updated files, specially the `.ts` and `.js` files
listed in the sections below, as some of them contain relative paths
that have been updated.
> * Think of potential impact of the move, including tooling and
configuration files that can be pointing to the relocated modules. E.g.:
> * customised eslint rules
> * docs pointing to source code
> [!NOTE]
> * This PR has been auto-generated.
> * Any manual contributions will be lost if the 'relocate' script is
re-run.
> * Try to obtain the missing reviews / approvals before applying manual
fixes, and/or keep your changes in a .patch / git stash.
> * Please use
[#sustainable_kibana_architecture](https://elastic.slack.com/archives/C07TCKTA22E )
Slack channel for feedback.
Are you trying to rebase this PR to solve merge conflicts? Please follow
the steps describe
[here](https://elastic.slack.com/archives/C07TCKTA22E/p1734019532879269?thread_ts=1734019339.935419&cid=C07TCKTA22E ).
#### 10 plugin(s) are going to be relocated:
| Id | Target folder |
| -- | ------------- |
| `@kbn/enterprise-search-plugin` |
`x-pack/solutions/search/plugins/enterprise_search` |
| `@kbn/search-assistant` |
`x-pack/solutions/search/plugins/search_assistant` |
| `@kbn/search-connectors-plugin` |
`x-pack/solutions/search/plugins/search_connectors` |
| `@kbn/search-homepage` |
`x-pack/solutions/search/plugins/search_homepage` |
| `@kbn/search-indices` |
`x-pack/solutions/search/plugins/search_indices` |
| `@kbn/search-inference-endpoints` |
`x-pack/solutions/search/plugins/search_inference_endpoints` |
| `@kbn/search-navigation` |
`x-pack/solutions/search/plugins/search_solution/search_navigation` |
| `@kbn/search-notebooks` |
`x-pack/solutions/search/plugins/search_notebooks` |
| `@kbn/search-playground` |
`x-pack/solutions/search/plugins/search_playground` |
| `@kbn/serverless-search` |
`x-pack/solutions/search/plugins/serverless_search` |
#### 11 packages(s) are going to be relocated:
| Id | Target folder |
| -- | ------------- |
| `@kbn/ai-assistant` |
`x-pack/platform/packages/shared/kbn-ai-assistant` |
| `@kbn/deeplinks-search` |
`src/platform/packages/shared/deeplinks/search` |
| `@kbn/ipynb` | `x-pack/solutions/search/packages/kbn-ipynb` |
| `@kbn/search-api-keys-components` |
`x-pack/solutions/search/packages/kbn-search-api-keys-components` |
| `@kbn/search-api-keys-server` |
`x-pack/solutions/search/packages/kbn-search-api-keys-server` |
| `@kbn/search-api-panels` |
`src/platform/packages/shared/kbn-search-api-panels` |
| `@kbn/search-connectors` |
`src/platform/packages/shared/kbn-search-connectors` |
| `@kbn/search-index-documents` |
`x-pack/solutions/search/packages/kbn-search-index-documents` |
| `@kbn/search-shared-ui` |
`x-pack/solutions/search/packages/search/shared_ui` |
| `@kbn/serverless-search-settings` |
`src/platform/packages/shared/serverless/settings/search_project` |
| `@kbn/try-in-console` |
`src/platform/packages/shared/kbn-try-in-console` |
<details open>
<summary>Script errors</summary>
```
Cannot replace multiple occurrences of "../.." in the same line, please fix manually: /Users/pgayvallet/DEV/workspaces/elastic/kibana/x-pack/solutions/search/plugins/enterprise_search/cypress.sh:17
Cannot replace multiple occurrences of "../.." in the same line, please fix manually: /Users/pgayvallet/DEV/workspaces/elastic/kibana/x-pack/solutions/search/plugins/enterprise_search/cypress.sh:19
```
</details><details >
<summary>Updated relative paths</summary>
```
src/platform/packages/shared/deeplinks/search/jest.config.js:12
src/platform/packages/shared/deeplinks/search/tsconfig.json:2
src/platform/packages/shared/deeplinks/search/tsconfig.type_check.json:2
src/platform/packages/shared/kbn-search-api-panels/jest.config.js:12
src/platform/packages/shared/kbn-search-api-panels/tsconfig.json:2
src/platform/packages/shared/kbn-search-api-panels/tsconfig.type_check.json:2
src/platform/packages/shared/kbn-search-api-panels/tsconfig.type_check.json:28
src/platform/packages/shared/kbn-search-api-panels/tsconfig.type_check.json:34
src/platform/packages/shared/kbn-search-api-panels/tsconfig.type_check.json:37
src/platform/packages/shared/kbn-search-connectors/jest.config.js:12
src/platform/packages/shared/kbn-search-connectors/tsconfig.json:2
src/platform/packages/shared/kbn-search-connectors/tsconfig.type_check.json:2
src/platform/packages/shared/kbn-search-connectors/tsconfig.type_check.json:27
src/platform/packages/shared/kbn-try-in-console/jest.config.js:12
src/platform/packages/shared/kbn-try-in-console/tsconfig.json:2
src/platform/packages/shared/kbn-try-in-console/tsconfig.type_check.json:2
src/platform/packages/shared/kbn-try-in-console/tsconfig.type_check.json:29
src/platform/packages/shared/kbn-try-in-console/tsconfig.type_check.json:32
src/platform/packages/shared/serverless/settings/search_project/tsconfig.json:2
src/platform/packages/shared/serverless/settings/search_project/tsconfig.type_check.json:2
src/platform/packages/shared/serverless/settings/search_project/tsconfig.type_check.json:20
src/platform/packages/shared/serverless/settings/search_project/tsconfig.type_check.json:23
x-pack/platform/packages/shared/kbn-ai-assistant/.storybook/main.ts:14
x-pack/platform/packages/shared/kbn-ai-assistant/jest.config.js:16
x-pack/platform/packages/shared/kbn-ai-assistant/tsconfig.json:2
x-pack/platform/packages/shared/kbn-ai-assistant/tsconfig.type_check.json:2
x-pack/platform/packages/shared/kbn-ai-assistant/tsconfig.type_check.json:23
x-pack/platform/packages/shared/kbn-ai-assistant/tsconfig.type_check.json:26
x-pack/platform/packages/shared/kbn-ai-assistant/tsconfig.type_check.json:29
x-pack/platform/packages/shared/kbn-ai-assistant/tsconfig.type_check.json:32
x-pack/platform/packages/shared/kbn-ai-assistant/tsconfig.type_check.json:35
x-pack/platform/packages/shared/kbn-ai-assistant/tsconfig.type_check.json:38
x-pack/platform/packages/shared/kbn-ai-assistant/tsconfig.type_check.json:41
x-pack/platform/packages/shared/kbn-ai-assistant/tsconfig.type_check.json:44
x-pack/platform/packages/shared/kbn-ai-assistant/tsconfig.type_check.json:47
x-pack/platform/packages/shared/kbn-ai-assistant/tsconfig.type_check.json:50
x-pack/platform/packages/shared/kbn-ai-assistant/tsconfig.type_check.json:53
x-pack/platform/packages/shared/kbn-ai-assistant/tsconfig.type_check.json:56
x-pack/platform/packages/shared/kbn-ai-assistant/tsconfig.type_check.json:59
x-pack/platform/packages/shared/kbn-ai-assistant/tsconfig.type_check.json:62
x-pack/platform/packages/shared/kbn-ai-assistant/tsconfig.type_check.json:65
x-pack/platform/packages/shared/kbn-ai-assistant/tsconfig.type_check.json:68
x-pack/platform/packages/shared/kbn-ai-assistant/tsconfig.type_check.json:71
x-pack/platform/packages/shared/kbn-ai-assistant/tsconfig.type_check.json:74
x-pack/solutions/search/packages/kbn-ipynb/jest.config.js:12
x-pack/solutions/search/packages/kbn-ipynb/tsconfig.json:2
x-pack/solutions/search/packages/kbn-ipynb/tsconfig.type_check.json:2
x-pack/solutions/search/packages/kbn-search-api-keys-components/jest.config.js:12
x-pack/solutions/search/packages/kbn-search-api-keys-components/tsconfig.json:2
x-pack/solutions/search/packages/kbn-search-api-keys-components/tsconfig.type_check.json:2
x-pack/solutions/search/packages/kbn-search-api-keys-components/tsconfig.type_check.json:23
x-pack/solutions/search/packages/kbn-search-api-keys-components/tsconfig.type_check.json:26
x-pack/solutions/search/packages/kbn-search-api-keys-components/tsconfig.type_check.json:29
x-pack/solutions/search/packages/kbn-search-api-keys-server/jest.config.js:12
x-pack/solutions/search/packages/kbn-search-api-keys-server/tsconfig.json:2
x-pack/solutions/search/packages/kbn-search-api-keys-server/tsconfig.type_check.json:2
x-pack/solutions/search/packages/kbn-search-api-keys-server/tsconfig.type_check.json:24
x-pack/solutions/search/packages/kbn-search-index-documents/README.md:11
x-pack/solutions/search/packages/kbn-search-index-documents/jest.config.js:12
x-pack/solutions/search/packages/kbn-search-index-documents/tsconfig.json:2
x-pack/solutions/search/packages/kbn-search-index-documents/tsconfig.type_check.json:2
x-pack/solutions/search/packages/kbn-search-index-documents/tsconfig.type_check.json:31
x-pack/solutions/search/packages/search/shared_ui/jest.config.js:13
x-pack/solutions/search/packages/search/shared_ui/tsconfig.json:2
x-pack/solutions/search/packages/search/shared_ui/tsconfig.type_check.json:2
x-pack/solutions/search/packages/search/shared_ui/tsconfig.type_check.json:23
x-pack/solutions/search/plugins/enterprise_search/README.md:138
x-pack/solutions/search/plugins/enterprise_search/README.md:140
x-pack/solutions/search/plugins/enterprise_search/common/jest.config.js:10
x-pack/solutions/search/plugins/enterprise_search/cypress.config.js:20
x-pack/solutions/search/plugins/enterprise_search/cypress.config.js:23
x-pack/solutions/search/plugins/enterprise_search/cypress.config.ts:20
x-pack/solutions/search/plugins/enterprise_search/cypress.config.ts:23
x-pack/solutions/search/plugins/enterprise_search/cypress.sh:17
x-pack/solutions/search/plugins/enterprise_search/cypress.sh:19
x-pack/solutions/search/plugins/enterprise_search/cypress.sh:8
x-pack/solutions/search/plugins/enterprise_search/cypress/tsconfig.json:2
x-pack/solutions/search/plugins/enterprise_search/cypress/tsconfig.type_check.json:2
x-pack/solutions/search/plugins/enterprise_search/cypress/tsconfig.type_check.json:22
x-pack/solutions/search/plugins/enterprise_search/jest.config.dev.js:10
x-pack/solutions/search/plugins/enterprise_search/public/applications/ai_search/jest.config.js:10
x-pack/solutions/search/plugins/enterprise_search/public/applications/analytics/jest.config.js:10
x-pack/solutions/search/plugins/enterprise_search/public/applications/app_search/jest.config.js:10
x-pack/solutions/search/plugins/enterprise_search/public/applications/applications/jest.config.js:10
x-pack/solutions/search/plugins/enterprise_search/public/applications/elasticsearch/jest.config.js:10
x-pack/solutions/search/plugins/enterprise_search/public/applications/enterprise_search_content/jest.config.js:10
x-pack/solutions/search/plugins/enterprise_search/public/applications/enterprise_search_overview/jest.config.js:10
x-pack/solutions/search/plugins/enterprise_search/public/applications/search_experiences/jest.config.js:10
x-pack/solutions/search/plugins/enterprise_search/public/applications/semantic_search/jest.config.js:10
x-pack/solutions/search/plugins/enterprise_search/public/applications/shared/cypress/tsconfig.json:2
x-pack/solutions/search/plugins/enterprise_search/public/applications/shared/cypress/tsconfig.type_check.json:2
x-pack/solutions/search/plugins/enterprise_search/public/applications/shared/cypress/tsconfig.type_check.json:21
x-pack/solutions/search/plugins/enterprise_search/public/applications/shared/jest.config.js:10
x-pack/solutions/search/plugins/enterprise_search/public/applications/vector_search/jest.config.js:10
x-pack/solutions/search/plugins/enterprise_search/public/applications/workplace_search/jest.config.js:10
x-pack/solutions/search/plugins/enterprise_search/public/jest.config.js:10
x-pack/solutions/search/plugins/enterprise_search/server/jest.config.js:10
x-pack/solutions/search/plugins/enterprise_search/tsconfig.json:2
x-pack/solutions/search/plugins/enterprise_search/tsconfig.type_check.json:100
x-pack/solutions/search/plugins/enterprise_search/tsconfig.type_check.json:103
x-pack/solutions/search/plugins/enterprise_search/tsconfig.type_check.json:106
x-pack/solutions/search/plugins/enterprise_search/tsconfig.type_check.json:109
x-pack/solutions/search/plugins/enterprise_search/tsconfig.type_check.json:112
x-pack/solutions/search/plugins/enterprise_search/tsconfig.type_check.json:115
x-pack/solutions/search/plugins/enterprise_search/tsconfig.type_check.json:118
x-pack/solutions/search/plugins/enterprise_search/tsconfig.type_check.json:121
x-pack/solutions/search/plugins/enterprise_search/tsconfig.type_check.json:124
x-pack/solutions/search/plugins/enterprise_search/tsconfig.type_check.json:127
x-pack/solutions/search/plugins/enterprise_search/tsconfig.type_check.json:130
x-pack/solutions/search/plugins/enterprise_search/tsconfig.type_check.json:133
x-pack/solutions/search/plugins/enterprise_search/tsconfig.type_check.json:136
x-pack/solutions/search/plugins/enterprise_search/tsconfig.type_check.json:139
x-pack/solutions/search/plugins/enterprise_search/tsconfig.type_check.json:142
x-pack/solutions/search/plugins/enterprise_search/tsconfig.type_check.json:148
x-pack/solutions/search/plugins/enterprise_search/tsconfig.type_check.json:151
x-pack/solutions/search/plugins/enterprise_search/tsconfig.type_check.json:154
x-pack/solutions/search/plugins/enterprise_search/tsconfig.type_check.json:157
x-pack/solutions/search/plugins/enterprise_search/tsconfig.type_check.json:163
x-pack/solutions/search/plugins/enterprise_search/tsconfig.type_check.json:166
x-pack/solutions/search/plugins/enterprise_search/tsconfig.type_check.json:169
x-pack/solutions/search/plugins/enterprise_search/tsconfig.type_check.json:172
x-pack/solutions/search/plugins/enterprise_search/tsconfig.type_check.json:175
x-pack/solutions/search/plugins/enterprise_search/tsconfig.type_check.json:178
x-pack/solutions/search/plugins/enterprise_search/tsconfig.type_check.json:181
x-pack/solutions/search/plugins/enterprise_search/tsconfig.type_check.json:19
x-pack/solutions/search/plugins/enterprise_search/tsconfig.type_check.json:193
x-pack/solutions/search/plugins/enterprise_search/tsconfig.type_check.json:196
x-pack/solutions/search/plugins/enterprise_search/tsconfig.type_check.json:199
x-pack/solutions/search/plugins/enterprise_search/tsconfig.type_check.json:2
x-pack/solutions/search/plugins/enterprise_search/tsconfig.type_check.json:202
x-pack/solutions/search/plugins/enterprise_search/tsconfig.type_check.json:205
x-pack/solutions/search/plugins/enterprise_search/tsconfig.type_check.json:208
x-pack/solutions/search/plugins/enterprise_search/tsconfig.type_check.json:211
x-pack/solutions/search/plugins/enterprise_search/tsconfig.type_check.json:214
x-pack/solutions/search/plugins/enterprise_search/tsconfig.type_check.json:217
x-pack/solutions/search/plugins/enterprise_search/tsconfig.type_check.json:22
x-pack/solutions/search/plugins/enterprise_search/tsconfig.type_check.json:220
x-pack/solutions/search/plugins/enterprise_search/tsconfig.type_check.json:223
x-pack/solutions/search/plugins/enterprise_search/tsconfig.type_check.json:226
x-pack/solutions/search/plugins/enterprise_search/tsconfig.type_check.json:229
x-pack/solutions/search/plugins/enterprise_search/tsconfig.type_check.json:25
x-pack/solutions/search/plugins/enterprise_search/tsconfig.type_check.json:28
x-pack/solutions/search/plugins/enterprise_search/tsconfig.type_check.json:31
x-pack/solutions/search/plugins/enterprise_search/tsconfig.type_check.json:34
x-pack/solutions/search/plugins/enterprise_search/tsconfig.type_check.json:55
x-pack/solutions/search/plugins/enterprise_search/tsconfig.type_check.json:61
x-pack/solutions/search/plugins/enterprise_search/tsconfig.type_check.json:64
x-pack/solutions/search/plugins/enterprise_search/tsconfig.type_check.json:67
x-pack/solutions/search/plugins/enterprise_search/tsconfig.type_check.json:70
x-pack/solutions/search/plugins/enterprise_search/tsconfig.type_check.json:73
x-pack/solutions/search/plugins/enterprise_search/tsconfig.type_check.json:76
x-pack/solutions/search/plugins/enterprise_search/tsconfig.type_check.json:79
x-pack/solutions/search/plugins/enterprise_search/tsconfig.type_check.json:82
x-pack/solutions/search/plugins/enterprise_search/tsconfig.type_check.json:85
x-pack/solutions/search/plugins/enterprise_search/tsconfig.type_check.json:88
x-pack/solutions/search/plugins/enterprise_search/tsconfig.type_check.json:91
x-pack/solutions/search/plugins/enterprise_search/tsconfig.type_check.json:94
x-pack/solutions/search/plugins/enterprise_search/tsconfig.type_check.json:97
x-pack/solutions/search/plugins/search_assistant/tsconfig.json:12
x-pack/solutions/search/plugins/search_assistant/tsconfig.json:2
x-pack/solutions/search/plugins/search_assistant/tsconfig.type_check.json:14
x-pack/solutions/search/plugins/search_assistant/tsconfig.type_check.json:2
x-pack/solutions/search/plugins/search_assistant/tsconfig.type_check.json:21
x-pack/solutions/search/plugins/search_assistant/tsconfig.type_check.json:24
x-pack/solutions/search/plugins/search_assistant/tsconfig.type_check.json:27
x-pack/solutions/search/plugins/search_assistant/tsconfig.type_check.json:30
x-pack/solutions/search/plugins/search_assistant/tsconfig.type_check.json:36
x-pack/solutions/search/plugins/search_assistant/tsconfig.type_check.json:39
x-pack/solutions/search/plugins/search_assistant/tsconfig.type_check.json:42
x-pack/solutions/search/plugins/search_assistant/tsconfig.type_check.json:48
x-pack/solutions/search/plugins/search_assistant/tsconfig.type_check.json:51
x-pack/solutions/search/plugins/search_assistant/tsconfig.type_check.json:54
x-pack/solutions/search/plugins/search_assistant/tsconfig.type_check.json:57
x-pack/solutions/search/plugins/search_assistant/tsconfig.type_check.json:66
x-pack/solutions/search/plugins/search_connectors/jest.config.js:10
x-pack/solutions/search/plugins/search_connectors/package.json:8
x-pack/solutions/search/plugins/search_connectors/package.json:9
x-pack/solutions/search/plugins/search_connectors/tsconfig.json:12
x-pack/solutions/search/plugins/search_connectors/tsconfig.json:2
x-pack/solutions/search/plugins/search_connectors/tsconfig.type_check.json:14
x-pack/solutions/search/plugins/search_connectors/tsconfig.type_check.json:2
x-pack/solutions/search/plugins/search_connectors/tsconfig.type_check.json:21
x-pack/solutions/search/plugins/search_connectors/tsconfig.type_check.json:24
x-pack/solutions/search/plugins/search_connectors/tsconfig.type_check.json:27
x-pack/solutions/search/plugins/search_connectors/tsconfig.type_check.json:30
x-pack/solutions/search/plugins/search_homepage/jest.config.js:10
x-pack/solutions/search/plugins/search_homepage/tsconfig.json:2
x-pack/solutions/search/plugins/search_homepage/tsconfig.type_check.json:19
x-pack/solutions/search/plugins/search_homepage/tsconfig.type_check.json:2
x-pack/solutions/search/plugins/search_homepage/tsconfig.type_check.json:22
x-pack/solutions/search/plugins/search_homepage/tsconfig.type_check.json:25
x-pack/solutions/search/plugins/search_homepage/tsconfig.type_check.json:28
x-pack/solutions/search/plugins/search_homepage/tsconfig.type_check.json:31
x-pack/solutions/search/plugins/search_homepage/tsconfig.type_check.json:34
x-pack/solutions/search/plugins/search_homepage/tsconfig.type_check.json:37
x-pack/solutions/search/plugins/search_homepage/tsconfig.type_check.json:40
x-pack/solutions/search/plugins/search_homepage/tsconfig.type_check.json:43
x-pack/solutions/search/plugins/search_homepage/tsconfig.type_check.json:46
x-pack/solutions/search/plugins/search_homepage/tsconfig.type_check.json:49
x-pack/solutions/search/plugins/search_homepage/tsconfig.type_check.json:52
x-pack/solutions/search/plugins/search_homepage/tsconfig.type_check.json:55
x-pack/solutions/search/plugins/search_homepage/tsconfig.type_check.json:58
x-pack/solutions/search/plugins/search_indices/jest.config.js:10
x-pack/solutions/search/plugins/search_indices/tsconfig.json:11
x-pack/solutions/search/plugins/search_indices/tsconfig.json:2
x-pack/solutions/search/plugins/search_indices/tsconfig.type_check.json:101
x-pack/solutions/search/plugins/search_indices/tsconfig.type_check.json:13
x-pack/solutions/search/plugins/search_indices/tsconfig.type_check.json:2
x-pack/solutions/search/plugins/search_indices/tsconfig.type_check.json:20
x-pack/solutions/search/plugins/search_indices/tsconfig.type_check.json:23
x-pack/solutions/search/plugins/search_indices/tsconfig.type_check.json:26
x-pack/solutions/search/plugins/search_indices/tsconfig.type_check.json:29
x-pack/solutions/search/plugins/search_indices/tsconfig.type_check.json:32
x-pack/solutions/search/plugins/search_indices/tsconfig.type_check.json:35
x-pack/solutions/search/plugins/search_indices/tsconfig.type_check.json:38
x-pack/solutions/search/plugins/search_indices/tsconfig.type_check.json:41
x-pack/solutions/search/plugins/search_indices/tsconfig.type_check.json:44
x-pack/solutions/search/plugins/search_indices/tsconfig.type_check.json:47
x-pack/solutions/search/plugins/search_indices/tsconfig.type_check.json:50
x-pack/solutions/search/plugins/search_indices/tsconfig.type_check.json:53
x-pack/solutions/search/plugins/search_indices/tsconfig.type_check.json:56
x-pack/solutions/search/plugins/search_indices/tsconfig.type_check.json:59
x-pack/solutions/search/plugins/search_indices/tsconfig.type_check.json:62
x-pack/solutions/search/plugins/search_indices/tsconfig.type_check.json:65
x-pack/solutions/search/plugins/search_indices/tsconfig.type_check.json:68
x-pack/solutions/search/plugins/search_indices/tsconfig.type_check.json:71
x-pack/solutions/search/plugins/search_indices/tsconfig.type_check.json:74
x-pack/solutions/search/plugins/search_indices/tsconfig.type_check.json:77
x-pack/solutions/search/plugins/search_indices/tsconfig.type_check.json:83
x-pack/solutions/search/plugins/search_indices/tsconfig.type_check.json:86
x-pack/solutions/search/plugins/search_indices/tsconfig.type_check.json:89
x-pack/solutions/search/plugins/search_indices/tsconfig.type_check.json:92
x-pack/solutions/search/plugins/search_indices/tsconfig.type_check.json:95
x-pack/solutions/search/plugins/search_indices/tsconfig.type_check.json:98
x-pack/solutions/search/plugins/search_inference_endpoints/jest.config.js:10
x-pack/solutions/search/plugins/search_inference_endpoints/tsconfig.json:2
x-pack/solutions/search/plugins/search_inference_endpoints/tsconfig.type_check.json:19
x-pack/solutions/search/plugins/search_inference_endpoints/tsconfig.type_check.json:2
x-pack/solutions/search/plugins/search_inference_endpoints/tsconfig.type_check.json:22
x-pack/solutions/search/plugins/search_inference_endpoints/tsconfig.type_check.json:25
x-pack/solutions/search/plugins/search_inference_endpoints/tsconfig.type_check.json:28
x-pack/solutions/search/plugins/search_inference_endpoints/tsconfig.type_check.json:31
x-pack/solutions/search/plugins/search_inference_endpoints/tsconfig.type_check.json:34
x-pack/solutions/search/plugins/search_inference_endpoints/tsconfig.type_check.json:40
x-pack/solutions/search/plugins/search_inference_endpoints/tsconfig.type_check.json:43
x-pack/solutions/search/plugins/search_inference_endpoints/tsconfig.type_check.json:46
x-pack/solutions/search/plugins/search_inference_endpoints/tsconfig.type_check.json:49
x-pack/solutions/search/plugins/search_inference_endpoints/tsconfig.type_check.json:55
x-pack/solutions/search/plugins/search_inference_endpoints/tsconfig.type_check.json:58
x-pack/solutions/search/plugins/search_inference_endpoints/tsconfig.type_check.json:61
x-pack/solutions/search/plugins/search_inference_endpoints/tsconfig.type_check.json:64
x-pack/solutions/search/plugins/search_inference_endpoints/tsconfig.type_check.json:67
x-pack/solutions/search/plugins/search_inference_endpoints/tsconfig.type_check.json:70
x-pack/solutions/search/plugins/search_inference_endpoints/tsconfig.type_check.json:73
x-pack/solutions/search/plugins/search_inference_endpoints/tsconfig.type_check.json:76
x-pack/solutions/search/plugins/search_inference_endpoints/tsconfig.type_check.json:82
x-pack/solutions/search/plugins/search_inference_endpoints/tsconfig.type_check.json:85
x-pack/solutions/search/plugins/search_inference_endpoints/tsconfig.type_check.json:88
x-pack/solutions/search/plugins/search_notebooks/jest.config.js:10
x-pack/solutions/search/plugins/search_notebooks/package.json:8
x-pack/solutions/search/plugins/search_notebooks/package.json:9
x-pack/solutions/search/plugins/search_notebooks/tsconfig.json:12
x-pack/solutions/search/plugins/search_notebooks/tsconfig.json:2
x-pack/solutions/search/plugins/search_notebooks/tsconfig.type_check.json:14
x-pack/solutions/search/plugins/search_notebooks/tsconfig.type_check.json:2
x-pack/solutions/search/plugins/search_notebooks/tsconfig.type_check.json:21
x-pack/solutions/search/plugins/search_notebooks/tsconfig.type_check.json:24
x-pack/solutions/search/plugins/search_notebooks/tsconfig.type_check.json:27
x-pack/solutions/search/plugins/search_notebooks/tsconfig.type_check.json:30
x-pack/solutions/search/plugins/search_notebooks/tsconfig.type_check.json:33
x-pack/solutions/search/plugins/search_notebooks/tsconfig.type_check.json:36
x-pack/solutions/search/plugins/search_notebooks/tsconfig.type_check.json:39
x-pack/solutions/search/plugins/search_notebooks/tsconfig.type_check.json:42
x-pack/solutions/search/plugins/search_notebooks/tsconfig.type_check.json:45
x-pack/solutions/search/plugins/search_notebooks/tsconfig.type_check.json:48
x-pack/solutions/search/plugins/search_notebooks/tsconfig.type_check.json:51
x-pack/solutions/search/plugins/search_notebooks/tsconfig.type_check.json:54
x-pack/solutions/search/plugins/search_notebooks/tsconfig.type_check.json:57
x-pack/solutions/search/plugins/search_playground/jest.config.js:10
x-pack/solutions/search/plugins/search_playground/tsconfig.json:2
x-pack/solutions/search/plugins/search_playground/tsconfig.type_check.json:100
x-pack/solutions/search/plugins/search_playground/tsconfig.type_check.json:103
x-pack/solutions/search/plugins/search_playground/tsconfig.type_check.json:106
x-pack/solutions/search/plugins/search_playground/tsconfig.type_check.json:109
x-pack/solutions/search/plugins/search_playground/tsconfig.type_check.json:112
x-pack/solutions/search/plugins/search_playground/tsconfig.type_check.json:115
x-pack/solutions/search/plugins/search_playground/tsconfig.type_check.json:118
x-pack/solutions/search/plugins/search_playground/tsconfig.type_check.json:121
x-pack/solutions/search/plugins/search_playground/tsconfig.type_check.json:124
x-pack/solutions/search/plugins/search_playground/tsconfig.type_check.json:19
x-pack/solutions/search/plugins/search_playground/tsconfig.type_check.json:2
x-pack/solutions/search/plugins/search_playground/tsconfig.type_check.json:22
x-pack/solutions/search/plugins/search_playground/tsconfig.type_check.json:25
x-pack/solutions/search/plugins/search_playground/tsconfig.type_check.json:28
x-pack/solutions/search/plugins/search_playground/tsconfig.type_check.json:31
x-pack/solutions/search/plugins/search_playground/tsconfig.type_check.json:34
x-pack/solutions/search/plugins/search_playground/tsconfig.type_check.json:37
x-pack/solutions/search/plugins/search_playground/tsconfig.type_check.json:43
x-pack/solutions/search/plugins/search_playground/tsconfig.type_check.json:46
x-pack/solutions/search/plugins/search_playground/tsconfig.type_check.json:49
x-pack/solutions/search/plugins/search_playground/tsconfig.type_check.json:52
x-pack/solutions/search/plugins/search_playground/tsconfig.type_check.json:55
x-pack/solutions/search/plugins/search_playground/tsconfig.type_check.json:58
x-pack/solutions/search/plugins/search_playground/tsconfig.type_check.json:67
x-pack/solutions/search/plugins/search_playground/tsconfig.type_check.json:70
x-pack/solutions/search/plugins/search_playground/tsconfig.type_check.json:82
x-pack/solutions/search/plugins/search_playground/tsconfig.type_check.json:85
x-pack/solutions/search/plugins/search_playground/tsconfig.type_check.json:88
x-pack/solutions/search/plugins/search_playground/tsconfig.type_check.json:91
x-pack/solutions/search/plugins/search_playground/tsconfig.type_check.json:94
x-pack/solutions/search/plugins/search_playground/tsconfig.type_check.json:97
x-pack/solutions/search/plugins/search_solution/search_navigation/jest.config.js:10
x-pack/solutions/search/plugins/search_solution/search_navigation/tsconfig.json:2
x-pack/solutions/search/plugins/serverless_search/jest.config.js:10
x-pack/solutions/search/plugins/serverless_search/package.json:8
x-pack/solutions/search/plugins/serverless_search/package.json:9
x-pack/solutions/search/plugins/serverless_search/tsconfig.json:12
x-pack/solutions/search/plugins/serverless_search/tsconfig.json:2
x-pack/solutions/search/plugins/serverless_search/tsconfig.type_check.json:102
x-pack/solutions/search/plugins/serverless_search/tsconfig.type_check.json:105
x-pack/solutions/search/plugins/serverless_search/tsconfig.type_check.json:111
x-pack/solutions/search/plugins/serverless_search/tsconfig.type_check.json:114
x-pack/solutions/search/plugins/serverless_search/tsconfig.type_check.json:120
x-pack/solutions/search/plugins/serverless_search/tsconfig.type_check.json:126
x-pack/solutions/search/plugins/serverless_search/tsconfig.type_check.json:132
x-pack/solutions/search/plugins/serverless_search/tsconfig.type_check.json:135
x-pack/solutions/search/plugins/serverless_search/tsconfig.type_check.json:138
x-pack/solutions/search/plugins/serverless_search/tsconfig.type_check.json:14
x-pack/solutions/search/plugins/serverless_search/tsconfig.type_check.json:2
x-pack/solutions/search/plugins/serverless_search/tsconfig.type_check.json:21
x-pack/solutions/search/plugins/serverless_search/tsconfig.type_check.json:24
x-pack/solutions/search/plugins/serverless_search/tsconfig.type_check.json:27
x-pack/solutions/search/plugins/serverless_search/tsconfig.type_check.json:30
x-pack/solutions/search/plugins/serverless_search/tsconfig.type_check.json:33
x-pack/solutions/search/plugins/serverless_search/tsconfig.type_check.json:36
x-pack/solutions/search/plugins/serverless_search/tsconfig.type_check.json:39
x-pack/solutions/search/plugins/serverless_search/tsconfig.type_check.json:51
x-pack/solutions/search/plugins/serverless_search/tsconfig.type_check.json:54
x-pack/solutions/search/plugins/serverless_search/tsconfig.type_check.json:57
x-pack/solutions/search/plugins/serverless_search/tsconfig.type_check.json:60
x-pack/solutions/search/plugins/serverless_search/tsconfig.type_check.json:63
x-pack/solutions/search/plugins/serverless_search/tsconfig.type_check.json:66
x-pack/solutions/search/plugins/serverless_search/tsconfig.type_check.json:69
x-pack/solutions/search/plugins/serverless_search/tsconfig.type_check.json:72
x-pack/solutions/search/plugins/serverless_search/tsconfig.type_check.json:75
x-pack/solutions/search/plugins/serverless_search/tsconfig.type_check.json:78
x-pack/solutions/search/plugins/serverless_search/tsconfig.type_check.json:81
x-pack/solutions/search/plugins/serverless_search/tsconfig.type_check.json:84
x-pack/solutions/search/plugins/serverless_search/tsconfig.type_check.json:90
x-pack/solutions/search/plugins/serverless_search/tsconfig.type_check.json:93
x-pack/solutions/search/plugins/serverless_search/tsconfig.type_check.json:96
x-pack/solutions/search/plugins/serverless_search/tsconfig.type_check.json:99
```
</details>
---------
Co-authored-by: pgayvallet <pierre.gayvallet@elastic.co>
Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
2024-12-27 10:55:21 -06:00
Samiul Monir
bc466ea738
[Search] Add Inference endpoint Flyout in Inference Management UI ( #203204 )
...
## Summary
This PR includes
- Create a UI component package to share AI connector form between
multiple plugins
- Integrate the packaged components into the `Search Inference Endpoint`
plugin.
https://github.com/user-attachments/assets/2b447b44-3d1d-4422-b76d-8d8fd160b2bc
### Checklist
Check the PR satisfies following conditions.
Reviewers should verify this PR satisfies this list as well.
- [X] Any text added follows [EUI's writing
guidelines](https://elastic.github.io/eui/#/guidelines/writing ), uses
sentence case text and includes [i18n
support](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md )
- [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
- [X] [Flaky Test
Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1 ) was
used on any tests changed
---------
Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
2024-12-24 22:23:25 -05:00
Tiago Costa
34bc507dc3
skip flaky suite ( #204507 )
2024-12-23 16:49:51 +00:00
Luke Gmys
3083706bc9
[Security Solution] [Cases] Introduce case observables (phase 0 & 1) ( #190237 )
...
## Summary
### Introducting Case Observables - _phases 0 and 1_
This pull request introduces case observables to Kibana, enhancing the
platform's case management capabilities. It adds support for capturing
and displaying observables (e.g., IP addresses, URLs, file hashes)
linked to cases. The feature integrates with the Cases UI, allowing
users to easily associate observables with cases for better tracking and
analysis in incident response workflows. This improves investigative
efficiency by correlating observables across multiple cases.
#### Requirements:
https://docs.google.com/document/d/12hZTpyn0eXy3Xnq8qLBd6_sJxBhNZoI7vXztxWHhUds/edit#heading=h.srf6mb8ifiad
#### Design document:
https://docs.google.com/document/d/1MeDLl6OEWast1RC1M3_hQXnRCd8frrXdGkFnypIYKJQ/edit#heading=h.kb5lrp2j62id
Notable Cases sections are added in this pr:
**1. Observables section in the case view, allowing for adding and
listing up to 10 observables for the case**

**2. Similar cases view for every case, allowing for similar case
discovery**

**3. Observable types management view in Cases settings**

Original issue:
https://github.com/elastic/kibana/issues/180360
Things skipped for now from MVP:
- [ ] Allow users to manually create observables from the cases alerts
table using the table actions (Phase 1)
- [ ] Allow users to manually create observables of type “hash” from the
files table using the table actions (Phase 1)
---------
Co-authored-by: Christos Nasikas <xristosnasikas@gmail.com>
Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
Co-authored-by: Christos Nasikas <christos.nasikas@elastic.co>
2024-12-23 14:25:58 +01:00
Robert Jaszczurek
0cc887be92
[ML][UX]: Consistent Layout and UI Enhancements for ML Pages ( #203813 )
...
## Summary
* Updated alignment for `Add to` action buttons across various ML pages
- see: #184109
* Fixed the overflowing date picker on `Anomaly Detection` pages - see:
[#204394 ](https://github.com/elastic/kibana/issues/204394 )
* Standardized gaps around items on pages to maintain consistent values
of `8px` (`gutterSize = 's'`)
* Fixed the header on the Data Visualizer page - see:
[#204393 ](https://github.com/elastic/kibana/issues/204393 )
* Adjusted the layout for Change Point Detection
* Updated toast messages & toast action button - see: #184109
* Added icons for attachments actions
Exploration around new `Add to` actions buttons - the right column is
the most recent one, see: #184109 :
| Before | After (add_to button) | After (icon button) - current |
| ------------- | ------------- | ------------- |
| 
| 
| 
|
| 
| 
| 
|
| 
| 
|

|
| 
| 
| 
|
| 
| 
|

|
Toasts:
| Before | After |
| ------ | ------ |
| <img width="376" alt="image"
src="https://github.com/user-attachments/assets/c58000c2-30d4-4312-be53-0e3e9a6e3ae6 "
/> |

|
Other changes:
| Before | After |
| ------ | ------ |
| 
| 
|
| 
| 
|
| 
| 
|
| 
| 
|
| 
| 
|
| 
| 
|
| <img width="342" alt="image"
src="https://github.com/user-attachments/assets/6529eebe-510e-4688-81e6-4cf3e880c610 "
/> | <img width="323" alt="image"
src="https://github.com/user-attachments/assets/6dada83e-252f-45d5-95d2-a03fa856d70a "
/> |
- [ ] Any text added follows [EUI's writing
guidelines](https://elastic.github.io/eui/#/guidelines/writing ), uses
sentence case text and includes [i18n
support](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md )
---------
Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
2024-12-23 11:56:12 +01:00
Elena Stoeva
f72b63f3b7
[Index Management] Add bulk edit data retention ( #203083 )
...
Closes https://github.com/elastic/kibana/issues/165142
## Summary
This PR adds bulk edit data retention to Data streams table.
On all offerings apart from serverless security project:
https://github.com/user-attachments/assets/aa091fc1-5029-4542-b76b-8045c65dda27
On serverless security project:
https://github.com/user-attachments/assets/cbccc8bd-d3f1-4511-8134-bfb0a9e8587f
### How to test:
Testing in serverless security project:
1. Start ES with `yarn es serverless --projectType security -E
data_streams.lifecycle.retention.max=200d` and Kibana with `yarn
serverless-security`
2. Navigate to console and create a few data streams following [these
instructions](https://www.elastic.co/guide/en/elasticsearch/reference/current/set-up-a-data-stream.html#create-component-templates )
3. Navigate to Index Management -> Data streams
4. Select multiple data streams and click on bulk edit data retention
button
5. Verify that:
- The help text displays the set max data retention with a link to
cloud.
- The form doesn't allow setting a data retention higher than the max
data retention.
- If any of the data streams has a reduced data retention period, an
error banner is shown, displaying the affected data streams.
Testing in stateful and searc/oblt serverless project:
1. Start ES with `yarn es serverless` and Kibana with `yarn
serverless-security`
2. Navigate to console and create a few data streams following [this
instructions](https://www.elastic.co/guide/en/elasticsearch/reference/current/set-up-a-data-stream.html#create-component-templates )
3. Navigate to Index Management -> Data streams
4. Select multiple data streams and click on bulk edit data retention
button
5. Verify that:
- There is no help text displaying the max data retention and no
validation for the data retention period.
- If any of the data streams has a reduced data retention period, an
error banner is shown, displaying the affected data streams.
Configure cloud locally by adding the following to
`config/kibana.dev.yml` and restarting Kibana:
```
xpack.cloud.id: 'test'
xpack.cloud.base_url: "https://cloud.elastic.co "
xpack.cloud.deployment_url: "/deployments/deploymentId"
```
### Checklist
- [x] Any text added follows [EUI's writing
guidelines](https://elastic.github.io/eui/#/guidelines/writing ), uses
sentence case text and includes [i18n
support](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md )
- [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
- [x] [Flaky Test
Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1 ) was
used on any tests changed -
https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7619
---------
Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
2024-12-19 15:11:52 +02:00
Sébastien Loix
6f28942e1e
[Serverless] Remove "userAndRoles" from es and security nav tree ( #204740 )
2024-12-19 12:52:35 +00:00