Add bundle library to build bundle manifest image#97
Add bundle library to build bundle manifest image#97openshift-merge-robot merged 7 commits intooperator-framework:masterfrom
Conversation
|
@dinhxuanvu won't this break the makefile because you are nesting an additional package into the |
|
@kevinrizza This is just a cherry-pick PR from original PR in OLM repo. I'm working on separating the functional code into an actual package under |
93c3351 to
9b53535
Compare
9b53535 to
1fda468
Compare
|
/test unit |
090f87b to
52b73ff
Compare
ecordell
left a comment
There was a problem hiding this comment.
This looks great! Tests and docs are great as well.
I have one comment on the labels for future-proofing, but once you make those changes we should merge 🎉
|
Ah, one issue to resolve for the tests: |
|
/retest |
693e669 to
24a26d3
Compare
|
/retest |
kevinrizza
left a comment
There was a problem hiding this comment.
Nice job on this! I just had a few small comments.
|
|
||
| bundleBuildCmd.Flags().StringVarP(&imageBuilderArgs, "image-builder", "b", "docker", "Tool to build container images. One of: [docker, podman, buildah]") | ||
|
|
||
| bundleBuildCmd.Flags().StringVarP(&channelDefaultArgs, "default", "e", "", "The default channel for the bundle image") |
There was a problem hiding this comment.
maybe defaultChannel is a better name here?
There was a problem hiding this comment.
The defaultChannel is a fine name but the reason I use default here is to keep the command flag to be as short as possible. Long name only makes the command even longer and difficult to read. I try to keep all flags to be single word with the exception of image-builder because SDK has the a flag with that name with the same functionality. So I decided to keep it the same as SDK to keep the consistency given this command will be added to SDK.
|
Sorry one more request @dinhxuanvu , can you squash your commits? There's a lot of old history that isn't really relevant anymore. |
89f5204 to
6c117a3
Compare
1. Add top level CLI command `operator-cli` 2. Add bundle command to generate annotations.yaml and Dockerfile 3. Add bundle command to build Bundle image * The build command will generate annotations.yaml and Dockerfile as well 4. Add unit test cases for operator bundle commands 5. Add operator bundle documentation Signed-off-by: Vu Dinh <vdinh@redhat.com>
1. Move bundle funcs to /pkg as a bundle package 2. ix some minor errors in unit test. 3. Modify bundle doc to reflect recent changes + operator-sdk information + Folder structure 4. Add bundle command to opm binary as hidden commands + The bundle commands are only available for internal development use as a part of opm binary. 5. Move bundle doc under /docs/design. Signed-off-by: Vu Dinh <vdinh@redhat.com>
1. Package name, channels, default channel info is now added to annotations.yaml 2. `bundle generate` will retain overwritten ability while `bundle build` will only overwrite Dockerfile. 3. Validate annotations.yaml if existed. 4. `--overwrite/o` flag is available to overwrite annotations.yaml during build command. Signed-off-by: Vu Dinh <vdinh@redhat.com>
Signed-off-by: Vu Dinh <vdinh@redhat.com>
Signed-off-by: Vu Dinh <vdinh@redhat.com>
f033b42 to
0bb8f40
Compare
|
Ready for another round of review. |
1ceb026 to
8037b61
Compare
|
lgtm |
1. Clarify a few helper texts in cli code 2. Improve librar document to specific input information 3. Move `bundle` comands under hidden `alpha` command Signed-off-by: Vu Dinh <vdinh@redhat.com>
8037b61 to
ee575b1
Compare
|
lgtm |
Signed-off-by: Vu Dinh <vdinh@redhat.com>
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dinhxuanvu, jpeeler The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
opmas well
Signed-off-by: Vu Dinh vdinh@redhat.com
Description of the change:
Motivation for the change:
Reviewer Checklist
/docs