I am trying to figure out how to provide plugin configuration dynamically and @douwe_maan gave me this great suggestion of passing them down as Environment variables while invoking the plugin. While this works great for one-time invocation of

meltano elt

, I run into a difficult while scheduling. If I

meltano schedule add

and then run the schedule later with

meltano schedule run

, I need to provide the environment variables during the run. I assume this can become a problem if I use an orchestrator. Is there any tips for "freezing" the config while creating the schedule so that it can be freely invoked by the orchestrator or CLI without worrying about providing config at that point?