mirror of
https://github.com/elastic/kibana.git
synced 2025-06-27 10:40:07 -04:00
68466226b3
* Support installing bundled packages during Fleet setup
* Fix failing API integration test
* Sort packages in test
* Move get bundled packages + add tests
* Fix mock installPackage type
* Don't attempt to install already-installed bundled packageS
* Use unique installation status for bundled packages
* Fix failing tests
* Fix type error
* Fix logic for latest value
* Remove bundled packages from test since they no longer come back from list endpoint
* Change assertion for empty preconfiguration update request
* Add all bundled packages + refactor install to use Promise.allSettled
* Fix name comparison again
* Rework approach to use preferred source at install-time instead
* Add helper script + update bundled packages + allow updates for upload path
* Fix failing test
* Address code review + add additional tests for update cases
* Fix type error
* Remove configOverride concept for now
* Fix another type error 🙃
* Add build step for bundling fleet packages
* Fix unused import in build step
* Keep bundled_packages directory in place to prevent setup failures
* Remove gitkeep + make bundled package directory lookup fault tolerant
* Update gitignore
* Add doc comment + use build.resolvePath
* Add --use-snapshot-registry CLI flag
* Update snapshots
* Rename arg to use-snapshot-epr
* Don't fail the build on failure to bundled packages
* Update all checksums + don't attempt download multiple times
* Skip checksum process for bundled packages for now
* mkdirp destination directory to fix tests
* Revert build_distributables file
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
36 lines
1.3 KiB
JSON
36 lines
1.3 KiB
JSON
/*
|
|
|
|
Packages in this file are considered "bundled" and are installed as part of Fleet's setup process. Each entry points to a valid version name
|
|
avaiable in the Elastic Package Registry service, and must include a sha-512 checksum of the `.zip` archive for the given package.
|
|
|
|
You may opt in to using the "snapshot" environment of the EPR service by passing the `--use-epr-snapshot-registry` flag to `yarn build`. This will
|
|
cause the package archive download to pull from the "spapshot" environment instead of the "production" environment. Be aware that not all packages
|
|
exist in the snapshot environment, so you may have errors when fetching package versions. It's recommended to alter this file to contain _only_ the
|
|
packages you're testing when using the snapshot environment.
|
|
|
|
These files don't include any kind of checksum, but they should eventually include a package signature as introduced in https://github.com/elastic/elastic-package/issues/583
|
|
in order to verify package integrity.
|
|
*/
|
|
|
|
[
|
|
{
|
|
"name": "apm",
|
|
"version": "8.0.0"
|
|
},
|
|
{
|
|
"name": "elastic_agent",
|
|
"version": "1.3.0"
|
|
},
|
|
{
|
|
"name": "endpoint",
|
|
"version": "1.4.1"
|
|
},
|
|
{
|
|
"name": "fleet_server",
|
|
"version": "1.1.0"
|
|
},
|
|
{
|
|
"name": "synthetics",
|
|
"version": "0.9.0"
|
|
}
|
|
]
|