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
During S3 static site deploys using the custom CloudFormation resource, files are only ever uploaded, never deleted. If a previous deploy included a file that no longer exist in the deployable archive, it will remain in S3 after the deploy. s3 sync has a -delete flag that handles this, so looking at how that is implemented could provide good leads on how to correct this using boto.
The text was updated successfully, but these errors were encountered:
During S3 static site deploys using the custom CloudFormation resource, files are only ever uploaded, never deleted. If a previous deploy included a file that no longer exist in the deployable archive, it will remain in S3 after the deploy.
s3 sync
has a-delete
flag that handles this, so looking at how that is implemented could provide good leads on how to correct this using boto.The text was updated successfully, but these errors were encountered: