-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
[No merge] swagger: add missing parameters #9126
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: tmds The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Signed-off-by: Tom Deseyn <[email protected]>
87d537f
to
d0dcdf2
Compare
Well that certainly cannot be true as we create containers and build images in both the compat and libpod sides of the api. @jwhonce what do you make of this? |
AFAIK: The parameters are there, but not documented, so an API client made using the swagger can't access them. |
How do we proceed with this? A suggestion: can you go over this PR, and create specific issue(s) for adding the parameters and validating they work? I think it's important to add these parameters because without them some really basic operations are not exposed through the swagger. |
Aligning the swagger to the as-built code is always good. An audit of all the endpoints will take some time. After Podman v3.0 is released let's add a card to Jira (@tmds Our Jira instance will soon be public.) to do the audit and generate issues for the missing parameters. That is the pattern we've used in the past. Any objections? There are some issues with this PR regarding the references, once fixed I would merge. |
Friendly ping |
ping @jwhonce |
A friendly reminder that this PR had no activity for 30 days. |
// - in: query | ||
// name: one-shot | ||
// type: boolean | ||
// default: false |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See #10058
// - in: query | ||
// name: platform | ||
// description: Platform in the format os[/arch[/variant]] | ||
// type: string | ||
// default: "" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would expect this to be grouped with other query parameters.
See #10060
// - in: query | ||
// name: verbose | ||
// type: boolean | ||
// default: false | ||
// - in: query | ||
// name: scope | ||
// type: string |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See #10061
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please see issues. As they are resolved I would like to update those areas of the swagger.
@tmds I also agreed to some changes that do not require code changes rather they comment existing behavior. Would you want to provide those changes in a PR that I can get merged for you?
A friendly reminder that this PR had no activity for 30 days. |
@tmds Since this PR has not been touched in a couple of months, I am going to close, Please reopen if you want to continue to work on it. |
@jwhonce @baude this PR gives an overview of parameters which are missing in podman swagger compared to docker.
This PR isn't meant for merging. You can go over the parameters and see which you want to add, and which you won't support.