Open myitcv opened 8 months ago
In the future this also enables adding cue env -w
, much like go env -w
, which I think has been helpful for portable scripting across OSes.
This would be useful when dynamically setting up a CI cache to store the contents of CUE_CACHE_DIR
. Currently I either have to set CUE_CACHE_DIR
explicitly, in the env (and cache that specific directory), or take a guess at the value that's being used by the command when setting up the CI cache.
As we add more environment variables it will be useful to unequivocally know what env is active during a CUE load/evaluation etc.
For example, as part of modules we added the flag
CUE_EXPERIMENT=modules
. Performance improvements via the evaluator will likely introduce more experiments, but alsoCUE_DEBUG
values.Go has
go env
for dumping useful effective environment information:"Effective" in so far as the value of a variable shown is the value after defaults etc have been applied.
We should add
cue env
in the same spirit, and also make the reporting of the value ofcue env
part of the GitHub bug report issue template.