SLS will create a new cloudfront distribution even if one already exists for your lambda and error when associating it with a domain

[danjiro]

Describe the bug
You will get a CNAMEAlreadyExists: One or more of the CNAMEs you provided are already associated with a different resource. when you are doing a fresh deploy (one without the .serverless folder with existing config info) and the lambda already exists. Serverless docs say you shouldnt commit your .serverless folder but in this case you would have to or else it will create a new cloudfront distribution and try to assign that new one to your domain and you get the error. Normal SLS avoids these issues because it uses cloudformation?

[dphang]

I believe this plugin needs to use new version of Serverless Components: #415 (comment) to sync the state, though it needs to be upgraded as per the issue.

You can commit the .serverless folder each time but will be hard to manage while in a CI/CD pipeline, especially if you have multiple deployment stages (test, prod, etc.). If you have a single stage, you can do something like the following:

# Before running serverless fetch remotely stored folders
aws s3 sync "s3://my-serverless-state-bucket/my-component/${STAGE}/.serverless" .serverless

serverless

# After running serverless sync it's folders back to S3 bucket
aws s3 sync .serverless "s3://my-serverless-state-bucket/my-component/${STAGE}/.serverless"

This is the solution from: #328 (comment). If you have multiple stages it might be useful to create a custom deployment script that will sync to different S3 buckets/paths based on stage (you would also need to programmatically generate different serverless.yml files for each stage).

[ezalorsara]

I'm also in this situation having multi stages. I'm still thinking what the best approach to this Issue

[danjiro]

Syncing the .serverless folder to an s3 bucket looks like the best way to approach it.

…

On Tue, Aug 25, 2020 at 12:38 PM Joed Parin ***@***.***> wrote: I'm also in this situation having multi stages. I'm still thinking what the best approach to this Issue — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#554 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAFZ557GXN5VIXF7C5FNQYDSCMPZDANCNFSM4QFW6MKQ> .