zuul-jobs/roles/use-buildset-registry
Andrii Ostapenko fd2dc3bc91
Fix certificate issue with use buildset registry
Use buildset_registry_alias for certificate file name to address
'unknown certificate authority' issue on consumer side when using standalone
use-buildset-registry role.

Issue is not visible with opendev parent jobs because certificate is handled
in pull-from-intermediate-registry role there.

Change-Id: Ieaf43be0dd4ccb92a8240a493ee6636a23c9d484
Signed-off-by: Andrii Ostapenko <andrii.ostapenko@att.com>
2020-09-29 10:24:23 -05:00
..
defaults use-buildset-registry: Add podman support 2019-12-05 11:44:15 -08:00
library Write buildkitd.toml in use-buildset-registry 2020-05-05 14:47:19 -05:00
module_utils use-buildset-registry: Vendor pytoml and remarshal 2019-12-03 14:10:23 -08:00
tasks Fix certificate issue with use buildset registry 2020-09-29 10:24:23 -05:00
vars use-buildset-registry: add Fedora certifacts vars 2020-04-30 17:34:04 +00:00
__init__.py use-buildset-registry: Add podman support 2019-12-05 11:44:15 -08:00
README.rst use-buildset-registry: Add podman support 2019-12-05 11:44:15 -08:00

Adds a buildset registry to the docker configuration.

Use this role on any host which should use the buildset registry.

Role Variables

Information about the registry, as returned by :zuulrun-buildset-registry.

The host (IP address) of the registry.

The port on which the registry is listening.

The username used to access the registry via HTTP basic auth.

The password used to access the registry via HTTP basic auth.

The (self-signed) certificate used by the registry.