Define a way to contribute environment variables to all the workspace POD containers

[davidfestal]

Is your feature request related to a problem? Please describe.

This feature was part of the devfile 1.0 plugin definitions (meta.yaml), and it would obviously be necessary in a number of use-cases.

Describe the solution you'd like

We would need a way in the Devfile 2.0 to declaratively add environment variables that would be added globally in the workspace, which means in all containers of the workspace POD.

Describe alternatives you've considered

Not aware about other ways to do the same thing.

[kadel]

How common is this use case?
If only 2% of users will ever do this Shouldn't be enough to just say that this is done by adding variables to all containers?

[elsony]

This requirement will be addressed by a more generic solution to provide a top-level attribute mechanism #239. Therefore, I am closing this off and this item is no longer a priority for 2.1.

[amisevsk]

This requirement will be addressed by a more generic solution to provide a top-level attribute mechanism #239. Therefore, I am closing this off and this item is no longer a priority for 2.1.

Worth noting that these are subtly different use cases -- global attributes are useful for defining string replacements within the devfile, but they cannot add environment variables where none exist. Global attributes wouldn't support the functionality David is describing.