GitHub user mattcasters added a comment to the discussion: Dynamic variables
So yes, people find interesting ways to resolve the variables needed in a
project.
Given the recursive nature of variable resolution, you could think of the
different environments:
* Development: `${PASSWORD}` resolves to value `abcd` in a config file, for a
MySQL database on your laptop.
* Production: `${PASSWORD}` resolves to `#{AzureVault:MySQLPassword}` (in a
config file) which then uses an Azure Key Vault variable resolver to look up
the password to a MySQL database running in the cloud somewhere.
Another obvious example are JSON Web Tokens where you first have to get a JWT
from a webservice to be able to re-use that in the rest of a pipeline or
workflow. It's possible to do this in a workflow but it's cleaner if we could
build a JWT Variable Resolver for this of some kind.
What I tried to do now is start with the Pipeline Variable Resolver since it
allows for many of the same things as a PoC.
These variable resolver plugins can be as simple as a single class file in the
various plugin sections to get them to work, plus some library dependencies.
I'll try to add a few other examples to the PR.
Cheers!
GitHub link:
https://github.com/apache/hop/discussions/4763#discussioncomment-11761642
----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to: [email protected]
