Remove unused filter params from Swagger

Commit 745795ef2e added
a `filter` query-parameter to all "prune" endpoints,
however the parameter was only used when pruning
images.

This patch removes the filter parameter from the other
endpoints, given that it is not used for those, so
there is no reason documenting it.

Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
This commit is contained in:
Sebastiaan van Stijn 2017-05-04 14:25:01 -07:00
parent 9db03bd8cd
commit 2bdaab759f
No known key found for this signature in database
GPG key ID: 76698F39D527CE8C

View file

@ -4261,14 +4261,6 @@ paths:
produces:
- "application/json"
operationId: "ContainerPrune"
parameters:
- name: "filters"
in: "query"
description: |
Filters to process on the prune list, encoded as JSON (a `map[string][]string`).
Available filters:
type: "string"
responses:
200:
description: "No error"
@ -6036,14 +6028,6 @@ paths:
produces:
- "application/json"
operationId: "VolumePrune"
parameters:
- name: "filters"
in: "query"
description: |
Filters to process on the prune list, encoded as JSON (a `map[string][]string`).
Available filters:
type: "string"
responses:
200:
description: "No error"
@ -6392,14 +6376,6 @@ paths:
produces:
- "application/json"
operationId: "NetworkPrune"
parameters:
- name: "filters"
in: "query"
description: |
Filters to process on the prune list, encoded as JSON (a `map[string][]string`).
Available filters:
type: "string"
responses:
200:
description: "No error"