set the channel topic: WireMock specifications working group: configuration files, Admin REST APIs, etc

FYI @Jamie Tanna [he/him] @Tom @mike waites specification WG placeholder, for all specs including the configuration files and admin REST APIs. Ideally, it would be great to align WireMock implementations overtime though the specs need to be extensible ◦ https://github.com/wiremock/ecosystem/issues/3 ◦ https://github.com/wiremock/ecosystem/issues/4

Initialized the repository for the specifications: https://github.com/wiremock/spec FYI @Stef Heyenrath @Tom Later I will replace WireMock.org one as a submodule

Next step is an entry for Testcontainers

FYI @Balog Tamás we had a sync with @Tom and agreed that https://github.com/wiremock/spec would become a source of truth for the specification. I will integrate the website and WireMock Java sources there, there are differences between them. Would you be able to start reporting gaps in that repo?

@Oleg Nenashev Alright. Yeah, I'll report them in the /spec repo then. Thanks for the heads-up.

FTR https://github.com/wiremock/wiremock/issues/2258

@Oleg Nenashev I created https://github.com/wiremock/spec/issues/3 for the schema gap analysis. I've covered only a part of the schema files because I'm not really familiar with those parts of WireMock, and I mentioned that in the issue as well. But later I can delve into them as well, and see what I can find.

I am currently looking into the specification gaps (an exploratory task). It looks like putting the WireMock Java specification to https://github.com/wiremock/spec would be a mistake at the moment, because there is a lot of evolution going on, and I would rather enforce Specification-as-Code with the spec being a part of the code repository. So I would propose that we.... 1. Move https://github.com/wiremock/wiremock/tree/master/src/main/resources/swagger to the root level of the repository (e.g.

/docs/spec

or

/spec

) 2. Declare the specification a source of truth for WireMock Java 3. Sync to other locations via submodules, maybe via intermediate repository or artifact WDYT @Balog Tamás @Stef Heyenrath @Tom?

@Tom Hi! Do we already have some metadata in the stub spec that allows to declare extensions (classnames or packages) needed for the stub definition to work? Conrtext: adding gRPC and GrapQL templates to the template library