Hello, I would either create subclass `MyDAG(DAG)` which validates the dag_id in init or use cluster policy to validate it (but this may create too many errors). Eventually, you can create test that loads all your dags and checks the dag_id. Such test can be run on your CI or before deploying a DAG to production.
Best, Tomek On Mon, Sep 21, 2020 at 10:14 AM Vasundhara Auvti < [email protected]> wrote: > Need help to enforce naming restriction on DAG_ID , i.e. to ensure the > dag_id are following standard naming conventions. such as > DAG_1234_5678_somename. > > All airflow users not allowed to create DAG's apart from above convention. > > Thanks >
