Skip to content

Add Swagger UI with versioned REST API spec #117

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

Open
antoinemzs opened this issue Mar 3, 2025 · 0 comments · May be fixed by #116
Open

Add Swagger UI with versioned REST API spec #117

antoinemzs opened this issue Mar 3, 2025 · 0 comments · May be fixed by #116
Assignees
Labels
documentation Improvements or additions to documentation
Milestone

Comments

@antoinemzs
Copy link
Contributor

antoinemzs commented Mar 3, 2025

Pitch

Summary

There should be a place, unrelated to a running OpenBAS instance, to expose a nice Swagger UI with the correct version of the API spec (relative to the version selector on the docs page header).

Business benefit

  • Community engagement: easy way to point to specific bits of API specs and for community members to explore the API for possible devs
  • Docs completeness: there is a need from other places in the greater Filigran documentation corpus to refer to the API specs; e.g. from the PyOBAS docs

Limits and no go

  • Swagger UI should be static and embedded in the docs repository bundle. It should not be dependent on a running OpenBAS server.
  • The default Swagger UI theme is what it is and does not conform to the rest of the docs website theme. No effort proposed to improve this.
  • Care from individual developers should be given to keep the static API specs file in sync with the version selector (i.e. latest patch-version Z in a given X.Y.Z version) whenever there is a release (addition to release process).

Example PoC

Image

cc @jborozco @EllynBsc @RomuDeuxfois @Dimfacion @guillaumejparis

@antoinemzs antoinemzs added the documentation Improvements or additions to documentation label Mar 3, 2025
@antoinemzs antoinemzs linked a pull request Mar 3, 2025 that will close this issue
@antoinemzs antoinemzs linked a pull request Mar 3, 2025 that will close this issue
@antoinemzs antoinemzs self-assigned this Mar 3, 2025
@jborozco jborozco added this to the Bugs backlog milestone Apr 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants