-
Notifications
You must be signed in to change notification settings - Fork 1
Add support to interact with a local podman installation #211
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
6d29503 to
9aff29a
Compare
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## main #211 +/- ##
==========================================
- Coverage 91.54% 91.18% -0.36%
==========================================
Files 42 44 +2
Lines 2070 2372 +302
==========================================
+ Hits 1895 2163 +268
- Misses 175 209 +34 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
9aff29a to
41c4a3a
Compare
vivus-ignis
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please add tests. I've also added some suggestions.
5eea9cf to
0f14ce7
Compare
4d6fba8 to
01a90ec
Compare
677b956 to
0915535
Compare
7aa9d6a to
7029e14
Compare
Signed-off-by: Tobias Wolf <[email protected]>
7029e14 to
b9039cc
Compare
Code is now ready for review, I would highly appreciate your feedback @vivus-ignis. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The code looks good to me, but the user experience of the gl-oci has a room for improvements. It's not obvious what is this tool is for in general and how to use it (see my comments on naming).
| """ | ||
| gl-oci main entrypoint | ||
| """ | ||
|
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think there's a general issue with naming here. A container is something running, while image is a filesystem snapshot. I think using word "container" here is confusing:
Commands:
add-container-to-index Adds an image container to an OCI image...
build-container Build an OCI container based on the...
load-container Push to an OCI registry.
load-containers-from-directory Push to an OCI registry.
new-index Push a list of files from the...
pull-container Push to an OCI registry.
push-container Push to an OCI registry.
push-manifest Push artifacts and the manifest from a...
push-manifest-tags Push artifacts and the manifest from a...
save-container Push to an OCI registry.
tag-container Push to an OCI registry.
update-index Push a list of files from the...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
An OCI container is the most generic term to refer to an OCI resource. I do agree that functions like pull-container could be named as pull-image but for e.g. tag-container it would have to stay generic as this method supports all OCI resources like index and manifest as well. It seems to be more convenient to use the same term for these functions.
Signed-off-by: Tobias Wolf <[email protected]> On-behalf-of: SAP <[email protected]>
Signed-off-by: Tobias Wolf <[email protected]> On-behalf-of: SAP <[email protected]>
0dbdc21 to
67d413d
Compare
What this PR does / why we need it:
This PR adds support to interact with a local podman installation.
Which issue(s) this PR fixes:
Closes #199
Closes #200