You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The `date_demo` DAG can be started by moving the slider and trigger the DAG runs. The DAG itself can be inspected by clicking on it.
255
+
The `date_demo` DAG can be started by moving the slider and trigger the DAG runs.
256
+
The DAG itself can be inspected by clicking on it.
256
257
257
258
=== Inspect the DAG
258
259
259
-
The overview displays details about the DAG runs, durations and other metadata. The graph, code or events can be selected in the tabs for more details.
260
+
The overview displays details about the DAG runs, durations and other metadata.
261
+
The graph, code or events can be selected in the tabs for more details.
260
262
261
263
image::argo-cd-git-ops/airflow-dag-overview.png[]
262
264
@@ -271,8 +273,9 @@ In the logs, the output of the DAG is printed under a line containing `Output:`,
271
273
272
274
== Minio
273
275
274
-
Since the Airflow Kubernetes Executor will be deleted after its run, the logs are written to an S3 bucket. When accessing the logs via the Airflow webserver,
275
-
the logs are fetched from S3 instead of the (already deleted) executor pods. The Minio / S3 instance can be accessed via port-forward:
276
+
Since the Airflow Kubernetes Executor will be deleted after its run, the logs are written to an S3 bucket.
277
+
When accessing the logs via the Airflow webserver, the logs are fetched from S3 instead of the (already deleted) executor pods.
278
+
The Minio / S3 instance can be accessed via port-forward:
276
279
277
280
[source,console]
278
281
----
@@ -295,7 +298,7 @@ This demo illustrates the combination of ArgoCD and Stackable, using the full po
295
298
296
299
// TODO: extend...
297
300
298
-
As a last step, in order to synchronize changes made to manifests or secrets from the Git repository, the following paragraph demonstrates on how to run this demo on a forked GitHub repository.
301
+
The last step is to demonstrate synchronizing changes made to manifests or secrets from the Git repository (to do this the demo is run on a forked GitHub repository).
299
302
300
303
[#interact-with-git-repository]
301
304
== How to interact with ArgoCD, Airflow and the Git repository
0 commit comments