You can store secrets and parameters once in the LUSID Configuration Store and then securely pull information from this central repository in to any number of Scheduler jobs at runtime.
For example, if the code in your Docker image exercises a LUSID SDK, you could store your SDK authentication credentials in the Configuration Store, rather than hard-coding this sensitive information in the Docker image. See an example.
When you create a job, you have the option to pass environment variables into the job at runtime. The value of any environment variable you pass in can be pulled from the Configuration Store. See how to set this up.
Authorising the Configuration Store to act on your behalf
The very first time you create a job that pulls information in from the Configuration Store, you must perform a one-time operation to authorise the Configuration Store to 'run as you'. See how to do this.
You don't need to do this again, for any subsequent job.