summaryrefslogtreecommitdiff
path: root/pkg/api/handlers/compat/swagger.go
diff options
context:
space:
mode:
authorbaude <bbaude@redhat.com>2020-10-20 12:10:58 -0500
committerbaude <bbaude@redhat.com>2020-10-22 08:20:28 -0500
commit68419365257f1fcaa638605576a0583ef282a5a5 (patch)
treec2020528598b5cbff0ac22f71d392af9c9f4112e /pkg/api/handlers/compat/swagger.go
parent2cd2359a6d9ba4135495dc9be616bb1edebb170d (diff)
downloadpodman-68419365257f1fcaa638605576a0583ef282a5a5.tar.gz
podman-68419365257f1fcaa638605576a0583ef282a5a5.tar.bz2
podman-68419365257f1fcaa638605576a0583ef282a5a5.zip
APIv2 compatibility network connect|disconnect
Add endpoints for the compat layer for network connect and disconnect. As of now, these two endpoints do nothing to change the network state of a container. They do some basic data verification and return the proper 200 response. This at least allows for scripts to work on the compatibility layer instead of getting 404s. Signed-off-by: baude <bbaude@redhat.com>
Diffstat (limited to 'pkg/api/handlers/compat/swagger.go')
-rw-r--r--pkg/api/handlers/compat/swagger.go14
1 files changed, 14 insertions, 0 deletions
diff --git a/pkg/api/handlers/compat/swagger.go b/pkg/api/handlers/compat/swagger.go
index 371d02388..0a514822b 100644
--- a/pkg/api/handlers/compat/swagger.go
+++ b/pkg/api/handlers/compat/swagger.go
@@ -63,3 +63,17 @@ type swagCompatNetworkCreateResponse struct {
// in:body
Body struct{ types.NetworkCreate }
}
+
+// Network disconnect
+// swagger:model NetworkConnectRequest
+type swagCompatNetworkConnectRequest struct {
+ // in:body
+ Body struct{ types.NetworkConnect }
+}
+
+// Network disconnect
+// swagger:model NetworkDisconnectRequest
+type swagCompatNetworkDisconnectRequest struct {
+ // in:body
+ Body struct{ types.NetworkDisconnect }
+}