With https://github.com/elastic/package-storage/issues/86 we have now 3 registries available: production, staging, snapshot. Our current master snapshot build should point to the snapshot registry. The 7.x and 7.8 branch both should point to the production registry. It means, if someone runs the master snapshot builds, he always has the most recent packages available.
This also ensures, we don't accidentally ship with the production registry. The only time we need to be careful, is when we will branch of 8.x from master. At this stage, we need to switch over the registry in 8.x to prod again.
The registry URL used is: https://epr-snapshot.ea-web.elastic.dev The reasons is that the CDN URL is not deployed yet. As soon as the CDN is available, we should switch it over to : https://epr-snapshot.elastic.co The reason I'm already switching over is to make sure we can use the snapshot branch as soon as possible.
* WiP load from json modal ready, need to refactor more stuff
* First iteration of load from JSON functionality
- refactored the pipeline processsors editor components for
portability
- added CIT for load from json component
* added comment
* update deserialize with tests and make it more fault tolerant
* use flyout footer
* remove console.error and make the json editor a lot shorter
* address PR feedback
- Update form schema and form schema types
- simplify the save handler
- refactor processors_title to processors_header
* remove unused translations
Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
* Add sorting params to list endpoints; allow sorting on agent config and package config tables; normalize casing of 'desc' and 'asc'
* Fix es archiver data
* Fix tests
* [Alerting] document requirements for developing new action types
resolves https://github.com/elastic/kibana/issues/67864
Adding this to the actions README.md, it should be published as asciidocs at GA.
* Fixed adding an extra space character on selecting alert variable in action text fields.
* Made components for variables to be able to insert the variable by the cursor position
* cleanup
* Added variables support for all components
* update on handle selections for text
* Fixed functional tests
* [Maps] show vector tile labels on top
* experiment with new sort algorithm
* clean up
* remove old sort method
* add unit test for sort layer
* tslint
* clean up
* make labelsOnTop configurable
* tslint
* more tslint
* add another test case for single layer move
* clarify should messages
* fix assert not null operators
* review feedback
* update snapshot
Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
* chore(NA): upgrade oss to lodash4
chore(NA): migrate cli, cli_plugin, cli_keystore, dev, test_utils and apm src script to lodash4
chore(NA): missing file for cli plugin
chore(NA): add src core
chore(NA): es archiver and fixtures
chore(NA): try to fix functional test failure
chore(NA): migrate src/legacy entirely to lodash4 except src/legacy/core_plugins
chore(NA): move legacy core plugins to lodash4
chore(NA): upgrade optimize to lodash4
chore(NA): upgrade to lodash4 on advanced_settings, charts, console and dashboard
chore(NA): migrate to lodash4 on dev_tools, discover, embeddable, es_ui)shared, expressions, home plugins
chore(NA): upgrade data plugin to lodash4
chore(NA): upgrade usage_collection, ui_actions, tile_map, telemtry, share, saved_objects, saved_objects_management, region_map and navigation to lodash4
chore(NA): missing data upgrades to lodash4
Revert "chore(NA): upgrade usage_collection, ui_actions, tile_map, telemtry, share, saved_objects, saved_objects_management, region_map and navigation to lodash4"
This reverts commit 137055c5fed2fc52bb26547e0bc1ad2e3d4fe309.
Revert "Revert "chore(NA): upgrade usage_collection, ui_actions, tile_map, telemtry, share, saved_objects, saved_objects_management, region_map and navigation to lodash4""
This reverts commit f7e73688782998513d9fb6d7e8f0765e9beb28d1.
Revert "chore(NA): missing data upgrades to lodash4"
This reverts commit 92b85bf947a89bfc70cc4052738a6b2128ffb076.
Revert "chore(NA): upgrade data plugin to lodash4"
This reverts commit 88fdb075ee1e26c4ac979b6681d8a2b002df74c6.
chore(NA): upgrade idx_pattern_mgt, input_control_vis, inspector, kbn_legacy, kbn_react, kbn_usage_collections, kbn_utils, management and maps_legacy to lodash4
chore(NA): map src plugin data to lodash3
chore(NA): missing lodash.clonedeep dep
chore(NA): change packages kbn-config-schema deps
chore(NA): update renovate config
chore(NA): upgrade vis_type plugins to lodash4
chore(NA): move vis_type_vislib to lodash3
chore(NA): update visualizations and visualize to lodash4
chore(NA): remove lodash 3 types from src and move test to lodash4
chore(NA): move home, usage_collection and management to lodash 3
Revert "chore(NA): move home, usage_collection and management to lodash 3"
This reverts commit f86e8585f02d21550746569af54215b076a79a3d.
chore(NA): move kibana_legacy, saved_objects saved_objects_management into lodash3
chore(NA): update x-pack test to mock lodash4
Revert "chore(NA): move kibana_legacy, saved_objects saved_objects_management into lodash3"
This reverts commit 2d10fe450533e1b36db21d99cfae3ce996a244e0.
* chore(NA): move x-pack and packages to lodash 4
* chore(NA): remove mention to lodash from main package.json
* chore(NA): remove helper alias for lodash4 and make it the default lodash
* chore(NA): fix last failing types in the repo
* chore(NA): fix public api
* chore(NA): fix types for agg_row.tsx
* chore(NA): fix increment of optimizer modules in the rollup plugin
* chore(NA): migrate `src/core/public/http/fetch.ts` (#5)
* omit undefined query props
* just remove merge usage
* fix types
* chore(NA): fixes for feedback from apm team
* chore(NA): recover old behaviour on apm LoadingIndeicatorContext.tsx
* chore(NA): fixes for feedback from watson
* Platform lodash4 tweaks (#6)
* chore(NA): fix types and behaviour on src/core/server/elasticsearch/errors.ts
* Canvas fixes for lodash upgrade
* [APM] Adds unit test for APM service maps transform (#7)
* Adds a snapshot unit test for getConnections and rearranges some code to make testing easier
* reverts `ArrayList` back to `String[]` in the painless script within `fetch_service_paths_from_trace_ids.ts`
* chore(NA): update yarn.lock
* chore(NA): remove any and use a real type for alerts task runner
Co-authored-by: Gidi Meir Morris <github@gidi.io>
* chore(NA): used named import for triggers_actions_ui file
* chore(NA): fix eslint
* chore(NA): fix types
* Delete most uptime lodash references.
* Simplify. Clean up types.
* [Uptime] Delete most uptime lodash references (#8)
* Delete most uptime lodash references.
* Simplify. Clean up types.
* chore(NA): add eslint rule to avoid using lodash3
* chore(NA): apply changes on feedback from es-ui team
* fix some types (#9)
* Clean up some expressions types.
* chore(NA): missing ts-expect-error statements
* Upgrade lodash 4 vislib (#11)
* replace lodash 3 with lodash 4 on vislib plugin
* Further changes
* further replacement of lodash3 to 4
* further work on upgrading to lodash 4
* final changes to update lodash
* chore(NA): upgrade data plugin to lodash4
chore(NA): upgrade data plugin public to lodash4
chore(NA): fix typecheck task
chore(NA): fix agg_config with hasIn
chore(NA): assign to assignIn and has to hasIn
chore(NA): upgrade data plugin server to lodash4
chore(NA): new signature for core api
fix(NA): match behaviour between lodash3 and lodash4 for set in search_source
* chore(NA): remove lodash3 completely from the repo
* chore(NA): fix x-pack/test/api_integration/apis/metrics_ui/snapshot.ts missing content
* chore(NA): fix lodash usage on apm
* chore(NA): fix typecheck for maps
* Patch lodash template (#12)
* Applying changes from https://github.com/elastic/kibana/pull/64985
* Using isIterateeCall, because it seems less brittle
* Also patching `lodash/template` and `lodash/fp/template`
* Reorganizing some files...
* Revising comment
* Ends up `_` is a function also... I hate JavaScript
Co-authored-by: Pierre Gayvallet <pierre.gayvallet@gmail.com>
Co-authored-by: Josh Dover <me@joshdover.com>
Co-authored-by: Clint Andrew Hall <clint.hall@elastic.co>
Co-authored-by: Oliver Gupte <ogupte@users.noreply.github.com>
Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
Co-authored-by: Gidi Meir Morris <github@gidi.io>
Co-authored-by: Justin Kambic <justin.kambic@elastic.co>
Co-authored-by: Stratoula Kalafateli <stratoula1@gmail.com>
Co-authored-by: Luke Elmers <luke.elmers@elastic.co>
Co-authored-by: Brandon Kobel <brandon.kobel@gmail.com>
Co-authored-by: kobelb <brandon.kobel@elastic.co>
### Summary
On initial render of the SIEM pages, a 400 error was showing for POST http://localhost:5601/api/detection_engine/signals/search. This PR is a temporary fix for this bug. This initial call is being used to populate the Last alert text that shows at the top of a number of the pages. The reason the size was 0 is because we weren't interested in the signals themselves, just the timestamp of the last alert. Teamed up with @XavierM and it seems to us that the issue is the server side validation. It may be Hapi misreading the 0 as false or our updated validation not accepting size 0.
As the base assets will be shipped by ES directly, the base package is not needed anymore. https://github.com/elastic/elasticsearch/pull/57629
In the future we might reintroduce it to update the installed assets.
FOSSA analysis by default checks for dependencies in the following order:
1. Parse output from `npm ls --json --production` - Runs if npm exists on the system and provides an accurate list of all dependencies needed to build the production project.
2. Parse `package.json` - Runs if `package.json` can be successfully parsed into a dependency graph.
3. Run yarn list --json - This command verifies through yarn what the actual dependencies which are installed on the system are. This strategy runs with `NODE_ENV=production` by default to find production dependencies.
4. Parse `yarn.lock` - Detects dependencies based on the yarn lockfile.
5. Parse `npm-shrinkwrap.json` - Detects dependencies based on the lockfile.
6. Parse `package-lock.json` - Detects dependencies based on the lockfile.
Since our dependencies specified in `package.json` use compatible version matching (`^`), the reported version would often not be what the `yarn.lock` is currently specified to use. Because of this, we are defining a single module with a strategy on `yarn.lock`. Our `yarn.lock` file includes all dependencies.
Signed-off-by: Tyler Smalley <tyler.smalley@elastic.co>
* updates apm integration job to work with service maps
* rename apm job in setup_module test
* modifies detector description
Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
In https://github.com/elastic/package-registry/issues/517 the naming of the file paths inside a package is standardised to only use `_` and not `-`. This adjusts the paths for `ilm-policy`, `component-template`, `index-template` to the correct path.
An additional change here is to get rid of assets we don't support yet, like rollup jobs and ml jobs. We will reintroduce these when we support them.
* Allow doc_values to be disabled
* Make doc_values optional
* doc_values type for CoreFieldMapping
* doc_values not doc_value
* Update docs
Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
* Sort endpoint responses into indices and datastreams
The server endpoint for policies now returns data streams and
filters out backing indices from the indices array it returned
previously
* Refactor indices switch and field out of the step settings file
* Fix indices field form behaviour
* WiP on UI. Added the second table per mockup for add and edit.
* add support for creating a policy that backs up data streams end to end
* wip on restore flow - added data streams to server response
* add logic for detecting whether an index is part of a data stream
* fix public jest tests
* fix server side jest tests
* pivot to different solution in UI while we do not have data streams nicely separated
* added data stream to snapshot summary details
* move the data streams badge file closer to where it used
* add data stream badge when restoring snapshots too
* update restore copy
* fix pattern specification in indices and data streams field
* first iteration of complete policy UX
* First iteration that is ready for review
Given the contraints on working with data streams and indices in policies
at the moment the simplest implementation is to just include data streams
with indices and have the user select them there for now.
The way snapshotting behaviour is currently implemented relies entirely
on what is specified inside of "indices", this is also where data
streams must be placed. This unfortunately means that capture patterns
defined in indices will capture entire data streams too.
* delete unused import
* fix type issue in tests
* added logic for rendering out previous selection as custom pattern
* refactor indices fields to make component smaller
* added CIT for data streams badge
* Data streams > indices
* updates to relevant pieces of copy
* more copy updates
* fix types and remove unused import
* removed backing indices from restore view
* Added data stream restore warning message
* restore CITs
* first round of copy feedback
* refactor help text to provide clearer feedback, for both restore and policy forms
* Restore updates
- added spacer between title and data streams callout
- added copy to the restore settings tab to indicate that settings
also apply to backing indices
* further copy refinements
* second round of copy feedback
* fix i18n
* added comment to mock
* line spacing fixes and created issue for tracking backing index discovery in snaphots
* refactor collapsible list logic and tests
* refactor editing managed policy check
* refactor copy to be clearer about pluralisation of data streams
* refactor file structure in components for data stream badge
* added tests for indices and data streams field helper
* refactored types and fixed i18n id per guidelines
Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>