Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

shouldrestart API missing from swagger file(s) #24985

Open
CheyenneWills opened this issue Jan 9, 2025 · 0 comments
Open

shouldrestart API missing from swagger file(s) #24985

CheyenneWills opened this issue Jan 9, 2025 · 0 comments
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@CheyenneWills
Copy link

Issue Description

Using the latest swagger yaml from https://docs.podman.io/en/latest/_static/api.html == > 'supports a RESTful API for the Libpod library (5.0.0)'

I'm working on a process that logs/audits the API calls and I'm using the latest swagger file to obtain a list of the different APIs. My code is a simple socket proxy that simply looks at the request, and reports the operationsID and description of the api obtained from swagger file. The code reads the swagger file to obtain information about the APIs.

Performing a simple:

podman -r -ti --rm debian ls -al 

My code shows the following:
POST HTTP/1.1 /v5.2.5/libpod/containers/{containerid}/shouldrestart
*** Was unable to find the api information for POST /v5.2.5/libpod/containers/{containerid}/shouldrestart
(with {containerid} replaced with actual container id).

A 'grep -i shouldrestart swagger-latest.yaml' doesn't find the string

Just to note that earlier versions of the podman command also use the shouldrestart api call

Steps to reproduce the issue

Steps to reproduce the issue

  1. grep -i shouldrestart swagger-latest.yaml

Describe the results you received

No string was found

Describe the results you expected

The swagger file should contain the information for the shouldrestart API call.

podman info output

N/A

Podman in a container

No

Privileged Or Rootless

None

Upstream Latest Release

Yes

Additional environment details

N/A

Additional information

No response

@CheyenneWills CheyenneWills added the kind/bug Categorizes issue or PR as related to a bug. label Jan 9, 2025
@CheyenneWills CheyenneWills marked this as a duplicate of #24986 Jan 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

No branches or pull requests

1 participant