Thanks for the quick reply, Richard. While the proposed solution would work, there are a few gotchas: 1. We're running Talend in the cloud, so an OS-level context variable I don't think would apply here. (Nor would it be accessible? Unless I'm mis-understanding something.. I'm a total noob to Talend) 2.If we were running all of our jobs locally at the server level, some of our servers are clustered, running multiple instances. Setting an OS level environment variable can only be done once, even if there are instances running multiple environments. (eg: DEV / UAT) As I'm typing this I'm wondering if it's a better idea to create a blank reference job with a given set of job contexts, then, create joblets as connectors to various platforms: ie: a joblet to connect to Salesforce, another to Netsuite, etc...The joblets will be tasked with getting context key/value data based on the current job context, with the parent reference job inheriting the joblet context vars. Interested to know your thoughts on this approach. Having a fair amount of experience in SSIS I am acutely familiar with the pain of having to go back and re-factor hundreds of packages because of poor design/implementation so naturally I want to avoid that situation. :-)
... View more
I want to create a Reference job that can be auto-populated with new or updated job contexts. A typical job context can be something like "DEV, "UAT", "PROD". But let's say down the road I want to add another job context called "PREPROD". My goal is to simply add this new job context to a database table, and when the job loads, the new job context becomes visible. Can this be done, and if so... how?
... View more