Publish with profile based (JSON-Override) ODBC.ini

We load our ODBC.ini as a secret in the Workbench, depending on the AD group, via JSON override. That works great for the Workbench.
Publishing the same app as a Shiny app to Connect does not work this way.
What is the best practice to provide this ODBC connection to Connect? The data scientists do not know the passwords, so these should remain in a secret and not be entered later via environment variables.

It is actually described here: Creating a Shiny app that interacts with a database - Posit
But is there a more elegant solution? For example, passing the entire connection string to Connect?

Thank you in advance for your help.

BR, Arno

Hello Arno,

Thanks for getting in touch. Can you provide some more details about your current Workbench configuration, and what you're hoping to achieve in Connect? What is it about the environment variable approach that you find less than ideal?

Please consider filing this as a Support ticket so that we can gather more details about your setup in confidence and provide tailored assistance.

Best,
Chris