Hey all, rookie here. What is the best practice for using blocks with varied teams? I have a very small team but an ultra rigid set of 'need to know' based access controls for things like docker images, code repositories, buckets/filesystems. I love the idea of reusable blocks but I'm apprehensive whether I can even use them in a workspace, it sort of feels like have a github repo with multiple .env files with keys that anyone can pull and use.
For something like a storage block that gives you access to an s3 bucket doesn't it basically circumvent all other access controls for all members of the workspace?
Does anyone have a pattern they're implementing that either allows for fine grained access control, or inherits existing auth mechanisms?
Bring your towel and join one of the fastest growing data communities. Welcome to our second-generation open source orchestration platform, a completely rethought approach to dataflow automation.