automation-tests/cmd/podman/networks
Daniel J Walsh 75419c5d88
When removing objects specifying --force,podman should exit with 0
This Patch will cause podman COMMAND rm --force bogus not fail

This is how Docker works, so Podman should follow this to allow existing
scripts to convert from Docker to Podman.

Fixes: #14612
Oprignal version of this patch came from wufan 1991849113@qq.com

Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
2022-07-26 16:00:42 -04:00
..
connect.go bump go module to version 4 2022-01-18 12:47:07 +01:00
create.go docs: remove CNI word where it is not applicable 2022-07-22 13:46:28 +02:00
disconnect.go bump go module to version 4 2022-01-18 12:47:07 +01:00
exists.go bump go module to version 4 2022-01-18 12:47:07 +01:00
inspect.go docs: remove CNI word where it is not applicable 2022-07-22 13:46:28 +02:00
list.go shell completion --format: use structs by reference 2022-04-28 18:12:17 +02:00
network.go bump go module to version 4 2022-01-18 12:47:07 +01:00
prune.go Refactored networkPrune function 2022-07-08 08:33:20 +09:00
reload.go Combine the CheckAllLatest CID and PodID functions 2022-05-26 11:12:40 -04:00
rm.go When removing objects specifying --force,podman should exit with 0 2022-07-26 16:00:42 -04:00