potiuk edited a comment on issue #14198:
URL: https://github.com/apache/airflow/issues/14198#issuecomment-778856396
I am not sure this is a good candidate for UI feature in general.
This seems like such a low-level detail that you really need to know what
you are doing to make any use of this information. There are many more details
people might want to get in similar way - environment variables, packages
installed in the system etc. etc.
People already use "maintenance DAGs" for cleanups and a number of other
things. If you are are DAG writer (which I presume is the case looking at the
"users" of the features you mentioned) you can very easily create a few lines
Bash DAG that would provide the information if needed (and can be manually
triggered)
@naturalett -> would that be a good solution for you to write a manually
triggered DAG that would provide all information you need in the logs? For
example consider those three task that can be part of a DAG triggerable by
those who need them?
```
pip_task = BashOperator(
task_id="pip_task",
bash_command='pip freeze',
)
printenv_task = BashOperator(
task_id="printenv_task",
bash_command='printenv',
)
apt_task = BashOperator(
task_id="apt_task",
bash_command='apt list --installed',
)
```
We could even document it in our documentation as an example of what users
can do.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
