oso
oso copied to clipboard
Create a way to use pyoso against producer trino
Currently, it's not simple to check for consistency issues with our producer trino cluster when we make changes to sqlmesh. We should make it possible for the internal team to point pyoso to producer trino instead of consumer trino (or something similar).
I'm guessing this is for global admins only?
See the admin table on Supabase