You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
.env is a well-known format of describing environment variables. Support for this would greatly reduce the scripting overhead needed to run multiple plugins that share the same (or different) sets of environment variables. An option like --plugin-env-file could be used (similar to --plugin-env)
At runtime, sonobuoy could create a config map that will be added to the plugin pod's spec's env field.
Alternatively, sonobuoy could parse the content of the file and create environment entries on the Pod's spec like it currently does with --plugin-env
The text was updated successfully, but these errors were encountered:
.env
is a well-known format of describing environment variables. Support for this would greatly reduce the scripting overhead needed to run multiple plugins that share the same (or different) sets of environment variables. An option like--plugin-env-file
could be used (similar to--plugin-env
)At runtime, sonobuoy could create a config map that will be added to the plugin pod's spec's env field.
Alternatively, sonobuoy could parse the content of the file and create environment entries on the Pod's spec like it currently does with
--plugin-env
The text was updated successfully, but these errors were encountered: