zuul-jobs/roles/use-buildset-registry
James E. Blair ec8a58ddb7 use-buildset-registry: Vendor pytoml and remarshal
In order to edit the V2 registries.conf file used by podman, we
need to be able to manipulate toml from ansible.  There is no
standard library or Ansible support for that now, and we don't want
to install any python packages on the remote node.  Therefore,
vendor the remarshal and pytoml code into this role.

This is done in a standalone commit for easier review and auditing.

The originating projects are:

  https://github.com/dbohdan/remarshal
  https://github.com/avakar/pytoml

And both are MIT licensed.  Appropriate headers are added where
necessary.

Note that pytoml has been concatenated into one file in order to
adhere to Ansible's requirements for python modules.

Change-Id: I679ea5eb5cb29591be09d2f1b712400c49158abd
2019-12-03 14:10:23 -08:00
..
module_utils use-buildset-registry: Vendor pytoml and remarshal 2019-12-03 14:10:23 -08:00
tasks Use zuul-registry as buildset registry 2019-10-28 15:42:26 -07:00
README.rst Use zuul-registry as buildset registry 2019-10-28 15:42:26 -07: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.