automation-tests/cmd/podman/machine
Paul Holzinger 4374038cc6
pkg/machine/e2e: do not import from cmd/podman
It should be avoided to import cmd/podman/... packages from outside of
cmd/podman. This can lead in weird hard to debug import paths but also
can have negative consequences when imported in unit tests. In this case
it will set XDG_CONFIG_HOME and thus the machine tests this dir over the
tmp HOME env variable which is set at a later point. This caused machine
files to be leaked into the actual users home dir.

Signed-off-by: Paul Holzinger <pholzing@redhat.com>
2022-07-07 20:48:28 +02:00
..
info.go Podman machine info 2022-07-05 15:18:41 -04:00
init.go cmd/podman: switch to golang native error wrapping 2022-06-30 12:58:57 +02:00
inspect.go Only allow Rootless runs of Podman Machine 2022-06-29 09:19:09 -04:00
list.go pkg/machine/e2e: do not import from cmd/podman 2022-07-07 20:48:28 +02:00
machine.go Podman machine info 2022-07-05 15:18:41 -04:00
machine_unix.go Fix podman machine on Windows 2022-06-30 16:21:59 -05:00
machine_unsupported.go go fmt: use go 1.18 conditional-build syntax 2022-03-18 09:11:53 +01:00
machine_windows.go Fix podman machine on Windows 2022-06-30 16:21:59 -05:00
platform.go podman system reset removed machines incorrectly 2022-05-04 10:31:42 -04:00
platform_windows.go podman system reset removed machines incorrectly 2022-05-04 10:31:42 -04:00
rm.go Only allow Rootless runs of Podman Machine 2022-06-29 09:19:09 -04:00
set.go Only allow Rootless runs of Podman Machine 2022-06-29 09:19:09 -04:00
ssh.go cmd/podman: switch to golang native error wrapping 2022-06-30 12:58:57 +02:00
start.go cmd/podman: switch to golang native error wrapping 2022-06-30 12:58:57 +02:00
stop.go Only allow Rootless runs of Podman Machine 2022-06-29 09:19:09 -04:00