This PR adds documentation about the new log column feature. To keep the docs Logs UI readable as new features are added, they are now restructured into four pages:
* a landing page with a full screenshot linking to the subsequent section
* a "getting started" page to link to the tutorials on ingesting log data
* a "using" page to explain the main features of the Logs UI
* a "configuring" page to explain the configuration UI
closeselastic/kibana#36025
* Allow passing in a signal to abort an Elasticsearch request using the cluster client
* Go back to using promises (which still return abort method) and update test
* Update docs
* Explicitly return Promise<any> instead of {}
* Kibana request keep a reference to raw request. used to bind hapi-cookie
* CookieSessionStorage should work with KibanaRequest
as soon as registerAuth refactored to restrict access to hapi Request, CookieSessionStorage won't work with hapi request directly
* change registerAuth public api
* adopt auth lifecycle tests
* move lifecycle auth tests from integration to unit and adopt to new api.
* mark toRawRequest as internal to prevent exposure
* generate docs
* reword test cases
* mark Request internals in tsdoc
* Adding read-only mode section to Discover
* No more "mode" or "badge" terminology
* Putting newline back
* Adding "Saving" section for visualize
* Adding dashboard read only access section
* Timelion gets read-only documentation
* Adding read only access section to index patterns and advanced settings
* Adding graph read only access section
* expose route info in KibanaRequest
* update mocks in test
* make tags readonly, getRouteInfo is private method
* add mocks for hapi internals
* mode deepFreeze to core utils level as it env agnostic
* freeze route props
* fix typo
* add tests for route options
* fix integration tests. deep_freeze was moved under core utils
* add comments, expose public types and regenerate docs
* address comment. remove unnecessary async in route handlers
* make routeSchema optional instead of union with undefined
* @skaapgif improvements
* update docs
* Allow interception of http requests from browser http service
* Update documentation and browser http types
* Remove async marker from fetch function
* Fix failing tests
* Attempting to fix kuery_autocomplete test
* Allow halting of http fetches from interception
* Re-use HttpInterceptHaltError
* Expose HttpInterceptor types and update docs
* Only mock calls to capabilities during browser testing
* Documenting missing cluster alerts.
Currently, the Cluster Alerts docs only list four cluster alerts. There are, in fact, six cluster alerts in all. This adds the remaining two.
* [DOCS] Fixes formatting
* introduce pre-,post-auth stages
* cleanup integration_tests. now contracts available in tests
* auth per route is configurable
* Unify lifecycle results structure
* expose api to store auth state and status via http service
* update tests
* update docs
* use full name, auth should not mutate request
* move basePath functionality under namespace
* regenerate docs
* Revert "move basePath functionality under namespace"
This reverts commit 9599d32801.
* Revert "regenerate docs"
This reverts commit 1799d3b088.
* regenerate docs
* updated yarn.lock no idea why
* extract AuthStateStorage to a separate entity
* get rid of nested ifs
* describe what is the difference between hooks
* re-wording
* Adding a read only access section to the infrastructure docs
* Adjusting where the infrastructure read only access section is and
adding the logs readonly access section
* Fixing grammar
* Remove browser basePath service, move functionality into browser http service
* Update generated documentation for removal of browser basePath
* Fix type interface for removal of basePath
* Split IHttpService into separate setup and start interfaces
* Rename appendToBasePath to prependBasePath, rename removeFromBasePath to removeBasePath
* Adjusting production setup instructions as a result of Spaces/RBAC
* Update docs/setup/production.asciidoc
Co-Authored-By: Larry Gregory <lgregorydev@gmail.com>
* remove LoggingConfig class
* get rid of ElasticsearchConfig class
* get rid of PluginsConfig class
* get rid of HttpConfig Class
* update ConfigService
* update LegacyService
* update testbed plugin
* update docs
* [Maps] Getting started docs - Adding the map to a dashboard
* clean up instructions
* Update docs/maps/maps-getting-started.asciidoc
Co-Authored-By: nreese <reese.nathan@gmail.com>
* Update docs/maps/maps-getting-started.asciidoc
Co-Authored-By: nreese <reese.nathan@gmail.com>
* Update docs/maps/maps-getting-started.asciidoc
Co-Authored-By: nreese <reese.nathan@gmail.com>
* Update docs/maps/maps-getting-started.asciidoc
Co-Authored-By: nreese <reese.nathan@gmail.com>
* Update docs/maps/maps-getting-started.asciidoc
Co-Authored-By: nreese <reese.nathan@gmail.com>
* Update docs/maps/maps-getting-started.asciidoc
Co-Authored-By: nreese <reese.nathan@gmail.com>
* Update docs/maps/maps-getting-started.asciidoc
Co-Authored-By: nreese <reese.nathan@gmail.com>
* Update docs/maps/maps-getting-started.asciidoc
Co-Authored-By: nreese <reese.nathan@gmail.com>
* combine Filtering sections into single section as suggested
* fix zoom instructions and clean up save map section
* add more wording about why the tutorial is adding a terms join
* talk about static and data-driving styling in Set the vector style section
* more review comments
* add screen shot of document layer
* Update docs/maps/maps-getting-started.asciidoc
Co-Authored-By: gchaps <33642766+gchaps@users.noreply.github.com>
* avoid using lets since there is no we
This moves the core Nav APIs from `ui/chrome` into the `ChromeService` in the new platform.
- `ChromeStart` now exposes a sub-service for reading and making limited updates to navlinks. These are powered by apps registered with the `ApplicationService` and filtered by UI Capabilities before being exposed by the `ChromeService`.
- The `header-global-nav` directive now consumes navlinks from the new platform.
- The `lastSubUrl` feature utilized by legacy apps has been refactored and will remain in `ui/chrome`. This feature utilizes the limited fields that `ChromeService` exposes to updates by outside code.
This change is the main blocker to moving the Chrome UI to the new platform. This will be necessary to enable the new platform to control top-level routing.
* Introduce new convention for config definition.
We need to define a way to acquire configuration schema as a part of
plugin definition. Having schema we can split steps of
config validation and plugin instantiation.
* Discover plugins, read their schema and validate the config.
Config validation finished before core services and plugins read from it.
That allows us to fail fast and have predictable validation results.
* Instantiate plugins using DiscoveredPluginsDefinitions.
* Update tests for new API.
* test server is not created if config validation fails
* move plugin discovery to plugin service pre-setup stage.
Set validation schemes in ConfigService.preSetup stage.
* fix eslint problem
* generate docs
* address Rudolfs comments
* separate core services and plugins validation
* rename files for consistency
* address comments for root.js
* address comments #1
* useSchema everywhere for consistency. get rid of validateAll
* plugin system runs plugin config validation
* rename configDefinition
* move plugin schema registration in plugins plugins service
plugins system is not setup when kibana is run in optimizer mode,
so config keys aren't marked as applied.
* cleanup
* update docs
* address comments
