operator-framework / operator-framework/operator-sdk
bundle.Dockerfile path should be parameterized
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 7.7k
- Forks
- 1.8k
- PR merge metrics
- No merged PRs in 30d
Description
Feature Request
bundle.Dockerfile path should be parameterized
Describe the problem you need a feature to resolve.
Currently bundle.Dockerfile by default generates at root directory of project.
Olm also expect dockerFile along the bundle dir.see
Currently we have to copy this file manually and edit the relative path of the content like manifest and metadata path.
Describe the solution you'd like.
It would be better if we could define --bundle.Dockerfile path and its name as input arg to operator-sdk generate bundle cmd
/language go
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
Start with the operator-sdk generate bundle command and trace how it currently creates bundle.Dockerfile at the project root. Check the command's existing input arguments and generated bundle layout, then verify that a user-supplied path and filename place the Dockerfile alongside the bundle without breaking its relative manifest and metadata paths.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- build-system, cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100