* Add opton to run chrome headless. Mainly for windows tests which can't use xvfb.
* Update from review comments
Make environment variable Boolean, remove single quotes from keys, remove window size.
* Revert "[DOCS]: Release notes, release highlights, and breaking changes for 6.4 (#22015)"
This reverts commit 0c820163f0.
* Revert "fixing issue with importing vis with missing saved search (#22029) (#22076)"
This reverts commit 4401b02365.
In #19916 we inadvertently began directly returning the data from the Keystore when the Kibana server expects a structured object.
Signed-off-by: Tyler Smalley <tyler.smalley@elastic.co>
* Beginning to work on the role management APIs. Added docs for GET
* Adding PUT docs
* Adding PUT details
* Adding delete docs
* Fixing linking
* Adding Kibana privileges section
* Fixing dashboard only mode docs
* Fixing a few more references to managing roles
* Beginning to work on authorization docs, might be moving some to
stack-docs
* Collapsing authorization description in the kibana privileges page
* Adding audit logging section
* Revising the language on the Kibana role management section
* Splitting back out the auth/privileges and adding legacy fallback
details
* Revising language around impact of disabling security
* Changing Kibana to {kib} and Elasticsearch to {es}
* Beginning to work on developer centric docs
* Fixing some formatting, adding some diagrams
* Adding note about the role management APIs
* Adding overview, fixing small syntax issues
* Fixing chunk name for transitioning to application privileges
* Adjusting tone for the authorization introduction
* Changing the tone and structure of the RBAC docs
* Deleting blog stuff after refactoring
* Addressing first round of peer review comments
* Fixing endpoints links
* Peer review suggested edits
* Addressing other PR feedback
This fixes bucket span estimation for the machine learning admin user when security is enabled. The original issue was that the machine learning admin by default doesn't have the necessary permissions to call cluster.getSettings to get the settings search.max_buckets. This is now fixed by using callWithInternalUser() and additional permissions checks.
* add polyfill for ChildNode remove
* call polyfill function
* add files as suggested by jbudz
* remove checks around polyfill
* just use polyfill that mozilla recommends
* add MIT license to file
* suffix file with polyfill, update copyright and link to repo
* update notice.txt
* Fix available fields option toggle (#21730)
a36b87a#diff-aff92ff718af4b68d02f030d8a438754 added an ng-if around the available fields button element. ng-if creates a child scope. The ng-click on the button directly modifies scope state. As a result, when the ng-if was added, that ng-click began modifying the ng-if's child scope instead of the parent scope.
The best solution would be to update the discFieldChooser directive to use the controllerAs property so its scope variables are namespaced. However, this is a bit risky because I'd need to make sure to update every single scope variable reference in the template, and it's a relatively large template. Since we'd like to backport this to 6.4 I've taken the less risky route of adding $parent to the scope reference inside the ng-if block.
* forgot I needed this one too
- If search.max_buckets wasn't set in elasticsearch.yml and defaulted to -1, the bucket span estimator would not be able to run against a reasonable time range and would always return "Bucket span could not be estimated". This fix falls back to 10000 buckets in the case search.max_buckets is set to -1.
- The PR also introduces two tests to check for different values of search.max_buckets. The first test would fail without the fix introduced by this PR.
* Fix hidden ticks when using log scale (#21507)
* Add support for vertical axis
The vertical axis scale has an inverted range (max, min) and we need to compute the absolute scale width instead.
* Add functional test for Y axis scale type switching
* Remove unnecessary waitUntilLoadingHasFinished
* Skip scale tick tests because of possible flakyness (#21641)
