[Runtimes] Adding a modifier and auto-mount option to configure multiple env variables #2276
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added a modifier function
set_env_variables
to add multiple env. variables to a runtime. Also added anenv
auto-mount option to use this function automatically. This can be used to mount an arbitrary set of env variables to every runtime in a project.While there are existing ways through MLRun/KFP-modifiers to add env. variables to runtimes, they have some short-comings, which this function solves:
RunConfig
which has an option to apply modifiers, but does not have ways to set env. variables on theRunConfig
itself. Also, since auto-mount option is available, it can be used for every job submitted without having to tweak theRunConfig
parametersfunction.apply(set_env_variables({"ENV1": "value1", "ENV2": "value2"}))
and can also do the same with:
function.apply(set_env_variables(ENV1="value1", ENV2="value2"))
The kwargs option is more limited and should be used for simple keys/values, while the dictionary option can be used for keys which do not pass as Python parameter names etc.