As you may have guessed from some from my posts on forum we are extensively into DB work.
For SQL Server we use your node (MSSQL Plus) and it fits our purpose perfectly (Thank You for this node.)
Recently as part of some work - we are now checking how to deploy flows across environments where the DB names etc. may differ.
1) We already allow go to flow post deployment to new env - and configure the credentials username/password which then gets used within flows.
2) In other cases - we need to handle everything as external properties and not touch the flows themselves post deployment. This is good. And even here we plan to use ENV variable approach supported by the node.
Challenge - sending Password as ENV variable may run into security risk. We need to set it in settings.js which is in readable format.
Is it possible to add some functionality to password field where we can call some JSONATA function aka - base64decode.
Or maybe some extensible in addition to JSONATA - so that even if we set it in settings.js in encoded form - then using some "callable" mechanism set in password field - the password gets decoded and used by the node.
Hi Steve,
As you may have guessed from some from my posts on forum we are extensively into DB work. For SQL Server we use your node (MSSQL Plus) and it fits our purpose perfectly (Thank You for this node.)
Recently as part of some work - we are now checking how to deploy flows across environments where the DB names etc. may differ. 1) We already allow go to flow post deployment to new env - and configure the credentials username/password which then gets used within flows. 2) In other cases - we need to handle everything as external properties and not touch the flows themselves post deployment. This is good. And even here we plan to use ENV variable approach supported by the node.
Challenge - sending Password as ENV variable may run into security risk. We need to set it in settings.js which is in readable format. Is it possible to add some functionality to password field where we can call some JSONATA function aka - base64decode. Or maybe some extensible in addition to JSONATA - so that even if we set it in settings.js in encoded form - then using some "callable" mechanism set in password field - the password gets decoded and used by the node.