FR: Hoverctl Import Swagger Spec

[disfluxly]

Good Morning Hoverfly Team,

First, great product from what I've used so far.

I was wondering if there are any plans to incorporate into the Go CLI the ability to import a swagger spec. I know that you guys currently have a Java tool that does this, https://github.com/SpectoLabs/swagger-to-hoverfly, however, it looks like it's not being actively developed on and outputs v1 of the hoverfly template.

From a user perspective, this could be as simple as an additional flag in the import:

hoverctl import --swagger myspec.yml

But would also be beneficial as its own option to be able to export out the simulation json files. This way they can get combined with other specs in order to create a single sim file for all of an app's external dependencies.

hoverctl swagger myspec.yml > myspecsims.json

Right now the lack of this functionality is the primary piece of debate between using Hoverfly & Prism within my team. Let me know what you think.

Thanks!

[JohnFDavenport]

@disfluxly Feedback from Swagger users said we give it a GUI so we built a better converter into Hoverfly Cloud. You can edit the resulting simulation and also export the resulting simulation json from there.

[disfluxly]

@JohnFDavenport Thanks for the quick reply. For my use cases, it's significantly more effective to have developers running their own instance(s) of Hoverfly, which puts Hoverfly Cloud out of bounds. Are there any plans to incorporate the Swagger converter that's in Hoverfly Cloud to just Hoverfly?

[JohnFDavenport]

You can carry on running Hoverfly locally but use Hoverfly Cloud for import/export. I'd be really glad to have your feedback on where we should be going with our developments. You can contact me by looking up my profile.

[rsaccoll]

There really is not the possibility of a version update, at least in the project quoted? (https://github.com/SpectoLabs/swagger-to-hoverfly)

[JohnFDavenport]

@rsaccoll The swagger converter is written in Java and so we can't integrate that with Hoverfly as we'd risk comprising Hoverfly and making it bloatware. The best compromise we've come up with is to put the converter up on Hoverfly Cloud so you can import and export simulations, and edit the simulations there.