Summary

Currently Kong supports writing configuration in a file, in YAML or JSON.
To provide a more flexible configuration, especially for those running Kong in different environments (dev, staging, production), an option to write configuration in lua can be very useful.

Additional Details

There are many use-cases that come to mind:

• Using environment variables inside the d

The README at https://github.com/Miserlou/Zappa#custom-aws-iam-roles-and-policies-for-execution talks about using manage_roles: false to manually set a role for custom permissions.

This along with Miserlou/Zappa#244 led me down a rabbit hole.

However, if all you want to do is restrict the permissions of the Lambda itself, it seems that the partially documented `at

Prerequisites

• I am running the latest version. (up upgrade)
• I searched to see if the issue already exists.
• I inspected the verbose debug output with the -v, --verbose flag.
• Are you an Up Pro subscriber?

Description

It would be great to add regex capabilities to redirects like so:

redirects: {
  "/folder/:slug(regexhere)": {
    "location": "https

**Do you want to request a feature or report a bug?

Feature?

What is the current behavior?
Session object ACLs require both the key and the api_id field of the ACL definition to match.

If they mismatch the API does not throw an error.

What is the expected behavior?

The Gateway API should report the discrepancy to stop the token from being generated.

Expected Behavior / New Feature

As stated in the ReadMe, Ocelot depends on .net standard 2.0 and should be usable with full .net framework

Actual Behavior / Motivation for New Feature

Nuget states that Ocelot 14.0.9 depends on .net core 3.1

Hi,

It would great if there was documentation on the steps taken by sam build. My concrete use case is that I'd like to know how it finds and installs packages for Python Lambda functions so I can figure out the best way to structure my project. More specifically, does it just do a pip install -r and copies the source files or does it build my package with setuptools?

Thanks!

(Edit

we want to use swagger integrated with API document under aws-serverless-express framework, so any document/guideline to follow?
if we follow some code rule to define the API method then generate the API document and show in swagger it is perfect

In README.md there is the following command:

docker run --it  --name tgr -p 5000:5000 -e CLIENT_ID="xxxxxxx" -e CLIENT_SECRET="xxxxxxxxxxxxxxx" -e DEBUG="True" tgr

There is two issues with that:

1. It should be -it, rather than --it, since the first one is invalid
2. You also need to specify -e HOST="0.0.0.0" and -e PORT="5000" in order for the app to start.

Addi

The document at:

https://github.com/datawire/ambassador-docs/blob/master/user-guide/grpc.md

Mentions

$ docker run -p 50051:50051 <docker_reg>/grpc_example
Greeter client received: Hello, you!

in the section that talks about running the client. But this command is in fact for running the server.

Add a config option to specify host:post.
Currently one can only set the port via config option Port just for krakend to use this value as a string.

func NewServer(cfg config.ServiceConfig, handler http.Handler) *http.Server {
	return &http.Server{
		Addr:              fmt.Sprintf(":%d", cfg.Port),
                ...
	}
}

See https://github.com/devopsfaith/krakend/blob/m

Issue description

We don't have a CoC file yet, could anyone can help to create one?

Environment

None

Reference links:

• CoC of Apache

Is your feature request related to a problem? Please describe.
Currently, the guide https://spring.io/guides/gs/gateway/#_writing_tests suggest to use "WireMock from Spring Cloud Contract in order stand up a server".
Unit tests of the people using this library to make gateways would be more performant, easier to write and more stable if they didn't make real tcp connections to do http reques

virtual host options

If not for some particular exceptions, the status code returned from our WebAPI on error is always 500, regardless of the kind of error.

If an object already exists, for example, it should be returned as 409. If the object does not pass the schema validation, it should be a 415.

Go through the whole WebAPI and verify that the status codes are being returned correctly.

Hint: Error cl

Would love to know the QoS/RPS of this gateway. If you guys need help, I can have my team write something in locus. But if anyone has some reports on hardware => performance, would love to hear about it before making a decision on joining this community :).

I am interested in the possibilities of cloning my back end to handle more server load. I have seen multiple references to having those capabilities, but nothing concrete on what the options are, and how to set them up.

Would this be something you could write up a doc sub-page under Website Backends? (https://api-umbrella.readthedocs.io/en/latest/admin/website-backends.html)

An example of th

• Framework version: 1.4
• Implementations: Spring Boot 2

Scenario

Using SAM cli pass the alb request
sam local invoke -e alb-post.json

Here is the alb-post.json:
`{
"requestContext": {
"elb": {
"targetGroupArn": "arn:aws:elasticloadbalancing:us-east-2:123456789012:targetgroup/lambda-279XGJDqGZ5rsrHC2Fjr/49e9d65c45c6791a"
}
},
"httpMethod": "POST",
"path":

Feature Request

Hi Fusio is a great project! Many thanks for that!

I'm looking for a feature to export a existing API to a fusio.yml file, so you can deploy it easyly form your dev server to an production server.

Most thinks like Actions and Routes can be change on the UI. For beginners it is also easy to build a complete API only with the the UI.

As I have seen you can export the A

Describe the bug
When using [email protected], navigating to an invalid URL does not show the 404 error page. Instead, you see 200 | An unexpected error has occurred.

To Reproduce
Steps to reproduce the behavior:

1. Clone this repository: https://github.com/sidarthar/serverless-nextjs-404-error
2. Run npx serverless to deploy

sls invoke is useful for testing our API one request at a time.

It would be nice to spin up a local version of the API on localhost to enable us to develop our frontend apps against it, and to more easily run integration and E2E tests.

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and

I keep forgetting about this so writing it down here.

Looks like GitBook are archiving their legacy service on 30th April, meaning that it won't regenerate automatically for us any more (but will continue to be hosted).

Unfortunately, their new services does not appear to support Asciidoc for whatever reason, and we make extensive use of Asciidoc features throughout the documentation.