We are planning to use self hosted version of Retool for internal app development . To avoid everytime adding the connection params in PostgresSQL database resource, we would like to deliver more smooth experience to Users by a readymade and pre-filled PostgresSQL Resource. The connection values will be hidden from the users. User exp will be like user can just select the resource and submit "create resource" and no need to provide any details. All the connection details will be handled under the hood in the application server level.
1 Like
In other words, I am looking for adding a custom resource on my self hosted Retool app.
Hey @dilip_chainani -
My read from your messages (but I might be wrong) - you want to add a 'template' style resource here with prefilled values / set up. Allowing some users to change only a couple of the configurations.
I don't think there is currently a way to create a resource 'template' to chose from.
If you are on enterprise, you can however use Retool API to programmatically interact with Retool resources. This means you could potentially have some sort of admin app that uses templated variables for creating resources?
I might be off from what you are trying to get at but I'm swinging none-the-less
Hello @dilip_chainani!
I believe that @JoeyKarczewski is correct, the closest thing to a customized resource that can currently be built is a REST API/GraphQL/SOAP Resource.
From your post, it sounds like you want to abstract away the use of the Postgres connection string needed to make a new resource from you app users. But this functionality might be currently possible, how many Postgres resources do you imagine your team will be creating and using?
Option 1: Managing a Few Postgres Instances
If you're working with one or a few Postgres instances, you would just set up a resource for each instance by providing its unique connection details. Users can then handle query creation, table selection, and other operations directly at the query level.
Option 2: Managing Many Postgres Instances
In your proposed custom resource creation feature, if you're planning to provide a dropdown near the "Create Resource" button, where users could select the desired Postgres instance from a list to create a resource, you’ll still need to define the connection details for the "selectable" option of the resources at least once.
Let me know if this helps!