GitHub user mattcasters added a comment to the discussion: Dynamic variables

Absolutely @nadment. For now I've taken the `#{name:value}` format, but 
of-course the value can contain additional colons that you could work with, 
depending on what you want to achieve.  Extra arguments wouldn't be an issue.  
Personally I would put as many configuration options as I can in the metadata 
but we can't argue over preferences ;-)

In any case, my opinion is that the value of the secret (after lookup) is 
stored only in the transform or action when needed, not in the whole pipeline 
or workflow.  As such it feels more secure this way.  

GitHub link: 
https://github.com/apache/hop/discussions/4763#discussioncomment-11765865

----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to: [email protected]

Reply via email to