Configure different connection strings for the migration job to the openfga pod?

[danielloader]

I've been seeing some intermittent migration issues when using a pooled (pgbouncer) connection, and the neon.tech documentation advises against using a pooled connection for the bouncer where possible unless sure the migration tooling is tolerant of it.

Would it be possible to a) make the key in the secret configurable rather than being fixed to "uri" and b) set which key (and or secret name) for both openfga and the migration tooling?

Related:

• https://neon.tech/docs/connect/connection-pooling#connection-pooling-with-schema-migration-tools
• Error while migrating pressly/goose#613