Workflows¶
If you have not yet installed the pulp_container
plugin on your Pulp installation, please follow our
User Setup. These documents will assume you have the environment installed and
ready to go.
Recommended Tools¶
httpie:
The REST API examples provided in this documentation use httpie. A user
executing the commands via httpie
is expected to have created the file .netrc
in the home
directory. The file .netrc
should have the following configuration:
machine localhost
login admin
password admin
By default, httpie
uses the configuration retrieved from .netrc
. Due to this, a custom
Authorization header is always overwritten by the Basic Authorization with the provided login and
password. In order to send HTTP requests which contain JWT Authorization headers, ensure yourself
that the plugin JWTAuth plugin is installed.
If you configured the admin
user with a different password, adjust the configuration
accordingly. If you prefer to specify the username and password with each request, please see
httpie
documentation on how to do that.
jq: This documentation makes use of the jq library to parse the json received from requests, in order to get the unique urls generated when objects are created. To follow this documentation as-is please install the jq library with:
$ sudo dnf install jq
environment variables: To make these workflows copy/pastable, we make use of environment variables. The first variable to set is the hostname and port:
$ export BASE_ADDR=http://<hostname>:24817
Container Workflows¶
- Synchronize a Repository
- Host and Consume a Container Repository
- Listing Repositories
- Manage Container Content in a Repository
- Build an OCI image from a Containerfile
- Managing Credentials
- Push content to a Repository
- Image signature configuration
- Sign images that were pushed to the Pulp Registry
- Sign images that were mirrored into the Pulp Registry from a remote Registry
- Managing signatures via the Extensions API
- Configure client signature verification policy
- Common use cases