Hey everyone, I'm looking for a tool that would allow my team to validate that our service API is backwards compatible on each release. Something that we can plug into our release process, that would fail the build / test / deploy if there is a breaking change between the current and the previous "swagger.json" file. We give it two JSON files, and it returns a boolean: compatible or not (exit code 0 or not).
So far the only tool I found with such a feature is Swagger Diff, the Ruby version (https://github.com/civisanalytics/swagger-diff), however, it seems to miss certain breaking changes, and we have no expertise in Ruby to fix any bugs. We're Java-focused, and there is a Java version too (https://github.com/Sayi/swagger-diff), but that only generates a list of differences, it doesn't classify them as breaking vs. non-breaking. We may be able to build our own logic around that changelist, but I'd like to avoid reinventing the wheel if possible. Also, these projects don't seem to have a lot of activity (last commits 5+ months ago), not sure whether there's anyone actively maintaining them. What are others using for this purpose? Is there anything recommended by the Swagger community? Are there any plans for such a tool? I found a few others looking for the same thing, but no perfect solution yet: https://stackoverflow.com/questions/28098715/is-there-a-way-to-detect-when-a-swagger-changes https://github.com/OAI/OpenAPI-Specification/issues/233 Thanks, Denes -- You received this message because you are subscribed to the Google Groups "Swagger" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
