Feature Request: Display env passed into ctx.run() when -e is used

[chrisc11]

I use invoke -e when adding new commands to make sure the right things are executing. Some commands rely on environmental overrides and change depending on the arguments added to the command.

For debug it would be useful if invoke -e (or another argument) could be used to echo the variables passed into env

[bitprophet]

This sounds like a reasonable enough request, thanks!

Not 100% sure how best to implement it; any solution needs to account for the default behavior of the env/update_env options, since the env handed to the subprocess runner will be a full copy of the invoking environment. Most folks' real shell environments are quite large.

Could simply be that we display only the value of env itself, and perhaps also the boolean value of update_env.

That said, this also smells like it may just fall under #15, re: having more granular logging. Right now we just have "no logging" or "full debug logging" (and of course -e which falls somewhere in the middle) and sometime I'd like to grow real warn, info, etc levels. For example, we could set it up such that the default level (which would be CRITICAL or WARN presumably) shows nothing, INFO level displays the command (like -e), and what the user supplied for env and update_env, and DEBUG causes display of the full actual env sent to the subprocess. That sort of thing.

[chrisc11]

Thanks! Yeah, I think I was most interested in displaying only the value of env itself as a way of validating that the task was setting the appropriate environment variables for the job. For this particular case, I was thinking dumping the info as part of -e made sense because the variables are part of what is needed to run the command correctly ... but in general I can see benefits for debug purposes with different levels of verbosity