I manage an on-premise installation, synced from github. We use resource files with exposed variables to manage connections from Retool to our database, without having to put the db credentials in version control. This is excellent!
I’m curious if there’s a way to use a
RETOOL_EXPOSED_... variable to substitute the value for
ssl in the resource yml. We’d like to have our production instance enforce SSL connections to our database, but allow our developers to run Retool locally without enforcing SSL (to their local dev db instances).
Example resource.yml to illustrate what I’m talking about:
name: Database type: mysql host: '%RETOOL_EXPOSED_DB_HOST%' port: '3306' databaseName: name databaseUsername: '%RETOOL_EXPOSED_DB_USER%' databasePassword: >- __RETOOL_ENCRYPTED__(...) ssl: %RETOOL_EXPOSED_DB_SSL% editPrivilege: false options: ...