pulp / pulp/pulp-cli

Add options for creating pull-through remote and distributions

Open
#1,034 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

feature request
Dominant language
Python
Stars
43
Forks
52
Avg merge
11h 38m
Merged PRs (30d)
11

Description

Summary

Currently, the container plugin offers the option of creating pull-through remotes and distributions as tech preview.
However, even at this stage, the feature is very useful and it would be nice to have contexts for it in pulp_glue and options for it in the CLI.
In terms of the CLI, I believe it could work as verbatim publications, by specifying a "type" argument.

Versions

pulpcore: 3.55 (currently installed version, likely applies to 3.56.1 as well)
pulp_container: 2.18.0 (introduced the pull-through feature)

Examples

Current state, from the pulp_container plugin documentation:

# initialize a pull-through remote (the concept of upstream-name is not applicable here)
REMOTE_HREF=$(http ${BASE_ADDR}/pulp/api/v3/remotes/container/pull-through/ name=docker-cache url=https://registry-1.docker.io | jq -r ".pulp_href")

# create a pull-through distribution linked to the initialized remote
http ${BASE_ADDR}/pulp/api/v3/distributions/container/pull-through/ remote=${REMOTE_HREF} name=docker-cache base_path=docker-cache

Idealised state (suggestion):

REMOTE_HREF=$(pulp container remote create --type pull-through --name docker-cache --url https://registry-1.docker.io | jq -r ".pulp_href")

pulp container distribution create --type pull-through --remote-href "$REMOTE_HREF"

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the existing container remote and distribution commands and their pulp_glue contexts, then compare them with the pull-through API examples and the proposed --type usage in the issue. Done means the CLI exposes options for creating pull-through remotes and distributions and supports the documented workflow.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
api, cli
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.