You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 21, 2023. It is now read-only.
Currently, one must enter their credentials into quay API Explorer to see the output of an endpoint. I'm not 100% comfortable entering my credentials there...
I'm only a little familiar with swagger, but it would be really nice to see some json or some indication of what the endpoints will output.
The text was updated successfully, but these errors were encountered:
Are you using Quay.io or Quay Enterprise? Are you running your own docs container?
I'm not 100% comfortable entering my credentials there...
The swagger page uses OAuth and client-side ajax requests to do everything. It's safe to enter your credentials as they'll only ever be on your machine.
Quay.io, not using the docs container. Yeah, I hear you.
It would be nice to be able to read what the output would be without having to trigger all of those conditionals, even just from a usability perspective and forgetting about security issues.
Swagger does support it but it requires having every API endpoint explicitly define the union of its various outputs, which is quite tedious to maintain. We'll give some more thought as to how we can go about doing so.
Currently, one must enter their credentials into quay API Explorer to see the output of an endpoint. I'm not 100% comfortable entering my credentials there...
I'm only a little familiar with swagger, but it would be really nice to see some json or some indication of what the endpoints will output.
The text was updated successfully, but these errors were encountered: