diff options
| author | Jhon Honce <jhonce@redhat.com> | 2020-02-03 11:57:54 -0700 |
|---|---|---|
| committer | Jhon Honce <jhonce@redhat.com> | 2020-02-03 11:57:54 -0700 |
| commit | 4d301c8c4f3301bc99a55752b387ef4f7be9de5f (patch) | |
| tree | 1f78b3b4d59f661947fc012de503622c44bb556e /libpod/runtime_pod_infra_linux.go | |
| parent | 23f795786224c27f737e9043e9d513f54fa35ba8 (diff) | |
| download | podman-4d301c8c4f3301bc99a55752b387ef4f7be9de5f.tar.gz podman-4d301c8c4f3301bc99a55752b387ef4f7be9de5f.tar.bz2 podman-4d301c8c4f3301bc99a55752b387ef4f7be9de5f.zip | |
Update /_ping support
* Add swagger support and documentation
* Promote handler as there can only ever be one
* Update swagger tags
Between verbs and paths there are four endpoints for /_ping. I've
attempted to document them well without four copies of the details.
Time will tell.
Clients will use the headers `Libpod-API-Version` and
`Libpod-Buildha-Version` to determine if they are connecting to a Podman
service or some other compatible engine.
Client calls GET(/_ping):
* VARLINK engines will fail with error message
* Compatible engines will return 200 without Libpod headers
* Podman engines will return 200 and Libpod headers
Signed-off-by: Jhon Honce <jhonce@redhat.com>
Diffstat (limited to 'libpod/runtime_pod_infra_linux.go')
0 files changed, 0 insertions, 0 deletions