mirror of
https://github.com/elastic/kibana.git
synced 2025-06-27 18:51:07 -04:00
575e80bccc
## Summary
This PR implements the frontend for opening a Saved Playground. As a
part of that there are several refactors to the current playground that
warrant regression testing.
### Testing
To test the saved playground view the search mode feature flag should be
enabled, either with a config override or via console:
```
POST kbn:/internal/kibana/settings/searchPlayground:searchModeEnabled
{"value": true}
```
Then you will need to manually save a playground:
```
curl -X "PUT" "http://localhost:5601/internal/search_playground/playgrounds" \
-H 'elastic-api-version: 1' \
-H 'kbn-xsrf: dev' \
-H 'x-elastic-internal-origin: Kibana' \
-H 'Content-Type: application/json; charset=utf-8' \
-u 'elastic_serverless:<PASSWORD>' \
-d $'{
"elasticsearchQueryJSON": "{\\"retriever\\":{\\"standard\\":{\\"query\\":{\\"semantic\\":{\\"field\\":\\"text\\",\\"query\\":\\"{query}\\"}}}},\\"highlight\\":{\\"fields\\":{\\"text\\":{\\"type\\":\\"semantic\\",\\"number_of_fragments\\":2,\\"order\\":\\"score\\"}}}}",
"indices": [
"search-test"
],
"name": "Test playground",
"queryFields": {
"search-test": [
"text"
]
}
}'
```
*Note this creates a saved playground in the Default space, and
playgrounds are space aware so it will only be available in the default
space. If you want to create a playground in another space you will need
to update this URL to include the space.
This assumes you have a `search-test` index created using the
semantic_text onboarding workflow mapping.
Then you can open the saved playground page at:
`/app/search_playground/p/<ID_RETURNED_FROM_CURL>`
## Screenshots
Chat
Chat - Query
Search - Query
### 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/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
- [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
- [ ] 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: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
|
||
|---|---|---|
| .. | ||
| hooks | ||
| pipeline-resource-definitions | ||
| pipeline-utils | ||
| pipelines | ||
| scripts | ||
| .mocharc.json | ||
| .npmrc | ||
| disabled_jest_configs.json | ||
| ftr_base_serverless_configs.yml | ||
| ftr_chat_serverless_configs.yml | ||
| ftr_configs_manifests.json | ||
| ftr_oblt_serverless_configs.yml | ||
| ftr_oblt_stateful_configs.yml | ||
| ftr_platform_stateful_configs.yml | ||
| ftr_search_serverless_configs.yml | ||
| ftr_search_stateful_configs.yml | ||
| ftr_security_serverless_configs.yml | ||
| ftr_security_stateful_configs.yml | ||
| package-lock.json | ||
| package.json | ||
| pull_requests.json | ||
| README.md | ||
| scout_ci_config.yml | ||
| tsconfig.json | ||
| tsconfig.test.json | ||
Kibana / Buildkite
Directory Structure
hooks- special directory used by Buildkite agents for hookspipeline-utils- Shared TypeScript utils for use in pipeline scriptspipelines- contains pipeline definitionsscripts/common- scripts that getsourced by other scripts to set environment variables or import shared functionsscripts/lifecycle- general scripts for tasks that run before or after individual steps or the entire buildscripts/steps- scripts that define something that will run for a step defined in a pipelinescripts/*- all other scripts are building blocks that make up the tasks in pipelines. They may be run by other scripts, but should not besourced