apache · potiuk · Mar 24, 2024 · Mar 24, 2024 · Mar 24, 2024 · Mar 24, 2024
diff --git a/airflow/example_dags/tutorial.py b/airflow/example_dags/tutorial.py
@@ -95,7 +95,7 @@
     You can document your task using the attributes `doc_md` (markdown),
     `doc` (plain text), `doc_rst`, `doc_json`, `doc_yaml` which gets
     rendered in the UI's Task Instance Details page.
-    ![img](http://montcs.bloomu.edu/~bobmon/Semesters/2012-01/491/import%20soul.png)
+    ![img](https://imgs.xkcd.com/comics/fixing_problems.png)
     **Image Credit:** Randall Munroe, [XKCD](https://xkcd.com/license.html)
     """
     )

diff --git a/docs/apache-airflow/core-concepts/dag-run.rst b/docs/apache-airflow/core-concepts/dag-run.rst
@@ -252,8 +252,16 @@ Using CLI
 Using UI
 ^^^^^^^^^^
 
+In the UI the parameters to trigger a DAG can be better represented via ``params`` definition as described in
+:ref:`concepts:params` documentation. Via defined params a proper form for value entry is rendered.
+
+If the DAG does not define ``params``the form is usually skipped, via the configuration option ``show_trigger_form_if_no_params``
+it is possible to force the display the classic form of a dict-only entry to pass configuration options.
+
 .. image:: ../img/example_passing_conf.png
 
+Please consider to convert such usage to ``params`` as this is the more convenient way and allows also validation of user input.
+
 To Keep in Mind
 ''''''''''''''''
 * Marking task instances as failed can be done through the UI. This can be used to stop running task instances.

diff --git a/docs/apache-airflow/img/add-dag-tags.png b/docs/apache-airflow/img/add-dag-tags.png
diff --git a/docs/apache-airflow/img/basic-dag.png b/docs/apache-airflow/img/basic-dag.png
diff --git a/docs/apache-airflow/img/branch_note.png b/docs/apache-airflow/img/branch_note.png
diff --git a/docs/apache-airflow/img/branch_with_trigger.png b/docs/apache-airflow/img/branch_with_trigger.png
diff --git a/docs/apache-airflow/img/branch_without_trigger.png b/docs/apache-airflow/img/branch_without_trigger.png
diff --git a/docs/apache-airflow/img/calendar.png b/docs/apache-airflow/img/calendar.png
diff --git a/docs/apache-airflow/img/change-site-title/default_instance_name_configuration.png b/docs/apache-airflow/img/change-site-title/default_instance_name_configuration.png
diff --git a/docs/apache-airflow/img/change-site-title/example_instance_name_configuration.png b/docs/apache-airflow/img/change-site-title/example_instance_name_configuration.png
diff --git a/docs/apache-airflow/img/change-ui-colors/dags-page-new.png b/docs/apache-airflow/img/change-ui-colors/dags-page-new.png
diff --git a/docs/apache-airflow/img/change-ui-colors/dags-page-old.png b/docs/apache-airflow/img/change-ui-colors/dags-page-old.png
diff --git a/docs/apache-airflow/img/change-ui-colors/graph-view-new.png b/docs/apache-airflow/img/change-ui-colors/graph-view-new.png
diff --git a/docs/apache-airflow/img/change-ui-colors/graph-view-old.png b/docs/apache-airflow/img/change-ui-colors/graph-view-old.png
diff --git a/docs/apache-airflow/img/change-ui-colors/tree-view-new.png b/docs/apache-airflow/img/change-ui-colors/tree-view-new.png
diff --git a/docs/apache-airflow/img/change-ui-colors/tree-view-old.png b/docs/apache-airflow/img/change-ui-colors/tree-view-old.png
diff --git a/docs/apache-airflow/img/context.png b/docs/apache-airflow/img/context.png
diff --git a/docs/apache-airflow/img/dag_doc.png b/docs/apache-airflow/img/dag_doc.png
diff --git a/docs/apache-airflow/img/edge_label_example.png b/docs/apache-airflow/img/edge_label_example.png
diff --git a/docs/apache-airflow/img/example_passing_conf.png b/docs/apache-airflow/img/example_passing_conf.png
diff --git a/docs/apache-airflow/img/latest_only_with_trigger.png b/docs/apache-airflow/img/latest_only_with_trigger.png
diff --git a/docs/apache-airflow/img/mapping-simple-graph.png b/docs/apache-airflow/img/mapping-simple-graph.png
diff --git a/docs/apache-airflow/img/mapping-simple-grid.png b/docs/apache-airflow/img/mapping-simple-grid.png
diff --git a/docs/apache-airflow/img/nested_branching.png b/docs/apache-airflow/img/nested_branching.png
diff --git a/docs/apache-airflow/img/scheduler_loop.jpg b/docs/apache-airflow/img/scheduler_loop.jpg
diff --git a/docs/apache-airflow/img/smart_sensor_architecture.png b/docs/apache-airflow/img/smart_sensor_architecture.png
diff --git a/docs/apache-airflow/img/smart_sensor_single_task_execute_flow.png b/docs/apache-airflow/img/smart_sensor_single_task_execute_flow.png
diff --git a/docs/apache-airflow/img/task_doc.png b/docs/apache-airflow/img/task_doc.png
diff --git a/docs/apache-airflow/img/tutorial-pipeline-1.png b/docs/apache-airflow/img/tutorial-pipeline-1.png
diff --git a/docs/apache-airflow/img/tutorial-pipeline-2.png b/docs/apache-airflow/img/tutorial-pipeline-2.png
diff --git a/docs/apache-airflow/img/ui-alert-message.png b/docs/apache-airflow/img/ui-alert-message.png
diff --git a/docs/apache-airflow/img/watcher.png b/docs/apache-airflow/img/watcher.png
diff --git a/docs/apache-airflow/tutorial/pipeline.rst b/docs/apache-airflow/tutorial/pipeline.rst
@@ -196,7 +196,7 @@ We've developed our tasks, now we need to wrap them in a DAG, which enables us t
 * only run once in the event that days are missed, and
 * timeout after 60 minutes
 
-And from the last line in the definition of the ``process-employees`` DAG, we see:
+And from the last line in the definition of the ``process_employees`` DAG, we see:
 
 .. code-block:: python
 
@@ -221,7 +221,7 @@ Putting all of the pieces together, we have our completed DAG.
 
 
   @dag(
-      dag_id="process-employees",
+      dag_id="process_employees",
       schedule_interval="0 0 * * *",
       start_date=pendulum.datetime(2021, 1, 1, tz="UTC"),
       catchup=False,
@@ -308,15 +308,15 @@ Putting all of the pieces together, we have our completed DAG.
 
   dag = ProcessEmployees()
 
-Save this code to a python file in the ``/dags`` folder (e.g. ``dags/process-employees.py``) and (after a `brief delay <https://airflow.apache.org/docs/apache-airflow/stable/configurations-ref.html#dag-dir-list-interval>`_), the ``process-employees`` DAG will be included in the list of available DAGs on the web UI.
+Save this code to a python file in the ``/dags`` folder (e.g. ``dags/process_employees.py``) and (after a `brief delay <https://airflow.apache.org/docs/apache-airflow/stable/configurations-ref.html#dag-dir-list-interval>`_), the ``process_employees`` DAG will be included in the list of available DAGs on the web UI.
 
 .. image:: ../img/tutorial-pipeline-1.png
 
-You can trigger the ``process-employees`` DAG by unpausing it (via the slider on the left end) and running it (via the Run button under **Actions**).
+You can trigger the ``process_employees`` DAG by unpausing it (via the slider on the left end) and running it (via the Run button under **Actions**).
 
 .. image:: ../img/tutorial-pipeline-2.png
 
-In the ``process-employees`` DAG's **Grid** view, we see all that all tasks ran successfully in all executed runs. Success!
+In the ``process_employees`` DAG's **Grid** view, we see all that all tasks ran successfully in all executed runs. Success!
 
 What's Next?
 -------------