You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You have there a bucketsToCleanOnDeploy option which you can use with the "old" bucket name.
To prevent serverless-s3-sync plugin from conflicting with the cleaner plugin, I use sls remove --nos3sync option. Basically I let serverless-s3-sync to handle bucket updates, and the serverless-s3-cleaner to handle bucket cleanups.
If I rename my bucket in my serverless config, it fails to delete the previous bucket causing the deploy to fail.
For more context, I am creating the bucket in the serverless config as well.
Is this behavior intended? Is there anyway I can work around this? Thanks for any guidance!
The text was updated successfully, but these errors were encountered: