Hi, I have been building a few things with ion this past week and it has been a wonderful experience.
Something I noticed looking through my S3 buckets was that there seems to be an sst-asset-[randomID] bucket which contains the code uploads for my deployments. However, it looks to me as though it is never deleting previous versions as I can see code archives all the way back to my first test, including many that have been fully overwritten. While the size of this bucket is still relatively manageable, I can see it starting to balloon as I continue to deploy if another 5-10MB is added there with every single update.
Is there a reason old instances aren't deleted, and is there a CLI command or project setting that could enable automatic deletions of old archived code assets? Would setting up my own lifecycle deletion policy be a good option?
Hi, I have been building a few things with ion this past week and it has been a wonderful experience.
Something I noticed looking through my S3 buckets was that there seems to be an
sst-asset-[randomID]
bucket which contains the code uploads for my deployments. However, it looks to me as though it is never deleting previous versions as I can see code archives all the way back to my first test, including many that have been fully overwritten. While the size of this bucket is still relatively manageable, I can see it starting to balloon as I continue to deploy if another 5-10MB is added there with every single update.Is there a reason old instances aren't deleted, and is there a CLI command or project setting that could enable automatic deletions of old archived code assets? Would setting up my own lifecycle deletion policy be a good option?
Thanks!