* [Discover] Hide "Add a field" button for read only access
* [Discover] Hide "Create a data view" button for read only access on desktop
* [Discover] Hide "Create a data view" and "Add a field" button for read only access on mobile
* [Discover] Make sure that error message is shown when access rights were reduced for a user in meantime
* [Discover] Make checks safe
* [Discover] Update tests
* [Discover] Streamline the logic
* [Discover] Update tests
* [Discover] Add tests
* [Discover] Add tests
* [Discover] Update code style
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
* docs(NA): windows wsl development
* docs(NA): update titles for the documentation created
* chore(NA): update dev_docs/tutorials/development_windows.mdx
Co-authored-by: Jonathan Budzenski <jon@budzenski.me>
* docs(NA): updated guide to include info around GUI apps support
* docs(NA): updated guide to include info around GUI apps support
* docs(NA): include win10 GUI workaround
* docs(NA): run a first sudo command before running others
* docs(NA): added remote code wsl extension
* docs(NA): mentioned NVIDIA does now includes vGPU drivers for WSL within the common drivers
* docs(NA): update sudo commands separation
* docs(NA): added hardware virtualization prerequisite awareness into the guide
* docs(NA): update wording on guide recomendation for win11
Co-authored-by: Jonathan Budzenski <jon@budzenski.me>
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
**Fixes:** https://github.com/elastic/kibana/issues/134639
## Summary
In Cloud, `Elastic APM` and `Fleet Server` integrations are installed by default. However, attempts to fetch their packages from Elastic Package Registry via Fleet services on the server-side fail with the following errors:
```json
{
"message": "apm@8.3.0 not found",
"status_code": 500
}
```
```json
{
"message": "fleet_server@1.2.0 not found",
"status_code": 500
}
```
<img width="797" alt="Screenshot 2022-06-20 at 11 28 18" src="https://user-images.githubusercontent.com/7359339/174571610-4c24e777-c49a-49e0-addf-54c6301cc8ca.png">
This behavior happens in some Cloud environments (like the one in the related ticket). It seems to not happen in Cloud CI environments and locally.
This PR adds error handling for this edge case to `GET /internal/detection_engine/fleet/integrations/installed?packages=` endpoint.
- It logs fetching errors to the console logs of Kibana.
- It uses a "best-effort" approach for returning data from the endpoint. If we could successfully read existing integration policies, we already have all of the needed data except correct integration titles. So, if after that any request to EPR results in an error, we:
- Still return 200 with a list of installed integrations
- Include correct titles for those packages that were successfully fetched
- Include "best guess" titles for those packages that failed
```
[2022-06-20T12:57:10.270+02:00][ERROR][plugins.securitySolution] Error fetching package info from registry for
fleet_server@1.2.0. Boom!
[2022-06-20T12:57:10.270+02:00][ERROR][plugins.securitySolution] Error fetching package info from registry for
apm@8.4.0. Boom!
```
<img width="1085" alt="Screenshot 2022-06-20 at 13 05 08" src="https://user-images.githubusercontent.com/7359339/174588468-d28c1383-3a25-4f16-8905-bad3ca73e63e.png">
### 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
* [Maps] fix array values out of order in tooltips
* [CI] Auto-commit changed files from 'node scripts/precommit_hook.js --ref HEAD~1..HEAD --fix'
Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
* New script endpoint_action_responder that will (currently) continuously pull for pending actions and respond to them (by sending to ES both the Fleet action response and Endpoint action response)
* common services for creating security user and stack services
* Add inline range datepicker
* Finish interscheduler UI internals
* Add repeat summaries and begin implementing saving
* Fix unsnooze, move all UI to snooze notify badge
* Hook up snooze schedule api
* Finish Rule Ds List scheduling UI
* Fix half-baked dropdown work:
* Fix displaying yearly recurrences
* Move snooze scheduler into snooze panel
* Implement scheduler on shareable RuleStatusDropdown
* Fix title and typecheck
* Fix lint
* Fix typecheck
* [CI] Auto-commit changed files from 'node scripts/eslint --no-cache --fix'
* Fix types and jest
* Fix jest
* Fix functional tests
* Fix Jest
* Fix test
* Re-enable snooze status on O11y
* Fix popover title and position
* Add 24h default to snooze schedule
* Fix delete schedule button text
* Disable daily recurrence when snooze is over 24h
* Fix button size
* Use default kibana tz in scheduler
* Add scheduled snooze notification badge
* Fix compressed styling
* Compress timezone dropdown
* Memoize select options
* Sort active snoozes in descending order
* re-structure
* unit test
* fix unit test
* fix collapse snooze notification
* re-structure RuleSnoozePanel components
* Clean up helper unit test descriptions
* add unit test for CustomRecurrenceScheduler
* Add rule_snooze helpers test
* Add base snooze panel tests
* Fix test
* Consolidate repeated types
* Fix bad merge
Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
Co-authored-by: Xavier Mouligneau <xavier.mouligneau@elastic.co>
* [ML] Anomaly detection job from lens functional tests
* test commit
* adding dashboard and tests
* increasing tab switch timeout
* moving archive
* changes based on review
* fix for browser window being too small
* adding another resize after tab open
* removing commented code
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
* [Archive Migration] x-pack global_search/search_syntax
* Fix using sort.
* Drop the original archive.
* Drop the original archive.
* Reordered.
* Revert.
* [packages/kbn-performance-testing-dataset-extractor] filter server transactions by journey time range
* check only 1 ftr transaction for run is found
* fixes
* remove data and agent confirmation steps from standalone flow
* bonus: downloading policy should set step as complete
* Bring confirm incoming data step for standalone agent
Co-authored-by: Nicolas Chaulet <nicolas.chaulet@elastic.co>
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
