-
Notifications
You must be signed in to change notification settings - Fork 325
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
internal endpoints swagger additional endpoints #3007
internal endpoints swagger additional endpoints #3007
Conversation
4dafe4c
to
161475e
Compare
2950e48
to
4eba89f
Compare
Start the ToSchema party with brig and cannon Remove unnecessary module qualifier Fix type error Fix Create instance `ToSchema List1` Add swagger tags (resulting in sections) Replace over with %~ Introduce SwaggerTag combinator Use lens Add some documentation text Test RawJson FromJSON/ToJSON Cleanup Delete unused endpoint Align title with cannon's swagger title Delete Won't-do ToDos Add changelog Remove superfluous comment Add docs about Swagger Describe the swagger URL pattern better Use versions in swagger endpoint Update docs Move example section Fix typo Update swagger.md Old Swagger is now gone. Update services/brig/src/Brig/API/Public.hs Co-authored-by: fisx <mf@zerobuzz.net> Update services/brig/docs/swagger-internal-endpoints.md Co-authored-by: fisx <mf@zerobuzz.net> Update changelog.d/2-features/internal-endpoints-swagger Co-authored-by: fisx <mf@zerobuzz.net> Update libs/wire-api/src/Wire/API/SwaggerServant.hs Co-authored-by: fisx <mf@zerobuzz.net> Update libs/wire-api/test/unit/Test/Wire/API/Roundtrip/Aeson.hs Co-authored-by: fisx <mf@zerobuzz.net> Remove redundant constraint Simplify operations tagging with allOperations Traversal Use LText as data store of RawJson Replace ToSchema instance with function Increase lazy-ness of ToSchema RawJson instance Remove ToSchema for internal data structures Swagger docs for internal endpoints of Legalhold and Cargohold Move galley's internal endpoint to wire-api Swagger for internal Galley endpoints Add spar's internal endpoints
f59abbf
to
13e157a
Compare
Displayed paths are prefixed by the service name (e.g. `/<brig>`). This is | ||
necessary because Swagger does not expect more than one endpoint for a given | ||
path and method. Though, some paths (e.g. `/i/status`) exist on more than one | ||
service. To use the a path, remove the prefix. |
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.
Alternatively, we could expose the internal swagger UI for each service on their own page?
Is it possible to use the swagger UI to call those endpoints, the way it is implemented now?
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.
Thanks for the inspiration! I was more focused on the overview over all endpoints. However, being able to use the endpoints is pretty appealing, too.
As this should be possible with a kubectl port-forward
, I'll give it a shot.
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.
maybe different PR, though?
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.
maybe different PR, though?
@fisx , Sounds good 👍
This adds internal Servant endpoints to the Swagger docs for internal endpoints. (
brig
andcannon
endpoints were already there.)To have them available I had to move some types from
galley-types
towire-api
.spar
andgalley
internal API definitions haven been moved there, too.Follow up to #3003
Rendered
Checklist
changelog.d