Adaverse opened a new issue, #31605:
URL: https://github.com/apache/airflow/issues/31605

   ### Apache Airflow version
   
   2.6.1
   
   ### What happened
   
   When calling the API GET `dags/{dag_id}/details`, we get the following 
response - 
   ```
   {
     "catchup": false,
     "concurrency": 16,
     "dag_id": "tutorial",
     "dag_run_timeout": null,
     "default_view": "grid",
     "description": "A simple tutorial DAG",
     "doc_md": "\n    This is a documentation placed anywhere\n    ",
     "end_date": null,
     "file_token": 
"Ii9maWxlcy9kYWdzL3R1dG9yaWFsLnB5Ig.OOp1l6v5V9rSh-D0cJjLCb8XlHI",
     "fileloc": "/files/dags/tutorial.py",
     "is_active": true,
     "is_paused": false,
     "is_paused_upon_creation": null,
     "is_subdag": false,
     "last_parsed": "2023-05-30T04:47:57.735743+00:00",
     "max_active_runs": 16,
     "max_active_tasks": 16,
     "orientation": "LR",
     "owners": [
       "airflow"
     ],
     "params": {},
     "pickle_id": null,
     "render_template_as_native_obj": false,
     "schedule_interval": {
       "__type": "TimeDelta",
       "days": 1,
       "microseconds": 0,
       "seconds": 0
     },
     "start_date": "2021-01-01T00:00:00+00:00",
     "tags": [
       {
         "name": "example"
       }
     ],
     "timezone": "Timezone('UTC')"
   }
   ```
   
   
   ### What you think should happen instead
   
   Instead, it should have returned all the fields mentioned in the schema - 
   ```
   {
     "dag_id": "string",
     "default_view": "string",
     "description": "string",
     "file_token": "string",
     "fileloc": "string",
     "has_import_errors": true,
     "has_task_concurrency_limits": true,
     "is_active": true,
     "is_paused": true,
     "is_subdag": true,
     "last_expired": "2023-05-30T04:48:34.555Z",
     "last_parsed_time": "2023-05-30T04:48:34.555Z",
     "last_pickled": "2023-05-30T04:48:34.555Z",
     "max_active_runs": 0,
     "max_active_tasks": 0,
     "next_dagrun": "2023-05-30T04:48:34.555Z",
     "next_dagrun_create_after": "2023-05-30T04:48:34.555Z",
     "next_dagrun_data_interval_end": "2023-05-30T04:48:34.555Z",
     "next_dagrun_data_interval_start": "2023-05-30T04:48:34.555Z",
     "owners": [
       "string"
     ],
     "pickle_id": "string",
     "root_dag_id": "string",
     "schedule_interval": {
       "__type": "string",
       "days": 0,
       "microseconds": 0,
       "seconds": 0
     },
     "scheduler_lock": true,
     "tags": [
       {
         "name": "string"
       }
     ],
     "timetable_description": "string",
     "catchup": true,
     "concurrency": 0,
     "dag_run_timeout": {
       "__type": "string",
       "days": 0,
       "microseconds": 0,
       "seconds": 0
     },
     "doc_md": "string",
     "end_date": "2023-05-30T04:48:34.555Z",
     "is_paused_upon_creation": true,
     "last_parsed": "2023-05-30T04:48:34.555Z",
     "orientation": "string",
     "params": {},
     "render_template_as_native_obj": true,
     "start_date": "2023-05-30T04:48:34.555Z",
     "template_search_path": [
       "string"
     ],
     "timezone": "string"
   }
   ```
   
   I can see a lot of these missing fields being returned from `dags/{dag_id}`. 
Also, the model on which the response of the details endpoint is based on, 
contains all these fields. Hence, ideally, it should return all these fields 
either null or some value.
   
   ### How to reproduce
   
   Just call the above endpoint from the Swagger UI or any other means.
   
   ### Operating System
   
   Ubuntu (20.04.5 LTS (Focal Fossa))
   
   ### Versions of Apache Airflow Providers
   
   None
   
   ### Deployment
   
   Docker-Compose
   
   ### Deployment details
   
   _No response_
   
   ### Anything else
   
   _No response_
   
   ### Are you willing to submit PR?
   
   - [X] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of 
Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to