Frank Schmid

Hi @lintaonz, thanks for the reproduction steps. I will check it and try to figure out what exactly happens there.

It is intended behavior, because the authorizer name must be unique, and a different alias can define the authorizer with different settings (not only a different target). E.g. you can...

The renaming is on purpose because authorizer X can be deployed to alias A1 with a different configuration than in alias A2. Imagine that you have a `stable` alias that...

@zachboyd Yes. They should be separate per alias deployment. I remember that I implemented it that way, but there might be a bug. I'll have to check.

This is how I would see the feature implemented and working ## Purpose In real-world scenarios alias deployments can be used to represent different quality stages that are deployed in...

Hi @cgrimal . Thanks for the ideas. Your approach with the aws cli sounds quite good as an intermediate workaround. For the roles, you might be able to enforce that...

No, if the role already exists, it should be sufficient to just reference it from the provider section.

`Error: spawn java ENOENT` That looks like the `java` executable could not be found. Can it be that dynamodb-local tries to start Java?

According to the [plugin requirements](https://github.com/99xt/serverless-dynamodb-local#this-plugin-requires) you need a JRE (I assume accessible through your path settings in the environment).

@btburton42 I only commented here as maintainer of `serverless-webpack` to add some thoughts to the issue 😄 . Originally @bebbi came up with the issue over there. @bebbi did you...