Put WARNING notice on DagProperties, move report query dicts out (!679) · Merge requests · repos / data-engineering / Airflow DAGs · GitLab

How to register an account on GitLab. Due to spam, new accounts are locked until approved by an admin or the approver bot. Your GitLab account gets automatically approved within one hour if you are a member of Trusted Contributors in Gerrit, or a member of the Trusted-Contributors group in Phabricator and linked your Developer account to your Phabricator account. If none of these apply, you can file an unlock request to expedite access.

Support: mw:GitLab, how to host a project on GitLab, #wikimedia-gitlab on libera.chat, #GitLab on Phabricator.

🚨THIS IS A REPLICA🚨 -- You probably want to use the production gitlab, https://gitlab.wikimedia.org. Data on this instance is likely to be overwritten at short notice. Login with hardware 2FA key does not work, please use one-time passwords.

Aleksandar Mastilovic requested to merge feature/Fix-DagProperties-in-Reports into main May 03, 2024

Put a WARNING notice on DagProperties objects in Python source code so that developers understand the mechanics and expectations of changing DagProperties variables in source code as opposed to UI
Move the queries objects out of DagProperties into common Python variables so that any changes made to them get reflected in the DAG with no need to reset the DAG properties in the UI