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
When using a ContainerSpec inside a pipeline, it would be useful to have the possibility to pass environment variables.
At the moment only command and args can be provided.
I want to run a pipeline where a user can submit the container image that shall be run. I want to provide some configuration values to the container but don't need to know the command. I would rather tell the user to use these environment values so that I am independent of different commands.
Is there a workaround currently?
At the moment, I pass the command and my parameters as arguments.
Love this idea? Give it a 👍.
The text was updated successfully, but these errors were encountered:
Feature Area
/area components
What feature would you like to see?
When using a
ContainerSpec
inside a pipeline, it would be useful to have the possibility to pass environment variables.At the moment only command and args can be provided.
What is the use case or pain point?
I want to run a pipeline where a user can submit the container image that shall be run. I want to provide some configuration values to the container but don't need to know the command. I would rather tell the user to use these environment values so that I am independent of different commands.
Is there a workaround currently?
At the moment, I pass the command and my parameters as arguments.
Love this idea? Give it a 👍.
The text was updated successfully, but these errors were encountered: