Skip to content
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 Specification for WireMock's standalone server Admin APIs #2

Open
oleg-nenashev opened this issue Apr 15, 2023 · 3 comments
Open
Labels
documentation Improvements or additions to documentation enhancement New feature or request

Comments

@oleg-nenashev
Copy link
Member

oleg-nenashev commented Apr 15, 2023

Proposal

There are many implementations of WireMock including the standalone server, and they have different REST APIs. It would be nice, in collaboration with maintainers of the implementations, to create an open specification within the WireMock organization that would be used as a recommended implementation of the interfaces.

Suggested implementation:

  • Standalone repository for the specification
  • SemVer versioning

Channel

  • #spec on WireMock Slack

If there are any existing implementations, prototypes, blogs or etc, let us know!

Reference any relevant documentation, other materials or issues/pull requests that can be used for inspiration.

@oleg-nenashev oleg-nenashev added enhancement New feature or request documentation Improvements or additions to documentation labels Apr 15, 2023
@oleg-nenashev oleg-nenashev transferred this issue from wiremock/ecosystem Jun 9, 2023
@oleg-nenashev
Copy link
Member Author

Created https://github.com/wiremock/spec as a foundation repository

@cezarypiatek
Copy link

I just wanted to use schema definition to generate C# client but it looks like the schema is incomplete.
For example, there's no schema definition for a response from __admin/requests https://github.com/wiremock/spec/blob/main/wiremock/wiremock-admin-api/wiremock-admin-api.yaml#L216

@oleg-nenashev can you provide the missing bits and pieces?

@oleg-nenashev
Copy link
Member Author

Yes, it needs to be updated for the recent version. Unfortunately I wasn't able to work on that before my vacation but I will revisit it in August

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 enhancement New feature or request
Projects
Development

No branches or pull requests

2 participants