Hans Van Akelyen
Hans Van Akelyen
yup this isn't right.
was supposed to be #4327
This should be resolved in the latest builds https://github.com/apache/hop/pull/3787 You can test this by downloading a [development build]([here](https://repository.apache.org/content/repositories/snapshots/org/apache/hop/hop-client/2.9.0-SNAPSHOT/))
+1 on prefixing, at least for the provider (AES/ENCRYPTED/MYVAULT). As for the resolving of nested variables, I lean towards making the default way to handle variables and keep the syntax...
If we have variable nesting working your variable in the pipeline/database metadata can be ${MY_VARIABLE} and in the environment in development it would be "my cleartext password" in production it...
for example you can have a variable that is ${MY_VARIABLE} but that variable could be configured in the environment with a value of ${MY_OTHER_VARIABLE} which could then be specified in...
Then in this case it might be an error I introduced in the PROJECT_HOME extension point. I will take a look
should be solved in the near future by #3676
This has been resolved