Skip to content
Runbooks

Pulp (pulp.pre.gitlab.net) Service

Logging

Section titled “Logging”

Documentation

Section titled “Documentation”

Summary

Section titled “Summary”

Pulp is set up via:

Architecture

Section titled “Architecture”

Infrastructure Architecture overview

Pulp CLI

Section titled “Pulp CLI”

The Pulp CLI is a command-line interface for interacting with the Pulp service. It can be used for various administrative tasks, including user management, repository management, and content synchronization.

Installation

Section titled “Installation”

Follow the Pulp CLI installation guide.

Configuration

Section titled “Configuration”

Before using the Pulp CLI, you need to configure it to connect to your Pulp instance. This typically involves setting the base URL, API root, and authentication credentials.

Terminal window
export PULP_ADMIN_PASSWORD=$(kubectl get secret pulp-custom-admin-password -o jsonpath='{.data.password}' | base64 -d)
export PULP_DOMAIN=<pulp-domain> # e.g., pulp.pre.gitlab.net


pulp config create \
  --base-url "https://${PULP_DOMAIN}" \
  --api-root "/pulp/" \
  --verify-ssl \
  --format json \
  --username admin \
  --password "${PULP_ADMIN_PASSWORD}" \
  --timeout 0

Note: Replace <pulp-domain> with the actual domain of your Pulp instance. The PULP_ADMIN_PASSWORD is retrieved from a Kubernetes secret, which assumes you have kubectl access to the cluster where Pulp is deployed.

Basic Usage

Section titled “Basic Usage”

Once configured, you can use the pulp command to interact with the service.

Checking Pulp Status

Section titled “Checking Pulp Status”

To verify that the CLI can connect to the Pulp instance and that the service is running:

Terminal window
pulp status

Listing Users

Section titled “Listing Users”

To list all users configured in Pulp:

Terminal window
pulp user list

Listing Roles

Section titled “Listing Roles”

To list available roles for role-based access control (RBAC):

Terminal window
pulp role list

Further Documentation

Section titled “Further Documentation”

For more detailed information on specific CLI commands and use cases, refer to: