Hey team,
If we wanted to set DB connection and store port in Environment variable it is impossible due to values being saved as strings.
This prevents us from protecting resources that have different ports or having to expose it.
Hey team,
If we wanted to set DB connection and store port in Environment variable it is impossible due to values being saved as strings.
This prevents us from protecting resources that have different ports or having to expose it.
Hi. Where are you trying access and use the port? In a query using javascript? if i was setting up postgres for instance, I would enter the port there
I was trying to use {{environment.variables.port}}
but that is always String so no way to hide it with variables.
I think you could convert it back to a number like this
{{ parseInt(environment.variables.port) }}
Function calling is not available on resource set-up.
I don't know a lot about resource setup. Maybe you could add a screenshot of where you are to help me understand?
Hi @stefancvrkotic, thanks for sharing this behavior. In case it helps, this bug affects {{ }}
expressions, but %RETOOL_EXPOSED_{NAME}%
references still work. Hope that helps!
I made a request for this and will let you know if there are any updates!
Support for this should be coming out in one of the next few releases!