-
Bug Report
-
Resolution: Fixed
-
L3 - Default
-
7.13.0
-
PROD
Expected Behavior
Downloading, opening and running the latest version of the swagger spec in OpenAPI tools such as Swagger UI or POSTMan should allow a user to make live calls to the engine REST API.
Actual Outcome
Because the swagger spec at v7.13.0 has errors in the URLs, a user cannot use OpenAPI tools such as Swagger UI or POSTMan to make live calls to certain endpoints.
Bug affects Swagger generated APIClients as well.
Steps to Reproduce
- Download the latest 7.13.0 community stand alone engine and start it on your localhost
- Download the latest 7.13.0 swagger jar, extract the swagger spec from it
- Open the Swagger Spec in Swagger UI or Swagger Editor
Notice the wrong /tenant/{teant-id}/ instead of /tenant-id/{tenant-id}/ in the URLs
Perhaps an easy unit test of the swagger spec would be to generate a Java API Client out of it using the Maven plugins from OpenAPI and then using Java Reflection to invoke each method to hit an instance of the engine REST API and make sure the URL exists. It would be okay to return a client error but not a 404.