Configuring Integrations via code/settings (Infrastructure as Code type question).
I am getting my feet wet with Supabase and one of the areas I am starting to mess with are the integrations, however they don't survive database resets.
I understand I can create a migration to re-enable them but all of their settings have to be copied and maintained in seeds and even extra migrations that the integration "knows how to take care of"
For instance if I understand correctly, to get the queue installed through code I need a migration to enable the extension, then a migration to hand "roll" (or export) the current pgmq_public (which to be fair could change over time but this migration wouldn't know that. And then update the config.toml
Is there a pattern here or best practice for this that I am missing...I realize this is optimized for "not your problem Backend as a Service" but when we are self hosting (or in my case local dev in a container) understanding the right pattern here is critical for long term maintainability.
Thanks in advance.
I understand I can create a migration to re-enable them but all of their settings have to be copied and maintained in seeds and even extra migrations that the integration "knows how to take care of"
For instance if I understand correctly, to get the queue installed through code I need a migration to enable the extension, then a migration to hand "roll" (or export) the current pgmq_public (which to be fair could change over time but this migration wouldn't know that. And then update the config.toml
Is there a pattern here or best practice for this that I am missing...I realize this is optimized for "not your problem Backend as a Service" but when we are self hosting (or in my case local dev in a container) understanding the right pattern here is critical for long term maintainability.
Thanks in advance.
