airflow dags list is not listing all the dags present in airflow home location

[MuthuVignesh91]

Apache Airflow version

Other Airflow 2 version (please specify below)

What happened

v2.0.2
When trying the "airflow dags list", via the aws mwaa API, we see that the list of dags we receive is not giving complete details.
I dont see any limit option to choose like list-jobs as well.
Unable to trace the exact reason why we are not able to see the complete list of dags.

What you think should happen instead

No response

How to reproduce

Just perform "airflow dags list" command when there are around 100+ dags in your airflow

Operating System

Amazon Linux

Versions of Apache Airflow Providers

No response

Deployment

Amazon (AWS) MWAA

Deployment details

No response

Anything else

No response

Are you willing to submit PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct

[boring-cyborg]

Thanks for opening your first issue here! Be sure to follow the issue template!

[josh-fell]

Hi @MuthuVignesh91, I cannot reproduce this on Airflow 2.5.1 nor 2.4.0.

DAG used:

from pendulum import datetime

from airflow.decorators import dag
from airflow.operators.empty import EmptyOperator


for i in range(200):

    @dag(dag_id=f"dag_{i}", start_date=datetime(2023, 1, 1), schedule=None)
    def _dag():
        EmptyOperator(task_id="empty")

    _dag()

DAGs in Airflow UI

Running airflow dags list

astro@d2c01fe9b20e:/usr/local/airflow$ airflow dags list | tail -n +3 | head -n -1 | wc -l
200

(^ Starting the count at line 3 since there are 2 header rows in the output and there is an empty line at the end.)

Is there always a consistent number of DAGs returned when running this against an MWAA environment? Also, can you try running airflow dags list on an environment with a more recent Airflow version too please?

[MuthuVignesh91]

Thanks for responding @josh-fell. I am using v2.0.2 for the same. Also I am using the managed version of airflow which is MWAA. Let me work with the AWS team and come back here if its an airflow issue or some kind of integration/config failure.

We could close this ticket for the moment. You can decide

p.s. Sorry for the delayed response

[josh-fell]

Sounds good. No problem to reopen later if needed.