Swagger for Nameko @http entrypoints

Hi,

I got inspired by the Nameko/RabbitMQ/Flask/Swagger Microservices example
from Bruno Rocha's blog. I've been putting together some proof-of-concept
services using Nameko/RabbitMQ and am really very pleased with the
results. So thanks to everyone!

I've not yet introduced an http API to interrogate the services. In
Bruno's tutorial, Flask+Flasgger are used to create this. However, I'm
really interested in using Nameko's @http entrypoints. So, I'm wondering
-- is there a port of Swagger that works on Nameko's @http decorators?

Thanks for any comments,

Chris

Hey Chris,

Nameko HTTP is built on top of Werkzeug, which is the WSGI library that
sits under Flask, so it should be easy to do something very similar to
Flasgger.

There is an old thread that Bruno started when he wrote that blog post
where we discussed
it: https://groups.google.com/forum/#!msg/nameko-dev/QijBX_DMsJ8/PEGed_qkCAAJ

Post back here if you have questions!

Matt.

···

On Monday, December 18, 2017 at 11:36:18 AM UTC, Chris Platts wrote:

Hi,

I got inspired by the Nameko/RabbitMQ/Flask/Swagger Microservices example
from Bruno Rocha's blog. I've been putting together some proof-of-concept
services using Nameko/RabbitMQ and am really very pleased with the
results. So thanks to everyone!

I've not yet introduced an http API to interrogate the services. In
Bruno's tutorial, Flask+Flasgger are used to create this. However, I'm
really interested in using Nameko's @http entrypoints. So, I'm wondering
-- is there a port of Swagger that works on Nameko's @http decorators?

Thanks for any comments,

Chris

anybody got Flasgger’s Swagger object working wrapping it around get_wsgi_app() I tried that but it did not work as i expect from ProxyFix. I guess this is because Swagger() is not a middleware. Hope there are other solution out there.