Frank Schmid

Hi @AnthonyWC , regarding the dash I can confirm that it is a bug in the alias plugin, because it does not use the Serverless function name transform. This has...

Yes, the order is important and defines the order of the hook executions, so the order in which the plugins are called. Regarding the dashes, there is a workaround: You...

Hi @anrocox , there is a general design problem of using aliases (the alias plugin) with shared API gateways. I elaborated on the topic in #79 and pointed out, why...

Fully agree. This is related to #11

First samples available here: https://github.com/HyperBrain/serverless-aws-alias-example (see README there). I will add some additional configs over time. So I'll keep this task open for now.

@mbruning24 This is a known issue. The problem here is, that Serverless creates the stage implicitly, i.e. it sets a stage name (string) in the CF deployment resource. That leads...

> What if you just errored out after analyzing and saw an existing stage already there and said something along the lines of "You have to delete or rename the...

Hi @cgrimal , if you do not set any of the throttling options, the limits are applied by AWS as mentioned in https://docs.aws.amazon.com/apigateway/latest/developerguide/api-gateway-request-throttling.html

I think so. If you do not add the settings, it should be equal to unchecking. Please let me know if you experienced a different behavior. You should see the...

Hi @pettyalex , thank you for the report. For me it looks like one of the plugins adds a resource that is not yet supported by the alias plugin. The...