Hi ,
Background :- We have multiple environments and we are developing flows and once the development finishes - we send them for QA. We are using ENV variables to set the config of MSSQL node - so that the DB connection can be defined per environment without having to touch the flow itself.
While deploying to each environment , while the process of deployment is automated - what we are finding is - every time someone needs to manually insert the user/password to the mssql contrib config node. This is even if the person needs to type in {{{user}}} and {{{pass}}} - variables defined in environment.
This then creates a situation
- The process is not automated. A manual intervention is required before the flow becomes usable.
- A person who knows the flow is needed. (Deployment folks do not know the details of the flows).
- If now the person makes an error then a new issue arises.... making the process error prone.
We would like - if the existing node - can be enhanced - where in if the user/pass is defined to take it from env - then during export these placeholders be maintained.
So if user was defined as {{{ENV_USER}}} and password as {{{ENV_PASS}}} - the export of that flow should contain {{{ ENV_USER}}} and {{{ENV_PASS}}}.
We do not want to export the actual credential/value of those variables as that would be a security breach and also against NR principles thereby defeating the concept of credential file.
Please suggest if this can be considered. Thanks.