[AIRFLOW-6695] Add DAG run configuration to UI

[dacohen]

---

Issue link: AIRFLOW-6695

Make sure to mark the boxes below before creating PR: [x]

• Description above provides context of the change
• Commit message/PR title starts with [AIRFLOW-NNNN]. AIRFLOW-NNNN = JIRA ID^*
• Unit tests coverage for changes (not needed for documentation changes)
• Commits follow "How to write a good git commit message"
• Relevant documentation is updated including usage instructions.
• I will engage committers as explained in Contribution Workflow Example.

^* For document-only changes commit message can start with [AIRFLOW-XXXX].

---

In case of fundamental code change, Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in UPDATING.md.
Read the Pull Request Guidelines for more information.

[potiuk]

Please rebase to latest master @dacohen - we had a failing master drama and there is much higher chance the build will succeed. We have still some intermittent errors, but there should be less often.

[dacohen]

@potiuk Rebase is done. Let me know if you need anything else.

[potiuk]

I am not really experienced in that part of the code (UI)? I will let others take a look (@ashb /@kaxil @mik-laj ). ?

[ashb]

You haven't tested that a GET request shows the form -- could you please?

[codecov-io]

Codecov Report

Merging #7312 into master will increase coverage by 0.13%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #7312      +/-   ##
==========================================
+ Coverage   86.21%   86.35%   +0.13%     
==========================================
  Files         871      871              
  Lines       40570    40636      +66     
==========================================
+ Hits        34979    35091     +112     
+ Misses       5591     5545      -46

Impacted Files	Coverage Δ
airflow/www/views.py	76.22% <100%> (+0.14%)	⬆️
...viders/cncf/kubernetes/operators/kubernetes_pod.py	93.61% <0%> (-4.04%)	⬇️
...providers/google/cloud/example_dags/example_gcs.py	96.29% <0%> (-3.71%)	⬇️
airflow/www/app.py	94.24% <0%> (ø)	⬆️
...rflow/providers/mysql/operators/presto_to_mysql.py	100% <0%> (ø)	⬆️
...flow/providers/amazon/aws/hooks/cloud_formation.py	96.77% <0%> (ø)	⬆️
.../providers/amazon/aws/operators/cloud_formation.py	100% <0%> (ø)	⬆️
...ow/providers/amazon/aws/sensors/cloud_formation.py	100% <0%> (ø)	⬆️
airflow/utils/dag_processing.py	87.93% <0%> (ø)	⬆️
airflow/api/common/experimental/trigger_dag.py	98.07% <0%> (+0.11%)	⬆️
... and 10 more

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 92c72f4...ec3174d. Read the comment docs.

[ashb]

Could you also post a screenshot of what this new page looks like please?

[dacohen]

@ashb Made those changes. Here are screenshots of the page on first load, and after entering an invalid payload. Thanks again for your help on this!

[dacohen]

@ashb Updated again. New error screenshot attached.

[josh-gree]

Why was this not an optional screen!?

[kaxil]

Why was this not an optional screen!?

The number of clicks are the same to trigger any job, previously you had a prompt box on the same window, now you need to Trigger button on a different window -- that is the only difference. Would love to hear your use-case where you would like to have this optional.

[matthewpick]

Is there an easy way to view the Configuration for a DAG run after I click Trigger?
Sometimes I am uncertain how a specific DAG run was triggered (unless I look at the task logs).

[kaxil]

Is there an easy way to view the Configuration for a DAG run after I click Trigger?
Sometimes I am uncertain how a specific DAG run was triggered (unless I look at the task logs).

@matthewpick You can go Browse -> DagRun and check the conf column to view what you passed:

[matthewpick]

@kaxil I see! I had to enable RBAC to see the Conf column. We're good now 👍