lloesche

6 ms·

1. 1.▲
   by lloesche 2y ago

   Neat! Done. Thank you! I also removed the old lambda based callback template from the repo. We're now using an SNS topic as part of a CustomFunction, to know when a user has deployed the stack ( https://github.com/someen
2. 2.▲
   by lloesche 2y ago

   We're currently working on Azure, but it's not stable enough to be listed here. > > AWS, Google Cloud, DigitalOcean, VMWare Vsphere, OneLogin, and Slack > kind of a weird mix of control planes :D agreed. Two of these thin
3. 3.▲
   by lloesche 2y ago

   The reasoning is explained in the very section of our Github org README you quoted this sentence from. Our main open source project is Fix Inventory ( https://github.com/someengineering/fixinventory ) and that is very we
4. 4.▲
   by lloesche 5y ago

   Like I wrote for us it was a one-off job to find and remove 6+ year old build artifacts that would never be needed again. I just looked for the cheapest solution of getting rid of them. I couldn't do it by prefix alone (prod files mixe
5. 5.▲
   by lloesche 5y ago

   I had a similar issue at my last job. Whenever a user created a PR on our open source project artifacts of 1GB size consisting of hundreds of small files would be created and uploaded to a bucket. There was just no process that would ever d