api-gateway-example | Boilerplate for tested NGINX API gateway | REST library

by nanit Ruby Version: Current License: No License

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | api-gateway-example Summary

api-gateway-example is a Ruby library typically used in Web Services, REST, Nginx applications. api-gateway-example has no bugs, it has no vulnerabilities and it has low support. You can download it from GitHub.

This repo is an example of how to create an NGINX proxy as a gateway to your micro services. There’s a [detailed blog post] about it. The important thing is that you can run tests to verify that the gateway routing is done correctly, meaning a request is routed to a specified service with a specified path. For example, you can verify that an HTTP call to is routed to your authentication service with the /login path.

Support

Quality

Security

License

Reuse

Support

api-gateway-example has a low active ecosystem.

It has 76 star(s) with 13 fork(s). There are 7 watchers for this library.

It had no major release in the last 6 months.

There are 1 open issues and 0 have been closed. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of api-gateway-example is current.

Quality

api-gateway-example has 0 bugs and 0 code smells.

Security

api-gateway-example has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

api-gateway-example code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

api-gateway-example does not have a standard license declared.

Check the repository for any license declaration and review the terms closely.

Without a license, all rights are reserved, and you cannot use the library in your applications.

Reuse

api-gateway-example releases are not available. You will need to build from source code and install.

Installation instructions are not available. Examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of api-gateway-example

Get all kandi verified functions for this library.

api-gateway-example Key Features

No Key Features are available at this moment for api-gateway-example.

api-gateway-example Examples and Code Snippets

No Code Snippets are available at this moment for api-gateway-example.

Community Discussions

Trending Discussions on api-gateway-example

Anyone here deployed Micronaut GraphQL API to AWS Lambda successfully?

QUESTION

Anyone here deployed Micronaut GraphQL API to AWS Lambda successfully?

Asked 2019-Nov-28 at 08:09

I created a GraphQL endpoint based on the following article: http://lifeinide.com/post/2019-04-15-micronaut-graphql-with-transaction-and-security-support/

It works properly in my local machine, but not after deploy to AWS lambda by referring to https://github.com/micronaut-projects/micronaut-aws/tree/master/examples/api-gateway-example.

I tested the /ping API of the Lambda with postman, it is working perfectly. However, when I post a graphql query to /graphql end point, it always return "415 Unsupported Media Type".

I think something is missing, but I not sure what is it, appreciate if anyone here could point me a way on how to make it works.

Thank you.

...

ANSWER

Answered 2019-Nov-28 at 08:09

After digging my head into source code, I found that graphQL post endpoint has Consumes property set to ALL i.e, / to accept any content type but in code they are specifically referring to application/json or application/graphQL.

When you hit the graphQL post endpoint with application/json then MICRONAUT lambda handler matches the content type with ALL, which is not true so it throws error 415 Unsupported Media Type. Request never reaches to the graphQL controller.

When you hit the graphQL post endpoint with / then MICRONAUT lambda handler matches the content type with ALL, which is seems to be true so it forward the request to GraphQL controller but in code it specifically looks for those specific content types. Again it relies on .equals method for comparison. Again it does not matches so throws 422 unprocessable entity.

I am still looking for solution to this.

Source https://stackoverflow.com/questions/58538624

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install api-gateway-example

You can download it from GitHub.
On a UNIX-like operating system, using your system’s package manager is easiest. However, the packaged Ruby version may not be the newest one. There is also an installer for Windows. Managers help you to switch between multiple Ruby versions on your system. Installers can be used to install a specific or multiple Ruby versions. Please refer ruby-lang.org for more information.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: