Environment variables for a specific command about api HOT 8 CLOSED

@maysunfaisal Both

from api.

cc @johnmcollier @elsony

from api.

That would be very easy to do, model-wise, and quite consistent with the way environment is mentioned in other parts of the devfile (in container components for example).

from api.

Reviewed and approved

from api.

I am wondering what is the benefit of doing this way as opposed to having the ENV defined for the component container?

Also what happens if multiple commands are referencing the same component and require the same ENV? Will I need to mention it twice in the respective command? That seems redundant IMO..

from api.

@maysunfaisal This allows you to easily set variables for just one command, without needing to change the default value for the entire container, and to allow separate commands to have separate values for the same variable.

The environment variable value will only be set in the context of the command, and shouldn't conflict with other commands setting the same variable.

The example given in issue description is a good one, setting different values of JAVA_OPTS for each separate command as needed.

from api.

@johnmcollier will 2.0 spec support defining ENV on the component level as well or just on the command level?

from api.

Implemented

from api.