supabase
Hello im using buildship to make a cronJOb to my supabase DB so i can keep some reports.
I can already do it, but, I have to turn off the policies for it to work, Is there a way of creating a policy to allow the buildship to interact with it?
Solution:Jump to solution
Hi @pedro Along with the above resource you can refer to this to create RLS policies and connect with BuildShip - https://docs.buildship.com/tutorials/supabase-crud#supabase-row-level-security-rls.
Integrate Supabase DB with BuildShip – BuildShip
A unified resource to start building your backend with low-code. Dive into triggers, nodes, and step-by-step guidance to jumpstart your workflow creation.
3 Replies
To create a policy that allows BuildShip to interact with your Supabase database without turning off the policies, you need to define a Row Level Security (RLS) policy in Supabase that grants the necessary permissions to the BuildShip service.
Here's a general approach:
1. Identify the Role: Determine the role that BuildShip uses to connect to your Supabase database.
2. Create a Policy: Write an RLS policy that grants the required permissions (e.g., SELECT, INSERT, UPDATE) to the identified role.
3. Attach the Policy to the Table: Apply the policy to the relevant tables in your Supabase database.
Since this involves setting up policies in Supabase, please refer to the Supabase documentation on Row Level Security for detailed instructions on how to create and manage these policies.
If you need further assistance with specific steps or configurations within BuildShip, please submit your query via the in-app support button.
Row Level Security | Supabase Docs
Secure your data using Postgres Row Level Security.
Solution
Hi @pedro Along with the above resource you can refer to this to create RLS policies and connect with BuildShip - https://docs.buildship.com/tutorials/supabase-crud#supabase-row-level-security-rls.
Integrate Supabase DB with BuildShip – BuildShip
A unified resource to start building your backend with low-code. Dive into triggers, nodes, and step-by-step guidance to jumpstart your workflow creation.
I did read that 3 times 🙂 but was not obvious for me, i tought ANON was nos a secure Key