Skip to content
This repository has been archived by the owner on Jan 23, 2024. It is now read-only.

Cannot run 7.x build candidates with snapshot registry #1068

Closed
axw opened this issue Feb 24, 2021 · 2 comments · Fixed by #1069
Closed

Cannot run 7.x build candidates with snapshot registry #1068

axw opened this issue Feb 24, 2021 · 2 comments · Fixed by #1069
Assignees

Comments

@axw
Copy link
Member

axw commented Feb 24, 2021

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.

@axw axw added the bug label Feb 24, 2021
@kuisathaverat
Copy link
Contributor

I think this setting is not implemented yet, IIRC the registry is forced based on the version you are using see elastic/kibana#90327

@axw
Copy link
Member Author

axw commented Feb 24, 2021

Yep, I'm in the process of adding a flag to control the registry URL used in Kibana.

@axw axw self-assigned this Feb 24, 2021
@axw axw added enhancement and removed bug labels Feb 24, 2021
@axw axw closed this as completed in #1069 Feb 25, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants