openshift / openshift/oadp-operator
Build and deploy operator using plugins/velero from remote branch
Open
Nobody has claimed this yet.
lifecycle/frozen
- Dominant language
- Go
- Stars
- 92
- Forks
- 93
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 43
Description
Ability to customize branch of plugins used when deploying.
Today OADP Operator uses images that are built post-submit in repos, pushed to openshift ci registry but are not promoted to quay.io for pulling for up to an hour later.
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 tracing how the OADP Operator selects plugin images during build and deployment. Define the configuration path for choosing a remote plugin branch, then verify that the resulting images can be built and deployed without waiting for promotion to quay.io.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- devops, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100