Changing lambda.layers from serverless gems breaks BasePathMapping

[jeremiahlukus]

Checklist

• Upgrade Jets: Are you using the latest version of Jets? This allows Jets to fix issues fast. There's a jets upgrade command that makes this a simple task. There's also an Upgrading Guide: http://rubyonjets.com/docs/upgrading/
• [ X] Reproducibility: Are you reporting a bug others will be able to reproduce and not asking a question. If you're unsure or want to ask a question, do so on https://community.boltops.com
• Code sample: Have you put together a code sample to reproduce the issue and make it available? Code samples help speed up fixes dramatically. If it's an easily reproducible issue, then code samples are not needed. If you're unsure, please include a code sample.

My Environment

Software	Version
Operating System
Jets	4.0.4
Ruby

---

Expected Behaviour

Able to switch lambda layers without deployment issues.

Current Behavior

If you deploy using serverless gems with a custom domain name then switch to use a custom lambda layer you get a failed deployment

was not successfully created: The following resource(s) failed to create: [BasePathMapping].

To deploy you have to remove the base path mapping, deploy, then add the domain mapping back then deploy again.

Step-by-step reproduction instructions

Code Sample

Solution Suggestion

[jeremiahlukus]

O its different than i thought

  # config.gems.disable = true 
  # config.lambda.layers = [   
  #   "arn:aws:lambda:us-east....,
  # ]

Adding this you are unable to do any domain mapping.

@tongueroo