You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 23, 2024. It is now read-only.
I'd like to test the 7.12 build candidates with Fleet, using the APM package in the snapshot package registry. When running a build candidate of Kibana, it will interact with the production package registry by default. This can be overridden with XPACK_FLEET_REGISTRYURL (xpack.fleet.registryUrl).
When running the managed APM Server service, one can pass the --package-registry-snapshot flag to direct it to use the snapshot registry. However, this only sets XPACK_FLEET_REGISTRYURL for the managed APM Server service. It should also be set for the Kibana process, so Kibana can fetch packages from the appropriate registry.
The text was updated successfully, but these errors were encountered:
I'd like to test the 7.12 build candidates with Fleet, using the APM package in the snapshot package registry. When running a build candidate of Kibana, it will interact with the production package registry by default. This can be overridden with
XPACK_FLEET_REGISTRYURL
(xpack.fleet.registryUrl
).When running the managed APM Server service, one can pass the
--package-registry-snapshot
flag to direct it to use the snapshot registry. However, this only setsXPACK_FLEET_REGISTRYURL
for the managed APM Server service. It should also be set for the Kibana process, so Kibana can fetch packages from the appropriate registry.The text was updated successfully, but these errors were encountered: