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
Is your feature request related to a problem? Please describe
If we strip both @SUMMONENVFILE and the proposed @SUMMONDOCKERARGSwe see that at the core they use the list of summon injected envvar names. If you know that the envvars that summon injected are A, B and C, then the rest can be done in bash or otherwise with relative ease.
This allows us to not build special cases into Summon. Instead we provide primitives to accommodate such cases and beyond.
Describe the solution you would like
Perhaps Summon injects a special environment variable called SUMMONVARNAMES or has a substitution variable similar to @SUMMONENVFILE called @SUMMONVARNAMES.
Describe alternatives you have considered
N/A
Additional context
N/A
The text was updated successfully, but these errors were encountered:
Maybe having a json output using a magic string (@SUMMONENVJSON or anything else) would do the trick.
This output could be easily formatted with any external tool.
Is your feature request related to a problem? Please describe
If we strip both
@SUMMONENVFILE
and the proposed@SUMMONDOCKERARGS
we see that at the core they use the list of summon injected envvar names. If you know that the envvars that summon injected are A, B and C, then the rest can be done in bash or otherwise with relative ease.This allows us to not build special cases into Summon. Instead we provide primitives to accommodate such cases and beyond.
Describe the solution you would like
Perhaps Summon injects a special environment variable called
SUMMONVARNAMES
or has a substitution variable similar to@SUMMONENVFILE
called@SUMMONVARNAMES
.Describe alternatives you have considered
N/A
Additional context
N/A
The text was updated successfully, but these errors were encountered: