mattcasters commented on issue #3454:
URL: https://github.com/apache/hop/issues/3454#issuecomment-1846167277
@usbrandon Variable expressions are basically used to look up a value
somewhere. Setting a value in a Hop context can either be a clear text value
or indeed another variable
usbrandon commented on issue #3454:
URL: https://github.com/apache/hop/issues/3454#issuecomment-1846039103
Does this mean if we are setting a variable in a transform "Set Variables",
if we put ${AES:MY_STRING} that the step would interpret that to be "Use AES to
encrypt the string when
mattcasters commented on issue #3454:
URL: https://github.com/apache/hop/issues/3454#issuecomment-1831542631
The idea to have a new 'Lookup' plugin type in core is meant to allow all
plugins to contribute and use without too many class loader issues. It also
allows us to integrate with
mattcasters commented on issue #3454:
URL: https://github.com/apache/hop/issues/3454#issuecomment-1831533959
That doesn't mean the other ideas aren't valid. Working with a prefix does
show the intent of the variable replacement clearly. `${AES:SOME_SECRET}` is
pretty clear once you know
mattcasters commented on issue #3454:
URL: https://github.com/apache/hop/issues/3454#issuecomment-1825662116
Question remains that we need a place to store the environment configuration
metadata.
The project metadata isn't really a suited location for it. We probably
need a separate
mattcasters commented on issue #3454:
URL: https://github.com/apache/hop/issues/3454#issuecomment-1825647388
The counter argument that I saw was that in development you might just want
to use clear-text passwords and in production secrets are stored in a vault.
Mind you, I'm not opposed
