brizzle
DTDrizzle Team
•Created by brizzle on 1/17/2025 in #help
Pull from an existing schema, but skip in migrations?
Hey all, I'm trying to do something a bit weird. I have a Keycloak instance that I am using to manage user identity, and have the schema stored in my postgres database in the "keycloak" schema. I would love to be able to reference user_entity ids in my public schema (managed by drizzle). I was able to (mostly) pull the keycloak schema using drizzle kit pull, but then, when I try to create migrations, it attempts to create all of the existing keycloak schema (which itself is managed by another migration tool).
Is there a way to pull in an existing schema, but to skip it when it comes to migrations?
Essentially, I just want to be able to build relations, and ideally create row-level security policies. thanks!
Is there a way to pull in an existing schema, but to skip it when it comes to migrations?
Essentially, I just want to be able to build relations, and ideally create row-level security policies. thanks!
2 replies