* fixing issues with index lifecycle summary
* correcting action / action time headers
* adding placeholder for optional replica fields and removing set to same link
* removing include/exclude from policy definitions
* changing wording to linked indices
* updating test snapshots
* changing index alias to index rollover alias
* changing minimum age select and label to make timing clearer
* adding description of valid policy name
* adding link to docs for timing
* adding defaults for hot and warm phase
* fixing tests and React warnings
* fixing spacing issues with min age component
* making actions button empty
* fixing invalid prop for empty button
* setting timzone to utc to fix snapshot tests
* copy edits
* addressing PR feedback
* [Test/Reporting] Enable "generates a report with/without data"
* navigate to discover before each csv test
* get another test working
* re-enable more tests
* refactor api usage tests
* catch error in createIndex to avoid race condition in test
* delete reports before
Login is no longer coupled directly to our basic auth provider, so
alternative auth providers can now be used with our standard login flow.
The LoginAttempt request service is the mechanism for auth providers to
integrate with the login flow.
We're using the successfully logged out page with the SAML provider
currently, so redirecting to the /login page is problematic since they
won't be able to login using this url. Instead, we're redirecting them
to '/' so that the auth providers can figure out what to do.
* Create calendar list in react
* wip: create new_calendar page
* Update new calendar settings directory name
* Edit button action + update utils
* Adds ability to create new calendar
* Display calendar data on edit
* rename directory to settings/calendar
* Add scss files to calendar dir
* Create new group from form
* Adds event table and partial event modal.
* adds datepicker to modal
* Time range event functionality
* add import event functionality
* upate new event modal design
* Add error handling to list/edit
* calendarId validity check
* Create/delete permission. List/form style tweak
* Update calendarList to match filterList
* Add missing newlines in scss files
* Initial tests for calendar list
* Update classnames to meet guidelines
* ImportedEvents component + create utils
* remove unnecessary import
* rename calendars dir
* include past evens in import if checkbox checked
* code review updates
* move components into own directories
* update index.scss with dir name change
* skip irrelevant tests
* fix unsaved event deletion. rename scss file.
* Add modal tests
* Show calendarId and description as header on edit
* update snapshot for refactor
* update classnames to BEM guidelines
* Update snapshot for classname change
* [APM] fixes#26525
- simplified the stackframe grouping algorithm
- add support for `stackframe.exclude_from_grouping`
- made the rendering more tolerant of edge cases
* Made improvements to code readability and added more meaningful test cases
Node 10 uses `null` to denote the non-existence of a querystring
parameter when `url.parse(urlString, true)` is used, the following
changes fix our usages within the security plugin.
* Feat: Workpad Templates (#23966)
* Added workpad manager which contains workpad_loader and workpad_templates
* Fixed term filter in workpad_templates
* design changes
* Removed console logs
Closes workpad manager modal after cloning template
Fixed filtering workpad templates
Removed console log
Added sample templates
Added more templates to test with
Removed cloneDeep
* case insensitive template search
* Case insensitive tag order in popover
* added descriptions and tags to sample data workpads
* refine list of initial templates
* remove sample data templates, make buttons bigger
* Added template and tag registries
* Fixed workpad loader resizing issue on home page
* Moved tags to ui folder
* Fixed template class
* Fixed properties in templates to match workpad
* fix lint errors (#26985)
* [BeatsCM] Cleanup and refactor (#26636)
* Refactor BeatsCM
* update deps
* update more deps
* update for new EUI definitions
* update import
* Revert "update deps"
This reverts commit 759a14561d.
* use _source_includes
* remove _source_includes
* work-around due to watcher UI tests
* Keep all xpack checks safe because we cant trust its there in tests for some reason
* VALIDATION. This commit is to ensure the errors in CI are coming from beats
* remove validation that this is a beats CM issue
* More try/catch to try and find where this error is
* testing another call
* revert back to dangerouslyGetActiveInjector
* ensure expire always is a number
* fix swallowed error
* Update x-pack/plugins/beats_management/public/lib/compose/kibana.ts
Co-Authored-By: mattapperson <me@mattapperson.com>
* Update x-pack/plugins/beats_management/public/utils/page_loader.test.ts
Co-Authored-By: mattapperson <me@mattapperson.com>
* Update x-pack/plugins/beats_management/public/utils/page_loader.ts
Co-Authored-By: mattapperson <me@mattapperson.com>
* fix for new webpack import
* Fix translation map
* fix URL path
* fix other link
* removing tag from beats via tag details screen now uses container
* remove debug text
* added comment/readme about routing on the client side
* enrolled beat UI now works on overview screen
* newly enrolled beat now reloads the beats table
* fix TS errors
# Conflicts:
# x-pack/plugins/beats_management/public/lib/adapters/elasticsearch/rest.ts
# x-pack/plugins/beats_management/server/lib/adapters/beats/elasticsearch_beats_adapter.ts
# x-pack/plugins/beats_management/server/lib/adapters/database/adapter_types.ts
* fix import for 6.x
* fix formatting
Closes https://github.com/elastic/kibana/issues/26405
Upgrades tinymath so that columns with dots now work correctly.
---
To test, follow the details in #26405.
1. Get some data that has fields with dots in them. Beats data would work, or you can create a test index with just 2 documents as follows:
```
POST test/test
{
"string":"abc",
"with.dot":"abc"
}
POST test/test
{
"string":"abcd",
"with.dot":"abcd"
}
```
2. Create a pie chart, splitting labels on one of the available fields.
Previously, given the POST info above, only `string` would work correctly. Now both (and both of their `.keyword` variants) work correctly.
