Skip to content

[placeholder] Web3Signer swagger-ui/internal openapi spec removal #873

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.

Sign up for GitHub

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

Jump to bottom
Open
usmansaleem opened this issue Aug 13, 2023 · 1 comment
Open

[placeholder] Web3Signer swagger-ui/internal openapi spec removal #873

usmansaleem opened this issue Aug 13, 2023 · 1 comment
Labels
snack Small coding task TeamCerberus Under active development by TeamCerberus @Consensys

Comments

@usmansaleem
Copy link
Collaborator

usmansaleem commented Aug 13, 2023 •
edited
Loading

The openapi spec has been moved to https://github.com/ethereum/remote-signing-api/. The web3signer should use the openapi spec (in its acceptance test) instead of the current internal version of openapi spec.

Also, w3s has a flag --swagger-ui-enabled (or similar), should be removed?

The openapi spec are also hosted at https://consensys.github.io/web3signer (the gh-pages branch).
@usmansaleem usmansaleem added the TeamCerberus Under active development by TeamCerberus @Consensys label Aug 13, 2023
@jframe jframe added the snack Small coding task label Oct 10, 2023
@jframe
Copy link
Contributor

jframe commented Jan 23, 2025

Alternatively update our open API spec to point to external open API specs for remote signing API, keymanager API and commit-boost API

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
snack Small coding task TeamCerberus Under active development by TeamCerberus @Consensys
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@usmansaleem @jframe