supabase local dev doesn't dump anything related to rbac

[MattpaulKing]

Hi thank you for setting this all up, it's a great package.

When I'm developing locally and I use supabase pull or try to dump the schema from my remote project, none of the modifications I've made to groups / group_users get dumped.

Do you have any insight into why this would be the case?

Thanks in advance

[point-source]

I'm not actually sure since I haven't used supabase pull. I have however used supabase db diff and that supposedly compares the remote schema to the local and looks for changes. When I do this, it also misses certain changes related to this package. It seems to be something related to the way supabase handles TLEs with respect to migrations.

Could you maybe describe the way you want this to work more specifically? Although there's likely not much I can do in this package to resolve it, it would help me open an upstream issue on the dbdev repo.

[MattpaulKing]

Thanks for taking the time to look into it.

So I've added a parent_id column for instance to the group_users table for groups of groups and changed the user_id to reference a different table.

Basically I'm just hoping to capture the state of the remote table(s) to my local instance when I do a pull.

This comes up for me quite a bit, because I do migration squashes so that my migrations folder isn't a zoo. But every time I squash my migrations, the changes I've made to the rbac tables aren't copied over.

No sweat about the package, I figured that it might be a supabase thing, I'll check out the diff command for now.

Thanks

[aplyd]

+1 also having issues with db pull not including tables made by this package (groups, group_users, etc.)

I had a similar issue with another dbdev package which caused me to remove it, as local development is rather important for me - but I'd like to continue using this if possible.

I understand it's an issue with dbdev but just wanted to join the conversation in case anyone knows of a solution.

[point-source]

I believe I have a solution for this as it relates to local dev. I will update the readme with a how-to

[elemdisc]

Just curious--did you write out the workaround or did I miss where it is?

I noticed this because I was trying to save out seed data as inserts using pg_dump.

[chriscdg]

Same question here, did you write a solution somewhere?

I just ran into this recently, I ended up using psql to grab it after struggling with this for some time. It would great to export normally with supabase cli or pg_dump!

[point-source]

I've opened a discussion about this here. I am considering migrating this project off of dbdev / tle and back to just standard migration files.

EDIT: As of version 5.2.0, this package ships with an install.sh script which can generate a migration file for install and for updates, just like dbdev but without the drawback of breaking schema dumps. Unfortunately, there isn't a clean migration path from dbdev-based install to install.sh based, but for future projects, this is fixed.