ricardozanini opened a new issue, #3124:
URL: https://github.com/apache/incubator-kie-tools/issues/3124
To support disconnected and air-gapped environments, the builder image
should be enhanced to:
1. Include a **pre-configured Quarkus registry client** pointing to a known,
trusted registry (e.g. Quarkus).
2. Ship with a **local cache of the Quarkus extension registry** so that
extension metadata can be resolved without requiring external network access.
3. Allow **overriding the registry configuration at build time** via
environment variables or volume mounts.
---
**Acceptance Criteria:**
* [ ] The builder image includes a default `.quarkus/config.yaml` placed
under `$HOME/.quarkus/`
* [ ] The image includes a **local extension registry cache**
* This cache must be discoverable by the Quarkus CLI and Maven plugin
* Should contain the metadata and catalog for `quarkus-platform` and any
used extensions
* [ ] If an environment variable like `QUARKUS_REGISTRY_CONFIG_PATH` is
defined, the image startup scripts copy the given file into
`$HOME/.quarkus/config.yaml` to override the default
* [ ] Optional: Provide an env var (`USE_LOCAL_REGISTRY_CACHE=true`) to
explicitly enable/disable using the local cache directory, defaulting to true
in the image
* [ ] Document:
* How to override the registry config
* How to update the local cache
* How to test `quarkus:add-extension` and `mvn clean install` offline
---
**Motivation:**
When using the builder image in air-gapped or proxy-restricted CI
environments, `quarkus:add-extension` and related Maven plugin invocations fail
if Quarkus attempts to contact the default extension registry at
`https://registry.quarkus.io`.
By bundling a local copy of the registry metadata and configuring Quarkus to
use it, we ensure:
* **100% offline builds**
* **Reproducibility**
* **Speed**, by avoiding external lookups
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
