Add openshift resource to manage pulp repository actions(create/sync/publish)
Open
Nobody has claimed this yet.
Feature
- Dominant language
- Go
- Stars
- 88
- Forks
- 66
- Avg merge
- 53m
- Merged PRs (30d)
- 1
Description
We are planning to move from pulp runinng on a VM to operator in openshift . From infrastructure as a code perspective , it would be great to control the repoistory actions like creating syncing and all also via openshift resources . If not separate automation tool has to be used for maanging repository part alone .
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Start by surveying the pulp-operator repository and its existing Kubernetes resources, then clarify the resource design and completion criteria for creating, syncing, and publishing Pulp repositories.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100