Airflow task logging not printing correlation-id
Airflow task logs have correlation-id as None. Ideally this should be the correlation-id with which the workflow service run API is triggered.
Starting on April 8th, The Open Group will require Two Factor Authentication for all GitLab users. For instructions on setting up 2FA, see the Knowledge Article or GitLab Documentation. Note in particular that any HTTPS clones will require the use of a Personal Access Token (rather than a user’s password) once 2FA is enabled.
Airflow task logs have correlation-id as None. Ideally this should be the correlation-id with which the workflow service run API is triggered.