Nested ENV

[michaelr0]

Use Case (delete as appropriate): Using Portainer at Home

Have you reviewed our technical documentation and knowledge base? Yes (couldn't find anything)

Question:
Is it possible to use nested ENV properties? might be using the wrong term here
Basically I have a usecase where a bunch of common properties might exist on separate ENV keys and what I'd like to do is like what seems possible on a .env file (with docker-compose) is to nest the properties.

Example:

COMMON="common things and stuff"
THING="I like ${COMMON}"
OTHER="I also like ${COMMON}"

Which should be the same as specifing

THING="I like common things and stuff"
OTHER="I also like common things and stuff"

The particular usecase in this example is that I'm setting up https://github.com/ServerContainers/samba/blob/master/docker-compose.yml#L39 locally and I'd like to reduce the repeat need to specify guest ok = no; read only = no; browseable = yes across multiple shares, instead just referring to them via ${COMMON_OPTIONS}

Thanks.