mik-laj commented on a change in pull request #10677:
URL: https://github.com/apache/airflow/pull/10677#discussion_r483280382
##########
File path: airflow/cli/cli_parser.py
##########
@@ -142,6 +142,10 @@ def positive_int(value):
("-e", "--end-date"),
help="Override end_date YYYY-MM-DD",
type=parsedate)
+ARG_OUTPUT_PATH = Arg(
+ ("-o", "--output-path",),
+ help="The output for generated yaml files",
+ default="/tmp/airflow_yaml_output/")
Review comment:
I understand the reasons, but I'm afraid it might be more difficult to
use because of this. It is common to save files in the current directory by
default. If the user wishes to write to tmp, he can execute the following
sequence of commands.
```bash
cd /tmp/
mkdir -p airflow_tmp
airflow dags generate_kubernetes_pod_yaml example_bash_operator
ls
```
If we save in / tmp / the user may feel confused. When I unpack or create a
file, it expects it to be visible after executing `` ls ''
```bash
cd ~
airflow dags generate_kubernetes_pod_yaml example_bash_operator
ls
# Generated files not visible.
```
In 2020, users have large enough hard drives that we do not have to worry
about saving too much data. I think their convenience and productivity are more
important.
----------------------------------------------------------------
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]
