-
-
Notifications
You must be signed in to change notification settings - Fork 36
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
Add ContainerPodman class #130
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #130 +/- ##
=======================================
Coverage 86.37% 86.37%
=======================================
Files 1 1
Lines 279 279
=======================================
Hits 241 241
Misses 38 38 ☔ View full report in Codecov by Sentry. |
c10ebad
to
1384f6b
Compare
Given there's no difference, I wonder if this is a benefit. Would it make sense to go the other direction and use |
I've no opinions here. I'm fine with every implementation. |
FWIW, I also think that this being |
Or, we keep the gem |
@evgeni like this? And then use container_podman as hypervisor in GHA-puppet and not docker_podman? |
require 'beaker/hypervisor/docker' | ||
|
||
module Beaker | ||
class ContainerPodman < Beaker::Docker |
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.
mhm or should it inherit from Beaker::Container?
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.
Technically, Beaker::Container
, not that it makes a difference today…
Yepp |
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 this is a good start, but I'd lean to:
- Rename
Beaker::Docker
toBeaker::Container
- Introduce
Beaker::ContainerDocker
,Beaker::ContainerPodman
andBeaker::ContainerSwam
that inherit fromBeaker::Container
Then deprecate Beaker::Docker
. At first we can keep all the code in a single class but later we can differentiate in different ways.
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.
New GH mobile app stinks
This allows us to set the beaker hypervisor not only to `docker`, but also to `docker_podmand`. This enables us to implement podman specific patches (if we ever need to). But it also makes it easier for modules to specify if they want to use podman or docker. See voxpupuli/gha-puppet#48 for reference.
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.
One day I'll figure out why these are called Beaker::Something
but live in beaker/hypervisor/something
. Today is not the day to think about that tho.
This allows us to set the beaker hypervisor not only to
docker
, but also todocker_podman
. This enables us to implement podman specific patches (if we ever need to). But it also makes it easier for modules to specify if they want to use podman or docker. See voxpupuli/gha-puppet#48 for reference.