Frank Schmid

see #83: the plugin is currently not compatible with the domain manager plugin

@pettyalex Thanks for the evaluation. Especially your last comment is very helpful. Do you have the versioning feature disabled in Serverless? I remember that the default was to create versions...

Bug, because it is not yet handled -> Feature, because the solution will/must lead to per-alias buckets if buckets emit S3 events. Otherwise an uncontrolled trigger of all deployed aliases...

@justinffs In general, the S3 triggers should be handled in the plugin in a similar way as the other event triggers (the code is located in the `stackOps` folder). I...

In the end we have to check if my comment above (https://github.com/HyperBrain/serverless-aws-alias/issues/73#issuecomment-330912022) is valid or not (the per alias bucket). Maybe it's not valid.

Can you give me more information about your service configuration? The alias plugin moves the APIG deployment to a separate stack (the alias stack). Can you check if there is...

Additionally you can use the `--verbose` switch, which will enable more detailed output, also for the alias plugin.

That looks indeed strange. The dependency array should never ever contain null values. Could you do come tests using my example repo (https://github.com/HyperBrain/serverless-aws-alias-example)?. A plain checkout and deploy of one...

@oleschaper Thank you for the files 👍 . I'll have a look and try to figure out, what exactly is missing in the plugin and if there's some edge case...

It seems the error is located here: ``` "UserGetLambdaPermissionApiGateway": { "Type": "AWS::Lambda::Permission", "Properties": { "FunctionName": {}, "Action": "lambda:InvokeFunction", "Principal": "apigateway.amazonaws.com", "SourceArn": { "Fn::Join": [ "", [ "arn:aws:execute-api:", { "Ref": "AWS::Region"...