Charlie Henry

03/24/2023, 4:37 PM
Building off ☝️, I'm curious what people are using to organize blocks to make them less messy? We're using github storage so we usually have to make a new storage block for every feature branch we want to test before merging to production, so things get crufty over time.

Henning Holgersen

03/24/2023, 5:27 PM
Ohhh… I hardly imagine how I would do it with GitHub storage. Perhaps some fancy GitHub actions to register blocks with the required branch name on push? My team uses azure storage (s3 but different), so defining those blocks is mostly a one-off job that requires a storage key secret and is OK to do manually. We do juggle some container images though, and I have just started porting those to be defined as code and run and updated in a sane way. So our repo with flows now has a “blocks” folder split into dev and prod. Because blocks are the one thing we do want to differ between environments - for instance using tagged images on prod but latest in dev.

Chris Reuter

03/24/2023, 6:18 PM
Another alternative is that today, you could isolate environments with workspaces. Sounds like that would be cost prohibitive if you have many different user-permission combinations. We do plan to add fine-grained object-oriented controls so as to accomplish user-level permissions for blocks in the future, but that is not something we're working on right now.

Charlie Henry

03/31/2023, 9:32 PM
Thanks for the responses y'all. Maybe the ability to add tags to blocks could help? Or folders to organize them?