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
We've started using this great module more and more across our stacks.
But we now have a dozen S3 buckets all with just 1 zip file in and as we intent to use it even more it made me wonder about if it could be made to use a shared bucket? It's not a blocker, but we had to ask for our S3 bucket quota to be raised which made me ponder this.
If we looked into submitting a patch would you be interested in this?
The text was updated successfully, but these errors were encountered:
We've started using this great module more and more across our stacks.
Awesome 🙌
If we looked into submitting a patch would you be interested in this?
For sure. It was always a future thing. I didn't want to worry about possible zip conflicts on the first iteration. I think we can maybe completely prevent this with an object prefix based on the stack and resource name. Maybe even make that prefix be something the user can override.
We've started using this great module more and more across our stacks.
But we now have a dozen S3 buckets all with just 1 zip file in and as we intent to use it even more it made me wonder about if it could be made to use a shared bucket? It's not a blocker, but we had to ask for our S3 bucket quota to be raised which made me ponder this.
If we looked into submitting a patch would you be interested in this?
The text was updated successfully, but these errors were encountered: