You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by ho...@apache.org on 2021/12/02 19:17:19 UTC

[airflow-client-go] branch main updated: Update Go Client for Airflow 2.2.2 (#13)

This is an automated email from the ASF dual-hosted git repository.

houqp pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/airflow-client-go.git


The following commit(s) were added to refs/heads/main by this push:
     new b125451  Update Go Client for Airflow 2.2.2 (#13)
b125451 is described below

commit b125451e80fd4da7038ceaea7654c885d155fb46
Author: Adam Boscarino <ad...@bosco.codes>
AuthorDate: Thu Dec 2 14:17:15 2021 -0500

    Update Go Client for Airflow 2.2.2 (#13)
    
    * upgrade go client to latest api spec using openapi-generator 5.x
    * run pre-commit hook to add licenses
---
 airflow/.openapi-generator/FILES                   |   4 +
 airflow/README.md                                  |  12 +-
 airflow/api/openapi.yaml                           | 419 ++++++++++++++++++-
 airflow/api_config.go                              |   2 +-
 airflow/api_connection.go                          | 152 ++++++-
 airflow/api_dag.go                                 | 172 +++++++-
 airflow/api_dag_run.go                             | 161 +++++++-
 airflow/api_event_log.go                           |   2 +-
 airflow/api_import_error.go                        |   2 +-
 airflow/api_monitoring.go                          |   2 +-
 airflow/api_permission.go                          |   2 +-
 airflow/api_plugin.go                              |   2 +-
 airflow/api_pool.go                                |   2 +-
 airflow/api_provider.go                            |   2 +-
 airflow/api_role.go                                |   2 +-
 airflow/api_task_instance.go                       |   2 +-
 airflow/api_user.go                                | 447 ++++++++++++++++++++-
 airflow/api_variable.go                            |   2 +-
 airflow/api_x_com.go                               |   2 +-
 airflow/client.go                                  |   2 +-
 airflow/configuration.go                           |   2 +-
 airflow/docs/Connection.md                         |   2 +-
 airflow/docs/ConnectionAllOf.md                    |   2 +-
 airflow/docs/ConnectionApi.md                      |  65 +++
 airflow/docs/ConnectionTest.md                     | 101 +++++
 airflow/docs/DAGApi.md                             |  77 +++-
 airflow/docs/DAGRunApi.md                          |  76 ++++
 airflow/docs/Dag.md                                |  36 ++
 airflow/docs/DagDetail.md                          |  36 ++
 airflow/docs/DagRun.md                             |  60 ++-
 airflow/docs/DagState.md                           |   4 +-
 airflow/docs/TaskInstance.md                       |  12 +-
 airflow/docs/TaskState.md                          |   4 +
 airflow/docs/TriggerRule.md                        |   2 +
 airflow/docs/UpdateDagRunState.md                  |  75 ++++
 airflow/docs/User.md                               |   2 +-
 airflow/docs/UserApi.md                            | 205 ++++++++++
 airflow/docs/UserCollectionItem.md                 |   2 +-
 airflow/model_action.go                            |   2 +-
 airflow/model_action_collection.go                 |   2 +-
 airflow/model_action_collection_all_of.go          |   2 +-
 airflow/model_action_resource.go                   |   2 +-
 airflow/model_class_reference.go                   |   2 +-
 airflow/model_clear_task_instance.go               |   2 +-
 airflow/model_collection_info.go                   |   2 +-
 airflow/model_config.go                            |   2 +-
 airflow/model_config_option.go                     |   2 +-
 airflow/model_config_section.go                    |   2 +-
 airflow/model_connection.go                        |   4 +-
 airflow/model_connection_all_of.go                 |   4 +-
 airflow/model_connection_collection.go             |   2 +-
 airflow/model_connection_collection_all_of.go      |   2 +-
 airflow/model_connection_collection_item.go        |   2 +-
 ...atabase_status.go => model_connection_test_.go} |  92 +++--
 airflow/model_cron_expression.go                   |   2 +-
 airflow/model_dag.go                               |  49 ++-
 airflow/model_dag_collection.go                    |   2 +-
 airflow/model_dag_collection_all_of.go             |   2 +-
 airflow/model_dag_detail.go                        |  49 ++-
 airflow/model_dag_detail_all_of.go                 |   2 +-
 airflow/model_dag_run.go                           | 115 ++++--
 airflow/model_dag_run_collection.go                |   2 +-
 airflow/model_dag_run_collection_all_of.go         |   2 +-
 airflow/model_dag_state.go                         |   8 +-
 airflow/model_error.go                             |   2 +-
 airflow/model_event_log.go                         |   2 +-
 airflow/model_event_log_collection.go              |   2 +-
 airflow/model_event_log_collection_all_of.go       |   2 +-
 airflow/model_extra_link.go                        |   2 +-
 airflow/model_extra_link_collection.go             |   2 +-
 airflow/model_health_info.go                       |   2 +-
 airflow/model_health_status.go                     |   2 +-
 airflow/model_import_error.go                      |   2 +-
 airflow/model_import_error_collection.go           |   2 +-
 airflow/model_import_error_collection_all_of.go    |   2 +-
 airflow/model_inline_response_200.go               |   2 +-
 airflow/model_inline_response_200_1.go             |   2 +-
 airflow/model_list_dag_runs_form.go                |   2 +-
 airflow/model_list_task_instance_form.go           |   2 +-
 airflow/model_metadatabase_status.go               |   2 +-
 airflow/model_plugin_collection.go                 |   2 +-
 airflow/model_plugin_collection_all_of.go          |   2 +-
 airflow/model_plugin_collection_item.go            |   2 +-
 airflow/model_pool.go                              |   2 +-
 airflow/model_pool_collection.go                   |   2 +-
 airflow/model_pool_collection_all_of.go            |   2 +-
 airflow/model_provider.go                          |   2 +-
 airflow/model_provider_collection.go               |   2 +-
 airflow/model_relative_delta.go                    |   2 +-
 airflow/model_resource.go                          |   2 +-
 airflow/model_role.go                              |   2 +-
 airflow/model_role_collection.go                   |   2 +-
 airflow/model_role_collection_all_of.go            |   2 +-
 airflow/model_schedule_interval.go                 |   2 +-
 airflow/model_scheduler_status.go                  |   2 +-
 airflow/model_sla_miss.go                          |   2 +-
 airflow/model_tag.go                               |   2 +-
 airflow/model_task.go                              |   2 +-
 airflow/model_task_collection.go                   |   2 +-
 airflow/model_task_extra_links.go                  |   2 +-
 airflow/model_task_instance.go                     |  34 +-
 airflow/model_task_instance_collection.go          |   2 +-
 airflow/model_task_instance_collection_all_of.go   |   2 +-
 airflow/model_task_instance_reference.go           |   2 +-
 .../model_task_instance_reference_collection.go    |   2 +-
 airflow/model_task_state.go                        |   6 +-
 airflow/model_time_delta.go                        |   2 +-
 airflow/model_trigger_rule.go                      |   4 +-
 ...ble_all_of.go => model_update_dag_run_state.go} |  75 ++--
 airflow/model_update_task_instances_state.go       |   2 +-
 airflow/model_user.go                              |   2 +-
 airflow/model_user_all_of.go                       |   2 +-
 airflow/model_user_collection.go                   |   2 +-
 airflow/model_user_collection_all_of.go            |   2 +-
 airflow/model_user_collection_item.go              |   2 +-
 airflow/model_user_collection_item_roles.go        |   2 +-
 airflow/model_variable.go                          |   2 +-
 airflow/model_variable_all_of.go                   |   2 +-
 airflow/model_variable_collection.go               |   2 +-
 airflow/model_variable_collection_all_of.go        |   2 +-
 airflow/model_variable_collection_item.go          |   2 +-
 airflow/model_version_info.go                      |   2 +-
 airflow/model_weight_rule.go                       |   2 +-
 airflow/model_x_com.go                             |   2 +-
 airflow/model_x_com_all_of.go                      |   2 +-
 airflow/model_x_com_collection.go                  |   2 +-
 airflow/model_x_com_collection_all_of.go           |   2 +-
 airflow/model_x_com_collection_item.go             |   2 +-
 airflow/response.go                                |   2 +-
 airflow/utils.go                                   |   2 +-
 130 files changed, 2525 insertions(+), 233 deletions(-)

diff --git a/airflow/.openapi-generator/FILES b/airflow/.openapi-generator/FILES
index 7cdf523..84f9344 100644
--- a/airflow/.openapi-generator/FILES
+++ b/airflow/.openapi-generator/FILES
@@ -36,6 +36,7 @@ docs/ConnectionApi.md
 docs/ConnectionCollection.md
 docs/ConnectionCollectionAllOf.md
 docs/ConnectionCollectionItem.md
+docs/ConnectionTest.md
 docs/CronExpression.md
 docs/DAG.md
 docs/DAGApi.md
@@ -101,6 +102,7 @@ docs/TaskInstanceReferenceCollection.md
 docs/TaskState.md
 docs/TimeDelta.md
 docs/TriggerRule.md
+docs/UpdateDagRunState.md
 docs/UpdateTaskInstancesState.md
 docs/User.md
 docs/UserAllOf.md
@@ -140,6 +142,7 @@ model_connection_all_of.go
 model_connection_collection.go
 model_connection_collection_all_of.go
 model_connection_collection_item.go
+model_connection_test_.go
 model_cron_expression.go
 model_dag.go
 model_dag_collection.go
@@ -194,6 +197,7 @@ model_task_instance_reference_collection.go
 model_task_state.go
 model_time_delta.go
 model_trigger_rule.go
+model_update_dag_run_state.go
 model_update_task_instances_state.go
 model_user.go
 model_user_all_of.go
diff --git a/airflow/README.md b/airflow/README.md
index 3c8d439..606e16f 100644
--- a/airflow/README.md
+++ b/airflow/README.md
@@ -144,7 +144,7 @@ Note that you will need to pass credentials data.
 
 For e.g., here is how to pause a DAG with [curl](https://curl.haxx.se/), when basic authorization is used:
 ```bash
-curl -X POST 'https://example.com/api/v1/dags/{dag_id}?update_mask=is_paused' \\
+curl -X PATCH 'https://example.com/api/v1/dags/{dag_id}?update_mask=is_paused' \\
 -H 'Content-Type: application/json' \\
 --user \"username:password\" \\
 -d '{
@@ -229,7 +229,7 @@ server is unwilling to supply a default representation.
 ## AlreadyExists
 
 The request could not be completed due to a conflict with the current state of the target
-resource, meaning that the resource already exists
+resource, e.g. the resource it tries to create already exists.
 
 ## Unknown
 
@@ -320,6 +320,8 @@ Class | Method | HTTP request | Description
 *ConnectionApi* | [**GetConnections**](docs/ConnectionApi.md#getconnections) | **Get** /connections | List connections
 *ConnectionApi* | [**PatchConnection**](docs/ConnectionApi.md#patchconnection) | **Patch** /connections/{connection_id} | Update a connection
 *ConnectionApi* | [**PostConnection**](docs/ConnectionApi.md#postconnection) | **Post** /connections | Create a connection
+*ConnectionApi* | [**TestConnection**](docs/ConnectionApi.md#testconnection) | **Post** /connections/test | Test a connection
+*DAGApi* | [**DeleteDag**](docs/DAGApi.md#deletedag) | **Delete** /dags/{dag_id} | Delete a DAG
 *DAGApi* | [**GetDag**](docs/DAGApi.md#getdag) | **Get** /dags/{dag_id} | Get basic information about a DAG
 *DAGApi* | [**GetDagDetails**](docs/DAGApi.md#getdagdetails) | **Get** /dags/{dag_id}/details | Get a simplified representation of DAG
 *DAGApi* | [**GetDagSource**](docs/DAGApi.md#getdagsource) | **Get** /dagSources/{file_token} | Get a source code
@@ -334,6 +336,7 @@ Class | Method | HTTP request | Description
 *DAGRunApi* | [**GetDagRuns**](docs/DAGRunApi.md#getdagruns) | **Get** /dags/{dag_id}/dagRuns | List DAG runs
 *DAGRunApi* | [**GetDagRunsBatch**](docs/DAGRunApi.md#getdagrunsbatch) | **Post** /dags/~/dagRuns/list | List DAG runs (batch)
 *DAGRunApi* | [**PostDagRun**](docs/DAGRunApi.md#postdagrun) | **Post** /dags/{dag_id}/dagRuns | Trigger a new DAG run
+*DAGRunApi* | [**UpdateDagRunState**](docs/DAGRunApi.md#updatedagrunstate) | **Patch** /dags/{dag_id}/dagRuns/{dag_run_id} | Modify a DAG run
 *EventLogApi* | [**GetEventLog**](docs/EventLogApi.md#geteventlog) | **Get** /eventLogs/{event_log_id} | Get a log entry
 *EventLogApi* | [**GetEventLogs**](docs/EventLogApi.md#geteventlogs) | **Get** /eventLogs | List log entries
 *ImportErrorApi* | [**GetImportError**](docs/ImportErrorApi.md#getimporterror) | **Get** /importErrors/{import_error_id} | Get an import error
@@ -358,8 +361,11 @@ Class | Method | HTTP request | Description
 *TaskInstanceApi* | [**GetTaskInstance**](docs/TaskInstanceApi.md#gettaskinstance) | **Get** /dags/{dag_id}/dagRuns/{dag_run_id}/taskInstances/{task_id} | Get a task instance
 *TaskInstanceApi* | [**GetTaskInstances**](docs/TaskInstanceApi.md#gettaskinstances) | **Get** /dags/{dag_id}/dagRuns/{dag_run_id}/taskInstances | List task instances
 *TaskInstanceApi* | [**GetTaskInstancesBatch**](docs/TaskInstanceApi.md#gettaskinstancesbatch) | **Post** /dags/~/dagRuns/~/taskInstances/list | List task instances (batch)
+*UserApi* | [**DeleteUser**](docs/UserApi.md#deleteuser) | **Delete** /users/{username} | Delete a user
 *UserApi* | [**GetUser**](docs/UserApi.md#getuser) | **Get** /users/{username} | Get a user
 *UserApi* | [**GetUsers**](docs/UserApi.md#getusers) | **Get** /users | List users
+*UserApi* | [**PatchUser**](docs/UserApi.md#patchuser) | **Patch** /users/{username} | Update a user
+*UserApi* | [**PostUser**](docs/UserApi.md#postuser) | **Post** /users | Create a user
 *VariableApi* | [**DeleteVariable**](docs/VariableApi.md#deletevariable) | **Delete** /variables/{variable_key} | Delete a variable
 *VariableApi* | [**GetVariable**](docs/VariableApi.md#getvariable) | **Get** /variables/{variable_key} | Get a variable
 *VariableApi* | [**GetVariables**](docs/VariableApi.md#getvariables) | **Get** /variables | List variables
@@ -386,6 +392,7 @@ Class | Method | HTTP request | Description
  - [ConnectionCollection](docs/ConnectionCollection.md)
  - [ConnectionCollectionAllOf](docs/ConnectionCollectionAllOf.md)
  - [ConnectionCollectionItem](docs/ConnectionCollectionItem.md)
+ - [ConnectionTest](docs/ConnectionTest.md)
  - [CronExpression](docs/CronExpression.md)
  - [DAG](docs/DAG.md)
  - [DAGCollection](docs/DAGCollection.md)
@@ -440,6 +447,7 @@ Class | Method | HTTP request | Description
  - [TaskState](docs/TaskState.md)
  - [TimeDelta](docs/TimeDelta.md)
  - [TriggerRule](docs/TriggerRule.md)
+ - [UpdateDagRunState](docs/UpdateDagRunState.md)
  - [UpdateTaskInstancesState](docs/UpdateTaskInstancesState.md)
  - [User](docs/User.md)
  - [UserAllOf](docs/UserAllOf.md)
diff --git a/airflow/api/openapi.yaml b/airflow/api/openapi.yaml
index 8584173..6ff4b6d 100644
--- a/airflow/api/openapi.yaml
+++ b/airflow/api/openapi.yaml
@@ -147,7 +147,7 @@ info:
 
     For e.g., here is how to pause a DAG with [curl](https://curl.haxx.se/), when basic authorization is used:
     ```bash
-    curl -X POST 'https://example.com/api/v1/dags/{dag_id}?update_mask=is_paused' \
+    curl -X PATCH 'https://example.com/api/v1/dags/{dag_id}?update_mask=is_paused' \
     -H 'Content-Type: application/json' \
     --user "username:password" \
     -d '{
@@ -232,7 +232,7 @@ info:
     ## AlreadyExists
 
     The request could not be completed due to a conflict with the current state of the target
-    resource, meaning that the resource already exists
+    resource, e.g. the resource it tries to create already exists.
 
     ## Unknown
 
@@ -511,6 +511,51 @@ paths:
       tags:
       - Connection
       x-openapi-router-controller: airflow.api_connexion.endpoints.connection_endpoint
+  /connections/test:
+    post:
+      operationId: test_connection
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/Connection'
+        required: true
+      responses:
+        "200":
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/ConnectionTest'
+          description: Success.
+        "400":
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Client specified an invalid argument.
+        "401":
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Request not authenticated due to missing, invalid, authentication
+            info.
+        "403":
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Client does not have sufficient permission.
+        "404":
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: A specified resource is not found.
+      summary: Test a connection
+      tags:
+      - Connection
+      x-openapi-router-controller: airflow.api_connexion.endpoints.connection_endpoint
   /dags:
     get:
       operationId: get_dags
@@ -544,6 +589,25 @@ paths:
         schema:
           type: string
         style: form
+      - description: List of tags to filter results
+        explode: true
+        in: query
+        name: tags
+        required: false
+        schema:
+          items:
+            type: string
+          type: array
+        style: form
+      - description: Only return active DAGs.
+        explode: true
+        in: query
+        name: only_active
+        required: false
+        schema:
+          default: true
+          type: boolean
+        style: form
       responses:
         "200":
           content:
@@ -563,6 +627,57 @@ paths:
       - DAG
       x-openapi-router-controller: airflow.api_connexion.endpoints.dag_endpoint
   /dags/{dag_id}:
+    delete:
+      description: |
+        Deletes all metadata related to the DAG, including finished DAG Runs and Tasks. Logs are not deleted. This action cannot be undone.
+      operationId: delete_dag
+      parameters:
+      - description: The DAG ID.
+        explode: false
+        in: path
+        name: dag_id
+        required: true
+        schema:
+          type: string
+        style: simple
+      responses:
+        "204":
+          description: Success.
+        "400":
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Client specified an invalid argument.
+        "401":
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Request not authenticated due to missing, invalid, authentication
+            info.
+        "403":
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Client does not have sufficient permission.
+        "404":
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: A specified resource is not found.
+        "409":
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: An existing resource conflicts with the request.
+      summary: Delete a DAG
+      tags:
+      - DAG
+      x-openapi-router-controller: airflow.api_connexion.endpoints.dag_endpoint
     get:
       description: |
         Presents only information available in database (DAGModel).
@@ -943,7 +1058,7 @@ paths:
             application/json:
               schema:
                 $ref: '#/components/schemas/Error'
-          description: The resource that a client tried to create already exists.
+          description: An existing resource conflicts with the request.
         "403":
           content:
             application/json:
@@ -1102,6 +1217,68 @@ paths:
       tags:
       - DAGRun
       x-openapi-router-controller: airflow.api_connexion.endpoints.dag_run_endpoint
+    patch:
+      description: Modify a DAG run
+      operationId: update_dag_run_state
+      parameters:
+      - description: The DAG ID.
+        explode: false
+        in: path
+        name: dag_id
+        required: true
+        schema:
+          type: string
+        style: simple
+      - description: The DAG run ID.
+        explode: false
+        in: path
+        name: dag_run_id
+        required: true
+        schema:
+          type: string
+        style: simple
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/UpdateDagRunState'
+        required: true
+      responses:
+        "200":
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/DAGRun'
+          description: Success.
+        "400":
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Client specified an invalid argument.
+        "401":
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Request not authenticated due to missing, invalid, authentication
+            info.
+        "403":
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Client does not have sufficient permission.
+        "404":
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: A specified resource is not found.
+      summary: Modify a DAG run
+      tags:
+      - DAGRun
+      x-openapi-router-controller: airflow.api_connexion.endpoints.dag_run_endpoint
   /eventLogs:
     get:
       description: List log entries from event log.
@@ -1547,7 +1724,7 @@ paths:
             application/json:
               schema:
                 $ref: '#/components/schemas/Error'
-          description: The resource that a client tried to create already exists.
+          description: An existing resource conflicts with the request.
       summary: Update a pool
       tags:
       - Pool
@@ -3102,7 +3279,94 @@ paths:
       tags:
       - User
       x-openapi-router-controller: airflow.api_connexion.endpoints.user_endpoint
+    post:
+      operationId: post_user
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/User'
+        required: true
+      responses:
+        "200":
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/User'
+          description: Success.
+        "400":
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Client specified an invalid argument.
+        "401":
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Request not authenticated due to missing, invalid, authentication
+            info.
+        "403":
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Client does not have sufficient permission.
+        "409":
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: An existing resource conflicts with the request.
+      summary: Create a user
+      tags:
+      - User
+      x-openapi-router-controller: airflow.api_connexion.endpoints.user_endpoint
   /users/{username}:
+    delete:
+      operationId: delete_user
+      parameters:
+      - description: The username of the user
+        explode: false
+        in: path
+        name: username
+        required: true
+        schema:
+          type: string
+        style: simple
+      responses:
+        "204":
+          description: Success.
+        "400":
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Client specified an invalid argument.
+        "401":
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Request not authenticated due to missing, invalid, authentication
+            info.
+        "403":
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Client does not have sufficient permission.
+        "404":
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: A specified resource is not found.
+      summary: Delete a user
+      tags:
+      - User
+      x-openapi-router-controller: airflow.api_connexion.endpoints.user_endpoint
     get:
       operationId: get_user
       parameters:
@@ -3144,6 +3408,71 @@ paths:
       tags:
       - User
       x-openapi-router-controller: airflow.api_connexion.endpoints.user_endpoint
+    patch:
+      operationId: patch_user
+      parameters:
+      - description: The username of the user
+        explode: false
+        in: path
+        name: username
+        required: true
+        schema:
+          type: string
+        style: simple
+      - description: |
+          The fields to update on the resource. If absent or empty, all modifiable fields are updated.
+          A comma-separated list of fully qualified names of fields.
+        explode: false
+        in: query
+        name: update_mask
+        required: false
+        schema:
+          items:
+            type: string
+          type: array
+        style: form
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/User'
+        required: true
+      responses:
+        "200":
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Role'
+          description: Success.
+        "400":
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Client specified an invalid argument.
+        "401":
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Request not authenticated due to missing, invalid, authentication
+            info.
+        "403":
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: Client does not have sufficient permission.
+        "404":
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Error'
+          description: A specified resource is not found.
+      summary: Update a user
+      tags:
+      - User
+      x-openapi-router-controller: airflow.api_connexion.endpoints.user_endpoint
 components:
   callbacks: {}
   examples: {}
@@ -3439,6 +3768,17 @@ components:
           type: string
         type: array
       style: form
+    FilterTags:
+      description: List of tags to filter results
+      explode: true
+      in: query
+      name: tags
+      required: false
+      schema:
+        items:
+          type: string
+        type: array
+      style: form
     OrderBy:
       description: |
         The name of the field to order the results by.
@@ -3520,7 +3860,7 @@ components:
         application/json:
           schema:
             $ref: '#/components/schemas/Error'
-      description: The resource that a client tried to create already exists.
+      description: An existing resource conflicts with the request.
     Unknown:
       content:
         application/json:
@@ -3548,15 +3888,19 @@ components:
       properties:
         first_name:
           description: The user firstname
+          minLength: 1
           type: string
         last_name:
           description: The user lastname
+          minLength: 1
           type: string
         username:
           description: The username
+          minLength: 1
           type: string
         email:
           description: The user's email
+          minLength: 1
           type: string
         active:
           description: Whether the user is active
@@ -3583,7 +3927,6 @@ components:
           description: User roles
           items:
             $ref: '#/components/schemas/UserCollectionItem_roles'
-          readOnly: true
           type: array
         created_on:
           description: The date user was created
@@ -3649,10 +3992,24 @@ components:
       - $ref: '#/components/schemas/ConnectionCollectionItem'
       - $ref: '#/components/schemas/Connection_allOf'
       description: Full representation of the connection.
+    ConnectionTest:
+      description: Connection test results.
+      example:
+        message: message
+        status: true
+      properties:
+        status:
+          description: The status of the request.
+          type: boolean
+        message:
+          description: The success or failure message of the request.
+          type: string
+      type: object
     DAG:
       description: DAG
       example:
         root_dag_id: root_dag_id
+        is_active: true
         is_paused: true
         description: description
         file_token: file_token
@@ -3680,6 +4037,11 @@ components:
           description: Whether the DAG is paused.
           nullable: true
           type: boolean
+        is_active:
+          description: Whether the DAG is currently seen by the scheduler(s).
+          nullable: true
+          readOnly: true
+          type: boolean
         is_subdag:
           description: Whether the DAG is SubDAG.
           readOnly: true
@@ -3728,6 +4090,7 @@ components:
         external_trigger: true
         conf: '{}'
         dag_id: dag_id
+        logical_date: 2000-01-23T04:56:07.000+00:00
         start_date: 2000-01-23T04:56:07.000+00:00
       properties:
         dag_run_id:
@@ -3747,17 +4110,32 @@ components:
         dag_id:
           readOnly: true
           type: string
-        execution_date:
+        logical_date:
           description: |
-            The execution date. This is the time when the DAG run should be started according to the DAG definition.
-            The value of this field can be set only when creating the object. If you try to modify the field of an existing object, the request fails with an BAD_REQUEST error.
+            The logical date (previously called execution date). This is the time or interval covered by
+            this DAG run, according to the DAG definition.
+
+            The value of this field can be set only when creating the object. If you try to modify the
+            field of an existing object, the request fails with an BAD_REQUEST error.
+
             This together with DAG_ID are a unique key.
           format: date-time
+          nullable: true
+          type: string
+        execution_date:
+          deprecated: true
+          description: |
+            The execution date. This is the same as logical_date, kept for backwards compatibility.
+            If both this field and logical_date are provided but with different values, the request
+            will fail with an BAD_REQUEST error.
+          format: date-time
+          nullable: true
           type: string
         start_date:
           description: |
             The start time. The time when DAG run was actually created.
           format: date-time
+          nullable: true
           readOnly: true
           type: string
         end_date:
@@ -3781,6 +4159,17 @@ components:
       required:
       - dag_id
       type: object
+    UpdateDagRunState:
+      example:
+        state: success
+      properties:
+        state:
+          description: The state to set this DagRun
+          enum:
+          - success
+          - failed
+          type: string
+      type: object
     DAGRunCollection:
       allOf:
       - $ref: '#/components/schemas/DAGRunCollection_allOf'
@@ -4067,6 +4456,7 @@ components:
         priority_weight:
           type: integer
         operator:
+          nullable: true
           type: string
         queued_when:
           nullable: true
@@ -4248,6 +4638,7 @@ components:
         - downstream_task_ids
         sub_dag:
           root_dag_id: root_dag_id
+          is_active: true
           is_paused: true
           description: description
           file_token: file_token
@@ -4382,6 +4773,7 @@ components:
           - downstream_task_ids
           sub_dag:
             root_dag_id: root_dag_id
+            is_active: true
             is_paused: true
             description: description
             file_token: file_token
@@ -4436,6 +4828,7 @@ components:
           - downstream_task_ids
           sub_dag:
             root_dag_id: root_dag_id
+            is_active: true
             is_paused: true
             description: description
             file_token: file_token
@@ -5132,13 +5525,16 @@ components:
       - queued
       - none
       - scheduled
+      - deferred
+      - sensing
       - removed
       type: string
     DagState:
       description: DAG State.
       enum:
-      - success
+      - queued
       - running
+      - success
       - failed
       type: string
     TriggerRule:
@@ -5152,6 +5548,7 @@ components:
       - none_failed
       - none_skipped
       - none_failed_or_skipped
+      - none_failed_min_one_success
       - dummy
       type: string
     WeightRule:
@@ -5215,7 +5612,7 @@ components:
     Connection_allOf:
       properties:
         password:
-          description: Paasword of the connection.
+          description: Password of the connection.
           format: password
           type: string
           writeOnly: true
diff --git a/airflow/api_config.go b/airflow/api_config.go
index 2657970..9001960 100644
--- a/airflow/api_config.go
+++ b/airflow/api_config.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
diff --git a/airflow/api_connection.go b/airflow/api_connection.go
index eb6c347..7543e69 100644
--- a/airflow/api_connection.go
+++ b/airflow/api_connection.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
@@ -757,3 +757,153 @@ func (a *ConnectionApiService) PostConnectionExecute(r ApiPostConnectionRequest)
 
 	return localVarReturnValue, localVarHTTPResponse, nil
 }
+
+type ApiTestConnectionRequest struct {
+	ctx _context.Context
+	ApiService *ConnectionApiService
+	connection *Connection
+}
+
+func (r ApiTestConnectionRequest) Connection(connection Connection) ApiTestConnectionRequest {
+	r.connection = &connection
+	return r
+}
+
+func (r ApiTestConnectionRequest) Execute() (ConnectionTest, *_nethttp.Response, error) {
+	return r.ApiService.TestConnectionExecute(r)
+}
+
+/*
+ * TestConnection Test a connection
+ * @param ctx _context.Context - for authentication, logging, cancellation, deadlines, tracing, etc. Passed from http.Request or context.Background().
+ * @return ApiTestConnectionRequest
+ */
+func (a *ConnectionApiService) TestConnection(ctx _context.Context) ApiTestConnectionRequest {
+	return ApiTestConnectionRequest{
+		ApiService: a,
+		ctx: ctx,
+	}
+}
+
+/*
+ * Execute executes the request
+ * @return ConnectionTest
+ */
+func (a *ConnectionApiService) TestConnectionExecute(r ApiTestConnectionRequest) (ConnectionTest, *_nethttp.Response, error) {
+	var (
+		localVarHTTPMethod   = _nethttp.MethodPost
+		localVarPostBody     interface{}
+		localVarFormFileName string
+		localVarFileName     string
+		localVarFileBytes    []byte
+		localVarReturnValue  ConnectionTest
+	)
+
+	localBasePath, err := a.client.cfg.ServerURLWithContext(r.ctx, "ConnectionApiService.TestConnection")
+	if err != nil {
+		return localVarReturnValue, nil, GenericOpenAPIError{error: err.Error()}
+	}
+
+	localVarPath := localBasePath + "/connections/test"
+
+	localVarHeaderParams := make(map[string]string)
+	localVarQueryParams := _neturl.Values{}
+	localVarFormParams := _neturl.Values{}
+	if r.connection == nil {
+		return localVarReturnValue, nil, reportError("connection is required and must be specified")
+	}
+
+	// to determine the Content-Type header
+	localVarHTTPContentTypes := []string{"application/json"}
+
+	// set Content-Type header
+	localVarHTTPContentType := selectHeaderContentType(localVarHTTPContentTypes)
+	if localVarHTTPContentType != "" {
+		localVarHeaderParams["Content-Type"] = localVarHTTPContentType
+	}
+
+	// to determine the Accept header
+	localVarHTTPHeaderAccepts := []string{"application/json"}
+
+	// set Accept header
+	localVarHTTPHeaderAccept := selectHeaderAccept(localVarHTTPHeaderAccepts)
+	if localVarHTTPHeaderAccept != "" {
+		localVarHeaderParams["Accept"] = localVarHTTPHeaderAccept
+	}
+	// body params
+	localVarPostBody = r.connection
+	req, err := a.client.prepareRequest(r.ctx, localVarPath, localVarHTTPMethod, localVarPostBody, localVarHeaderParams, localVarQueryParams, localVarFormParams, localVarFormFileName, localVarFileName, localVarFileBytes)
+	if err != nil {
+		return localVarReturnValue, nil, err
+	}
+
+	localVarHTTPResponse, err := a.client.callAPI(req)
+	if err != nil || localVarHTTPResponse == nil {
+		return localVarReturnValue, localVarHTTPResponse, err
+	}
+
+	localVarBody, err := _ioutil.ReadAll(localVarHTTPResponse.Body)
+	localVarHTTPResponse.Body.Close()
+	localVarHTTPResponse.Body = _ioutil.NopCloser(bytes.NewBuffer(localVarBody))
+	if err != nil {
+		return localVarReturnValue, localVarHTTPResponse, err
+	}
+
+	if localVarHTTPResponse.StatusCode >= 300 {
+		newErr := GenericOpenAPIError{
+			body:  localVarBody,
+			error: localVarHTTPResponse.Status,
+		}
+		if localVarHTTPResponse.StatusCode == 400 {
+			var v Error
+			err = a.client.decode(&v, localVarBody, localVarHTTPResponse.Header.Get("Content-Type"))
+			if err != nil {
+				newErr.error = err.Error()
+				return localVarReturnValue, localVarHTTPResponse, newErr
+			}
+			newErr.model = v
+			return localVarReturnValue, localVarHTTPResponse, newErr
+		}
+		if localVarHTTPResponse.StatusCode == 401 {
+			var v Error
+			err = a.client.decode(&v, localVarBody, localVarHTTPResponse.Header.Get("Content-Type"))
+			if err != nil {
+				newErr.error = err.Error()
+				return localVarReturnValue, localVarHTTPResponse, newErr
+			}
+			newErr.model = v
+			return localVarReturnValue, localVarHTTPResponse, newErr
+		}
+		if localVarHTTPResponse.StatusCode == 403 {
+			var v Error
+			err = a.client.decode(&v, localVarBody, localVarHTTPResponse.Header.Get("Content-Type"))
+			if err != nil {
+				newErr.error = err.Error()
+				return localVarReturnValue, localVarHTTPResponse, newErr
+			}
+			newErr.model = v
+			return localVarReturnValue, localVarHTTPResponse, newErr
+		}
+		if localVarHTTPResponse.StatusCode == 404 {
+			var v Error
+			err = a.client.decode(&v, localVarBody, localVarHTTPResponse.Header.Get("Content-Type"))
+			if err != nil {
+				newErr.error = err.Error()
+				return localVarReturnValue, localVarHTTPResponse, newErr
+			}
+			newErr.model = v
+		}
+		return localVarReturnValue, localVarHTTPResponse, newErr
+	}
+
+	err = a.client.decode(&localVarReturnValue, localVarBody, localVarHTTPResponse.Header.Get("Content-Type"))
+	if err != nil {
+		newErr := GenericOpenAPIError{
+			body:  localVarBody,
+			error: err.Error(),
+		}
+		return localVarReturnValue, localVarHTTPResponse, newErr
+	}
+
+	return localVarReturnValue, localVarHTTPResponse, nil
+}
diff --git a/airflow/api_dag.go b/airflow/api_dag.go
index bd07a11..8c01aff 100644
--- a/airflow/api_dag.go
+++ b/airflow/api_dag.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
@@ -35,6 +35,7 @@ import (
 	_nethttp "net/http"
 	_neturl "net/url"
 	"strings"
+	"reflect"
 )
 
 // Linger please
@@ -45,6 +46,151 @@ var (
 // DAGApiService DAGApi service
 type DAGApiService service
 
+type ApiDeleteDagRequest struct {
+	ctx _context.Context
+	ApiService *DAGApiService
+	dagId string
+}
+
+
+func (r ApiDeleteDagRequest) Execute() (*_nethttp.Response, error) {
+	return r.ApiService.DeleteDagExecute(r)
+}
+
+/*
+ * DeleteDag Delete a DAG
+ * Deletes all metadata related to the DAG, including finished DAG Runs and Tasks. Logs are not deleted. This action cannot be undone.
+
+ * @param ctx _context.Context - for authentication, logging, cancellation, deadlines, tracing, etc. Passed from http.Request or context.Background().
+ * @param dagId The DAG ID.
+ * @return ApiDeleteDagRequest
+ */
+func (a *DAGApiService) DeleteDag(ctx _context.Context, dagId string) ApiDeleteDagRequest {
+	return ApiDeleteDagRequest{
+		ApiService: a,
+		ctx: ctx,
+		dagId: dagId,
+	}
+}
+
+/*
+ * Execute executes the request
+ */
+func (a *DAGApiService) DeleteDagExecute(r ApiDeleteDagRequest) (*_nethttp.Response, error) {
+	var (
+		localVarHTTPMethod   = _nethttp.MethodDelete
+		localVarPostBody     interface{}
+		localVarFormFileName string
+		localVarFileName     string
+		localVarFileBytes    []byte
+	)
+
+	localBasePath, err := a.client.cfg.ServerURLWithContext(r.ctx, "DAGApiService.DeleteDag")
+	if err != nil {
+		return nil, GenericOpenAPIError{error: err.Error()}
+	}
+
+	localVarPath := localBasePath + "/dags/{dag_id}"
+	localVarPath = strings.Replace(localVarPath, "{"+"dag_id"+"}", _neturl.PathEscape(parameterToString(r.dagId, "")), -1)
+
+	localVarHeaderParams := make(map[string]string)
+	localVarQueryParams := _neturl.Values{}
+	localVarFormParams := _neturl.Values{}
+
+	// to determine the Content-Type header
+	localVarHTTPContentTypes := []string{}
+
+	// set Content-Type header
+	localVarHTTPContentType := selectHeaderContentType(localVarHTTPContentTypes)
+	if localVarHTTPContentType != "" {
+		localVarHeaderParams["Content-Type"] = localVarHTTPContentType
+	}
+
+	// to determine the Accept header
+	localVarHTTPHeaderAccepts := []string{"application/json"}
+
+	// set Accept header
+	localVarHTTPHeaderAccept := selectHeaderAccept(localVarHTTPHeaderAccepts)
+	if localVarHTTPHeaderAccept != "" {
+		localVarHeaderParams["Accept"] = localVarHTTPHeaderAccept
+	}
+	req, err := a.client.prepareRequest(r.ctx, localVarPath, localVarHTTPMethod, localVarPostBody, localVarHeaderParams, localVarQueryParams, localVarFormParams, localVarFormFileName, localVarFileName, localVarFileBytes)
+	if err != nil {
+		return nil, err
+	}
+
+	localVarHTTPResponse, err := a.client.callAPI(req)
+	if err != nil || localVarHTTPResponse == nil {
+		return localVarHTTPResponse, err
+	}
+
+	localVarBody, err := _ioutil.ReadAll(localVarHTTPResponse.Body)
+	localVarHTTPResponse.Body.Close()
+	localVarHTTPResponse.Body = _ioutil.NopCloser(bytes.NewBuffer(localVarBody))
+	if err != nil {
+		return localVarHTTPResponse, err
+	}
+
+	if localVarHTTPResponse.StatusCode >= 300 {
+		newErr := GenericOpenAPIError{
+			body:  localVarBody,
+			error: localVarHTTPResponse.Status,
+		}
+		if localVarHTTPResponse.StatusCode == 400 {
+			var v Error
+			err = a.client.decode(&v, localVarBody, localVarHTTPResponse.Header.Get("Content-Type"))
+			if err != nil {
+				newErr.error = err.Error()
+				return localVarHTTPResponse, newErr
+			}
+			newErr.model = v
+			return localVarHTTPResponse, newErr
+		}
+		if localVarHTTPResponse.StatusCode == 401 {
+			var v Error
+			err = a.client.decode(&v, localVarBody, localVarHTTPResponse.Header.Get("Content-Type"))
+			if err != nil {
+				newErr.error = err.Error()
+				return localVarHTTPResponse, newErr
+			}
+			newErr.model = v
+			return localVarHTTPResponse, newErr
+		}
+		if localVarHTTPResponse.StatusCode == 403 {
+			var v Error
+			err = a.client.decode(&v, localVarBody, localVarHTTPResponse.Header.Get("Content-Type"))
+			if err != nil {
+				newErr.error = err.Error()
+				return localVarHTTPResponse, newErr
+			}
+			newErr.model = v
+			return localVarHTTPResponse, newErr
+		}
+		if localVarHTTPResponse.StatusCode == 404 {
+			var v Error
+			err = a.client.decode(&v, localVarBody, localVarHTTPResponse.Header.Get("Content-Type"))
+			if err != nil {
+				newErr.error = err.Error()
+				return localVarHTTPResponse, newErr
+			}
+			newErr.model = v
+			return localVarHTTPResponse, newErr
+		}
+		if localVarHTTPResponse.StatusCode == 409 {
+			var v Error
+			err = a.client.decode(&v, localVarBody, localVarHTTPResponse.Header.Get("Content-Type"))
+			if err != nil {
+				newErr.error = err.Error()
+				return localVarHTTPResponse, newErr
+			}
+			newErr.model = v
+		}
+		return localVarHTTPResponse, newErr
+	}
+
+	return localVarHTTPResponse, nil
+}
+
 type ApiGetDagRequest struct {
 	ctx _context.Context
 	ApiService *DAGApiService
@@ -470,6 +616,8 @@ type ApiGetDagsRequest struct {
 	limit *int32
 	offset *int32
 	orderBy *string
+	tags *[]string
+	onlyActive *bool
 }
 
 func (r ApiGetDagsRequest) Limit(limit int32) ApiGetDagsRequest {
@@ -484,6 +632,14 @@ func (r ApiGetDagsRequest) OrderBy(orderBy string) ApiGetDagsRequest {
 	r.orderBy = &orderBy
 	return r
 }
+func (r ApiGetDagsRequest) Tags(tags []string) ApiGetDagsRequest {
+	r.tags = &tags
+	return r
+}
+func (r ApiGetDagsRequest) OnlyActive(onlyActive bool) ApiGetDagsRequest {
+	r.onlyActive = &onlyActive
+	return r
+}
 
 func (r ApiGetDagsRequest) Execute() (DAGCollection, *_nethttp.Response, error) {
 	return r.ApiService.GetDagsExecute(r)
@@ -535,6 +691,20 @@ func (a *DAGApiService) GetDagsExecute(r ApiGetDagsRequest) (DAGCollection, *_ne
 	if r.orderBy != nil {
 		localVarQueryParams.Add("order_by", parameterToString(*r.orderBy, ""))
 	}
+	if r.tags != nil {
+		t := *r.tags
+		if reflect.TypeOf(t).Kind() == reflect.Slice {
+			s := reflect.ValueOf(t)
+			for i := 0; i < s.Len(); i++ {
+				localVarQueryParams.Add("tags", parameterToString(s.Index(i), "multi"))
+			}
+		} else {
+			localVarQueryParams.Add("tags", parameterToString(t, "multi"))
+		}
+	}
+	if r.onlyActive != nil {
+		localVarQueryParams.Add("only_active", parameterToString(*r.onlyActive, ""))
+	}
 	// to determine the Content-Type header
 	localVarHTTPContentTypes := []string{}
 
diff --git a/airflow/api_dag_run.go b/airflow/api_dag_run.go
index 89b926c..4e6effa 100644
--- a/airflow/api_dag_run.go
+++ b/airflow/api_dag_run.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
@@ -814,3 +814,162 @@ func (a *DAGRunApiService) PostDagRunExecute(r ApiPostDagRunRequest) (DAGRun, *_
 
 	return localVarReturnValue, localVarHTTPResponse, nil
 }
+
+type ApiUpdateDagRunStateRequest struct {
+	ctx _context.Context
+	ApiService *DAGRunApiService
+	dagId string
+	dagRunId string
+	updateDagRunState *UpdateDagRunState
+}
+
+func (r ApiUpdateDagRunStateRequest) UpdateDagRunState(updateDagRunState UpdateDagRunState) ApiUpdateDagRunStateRequest {
+	r.updateDagRunState = &updateDagRunState
+	return r
+}
+
+func (r ApiUpdateDagRunStateRequest) Execute() (DAGRun, *_nethttp.Response, error) {
+	return r.ApiService.UpdateDagRunStateExecute(r)
+}
+
+/*
+ * UpdateDagRunState Modify a DAG run
+ * Modify a DAG run
+ * @param ctx _context.Context - for authentication, logging, cancellation, deadlines, tracing, etc. Passed from http.Request or context.Background().
+ * @param dagId The DAG ID.
+ * @param dagRunId The DAG run ID.
+ * @return ApiUpdateDagRunStateRequest
+ */
+func (a *DAGRunApiService) UpdateDagRunState(ctx _context.Context, dagId string, dagRunId string) ApiUpdateDagRunStateRequest {
+	return ApiUpdateDagRunStateRequest{
+		ApiService: a,
+		ctx: ctx,
+		dagId: dagId,
+		dagRunId: dagRunId,
+	}
+}
+
+/*
+ * Execute executes the request
+ * @return DAGRun
+ */
+func (a *DAGRunApiService) UpdateDagRunStateExecute(r ApiUpdateDagRunStateRequest) (DAGRun, *_nethttp.Response, error) {
+	var (
+		localVarHTTPMethod   = _nethttp.MethodPatch
+		localVarPostBody     interface{}
+		localVarFormFileName string
+		localVarFileName     string
+		localVarFileBytes    []byte
+		localVarReturnValue  DAGRun
+	)
+
+	localBasePath, err := a.client.cfg.ServerURLWithContext(r.ctx, "DAGRunApiService.UpdateDagRunState")
+	if err != nil {
+		return localVarReturnValue, nil, GenericOpenAPIError{error: err.Error()}
+	}
+
+	localVarPath := localBasePath + "/dags/{dag_id}/dagRuns/{dag_run_id}"
+	localVarPath = strings.Replace(localVarPath, "{"+"dag_id"+"}", _neturl.PathEscape(parameterToString(r.dagId, "")), -1)
+	localVarPath = strings.Replace(localVarPath, "{"+"dag_run_id"+"}", _neturl.PathEscape(parameterToString(r.dagRunId, "")), -1)
+
+	localVarHeaderParams := make(map[string]string)
+	localVarQueryParams := _neturl.Values{}
+	localVarFormParams := _neturl.Values{}
+	if r.updateDagRunState == nil {
+		return localVarReturnValue, nil, reportError("updateDagRunState is required and must be specified")
+	}
+
+	// to determine the Content-Type header
+	localVarHTTPContentTypes := []string{"application/json"}
+
+	// set Content-Type header
+	localVarHTTPContentType := selectHeaderContentType(localVarHTTPContentTypes)
+	if localVarHTTPContentType != "" {
+		localVarHeaderParams["Content-Type"] = localVarHTTPContentType
+	}
+
+	// to determine the Accept header
+	localVarHTTPHeaderAccepts := []string{"application/json"}
+
+	// set Accept header
+	localVarHTTPHeaderAccept := selectHeaderAccept(localVarHTTPHeaderAccepts)
+	if localVarHTTPHeaderAccept != "" {
+		localVarHeaderParams["Accept"] = localVarHTTPHeaderAccept
+	}
+	// body params
+	localVarPostBody = r.updateDagRunState
+	req, err := a.client.prepareRequest(r.ctx, localVarPath, localVarHTTPMethod, localVarPostBody, localVarHeaderParams, localVarQueryParams, localVarFormParams, localVarFormFileName, localVarFileName, localVarFileBytes)
+	if err != nil {
+		return localVarReturnValue, nil, err
+	}
+
+	localVarHTTPResponse, err := a.client.callAPI(req)
+	if err != nil || localVarHTTPResponse == nil {
+		return localVarReturnValue, localVarHTTPResponse, err
+	}
+
+	localVarBody, err := _ioutil.ReadAll(localVarHTTPResponse.Body)
+	localVarHTTPResponse.Body.Close()
+	localVarHTTPResponse.Body = _ioutil.NopCloser(bytes.NewBuffer(localVarBody))
+	if err != nil {
+		return localVarReturnValue, localVarHTTPResponse, err
+	}
+
+	if localVarHTTPResponse.StatusCode >= 300 {
+		newErr := GenericOpenAPIError{
+			body:  localVarBody,
+			error: localVarHTTPResponse.Status,
+		}
+		if localVarHTTPResponse.StatusCode == 400 {
+			var v Error
+			err = a.client.decode(&v, localVarBody, localVarHTTPResponse.Header.Get("Content-Type"))
+			if err != nil {
+				newErr.error = err.Error()
+				return localVarReturnValue, localVarHTTPResponse, newErr
+			}
+			newErr.model = v
+			return localVarReturnValue, localVarHTTPResponse, newErr
+		}
+		if localVarHTTPResponse.StatusCode == 401 {
+			var v Error
+			err = a.client.decode(&v, localVarBody, localVarHTTPResponse.Header.Get("Content-Type"))
+			if err != nil {
+				newErr.error = err.Error()
+				return localVarReturnValue, localVarHTTPResponse, newErr
+			}
+			newErr.model = v
+			return localVarReturnValue, localVarHTTPResponse, newErr
+		}
+		if localVarHTTPResponse.StatusCode == 403 {
+			var v Error
+			err = a.client.decode(&v, localVarBody, localVarHTTPResponse.Header.Get("Content-Type"))
+			if err != nil {
+				newErr.error = err.Error()
+				return localVarReturnValue, localVarHTTPResponse, newErr
+			}
+			newErr.model = v
+			return localVarReturnValue, localVarHTTPResponse, newErr
+		}
+		if localVarHTTPResponse.StatusCode == 404 {
+			var v Error
+			err = a.client.decode(&v, localVarBody, localVarHTTPResponse.Header.Get("Content-Type"))
+			if err != nil {
+				newErr.error = err.Error()
+				return localVarReturnValue, localVarHTTPResponse, newErr
+			}
+			newErr.model = v
+		}
+		return localVarReturnValue, localVarHTTPResponse, newErr
+	}
+
+	err = a.client.decode(&localVarReturnValue, localVarBody, localVarHTTPResponse.Header.Get("Content-Type"))
+	if err != nil {
+		newErr := GenericOpenAPIError{
+			body:  localVarBody,
+			error: err.Error(),
+		}
+		return localVarReturnValue, localVarHTTPResponse, newErr
+	}
+
+	return localVarReturnValue, localVarHTTPResponse, nil
+}
diff --git a/airflow/api_event_log.go b/airflow/api_event_log.go
index 7247f29..bb5f2d9 100644
--- a/airflow/api_event_log.go
+++ b/airflow/api_event_log.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
diff --git a/airflow/api_import_error.go b/airflow/api_import_error.go
index d1fa788..ac7bf99 100644
--- a/airflow/api_import_error.go
+++ b/airflow/api_import_error.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
diff --git a/airflow/api_monitoring.go b/airflow/api_monitoring.go
index 335a2d0..0b9b56a 100644
--- a/airflow/api_monitoring.go
+++ b/airflow/api_monitoring.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
diff --git a/airflow/api_permission.go b/airflow/api_permission.go
index eb7f5f7..a2135ca 100644
--- a/airflow/api_permission.go
+++ b/airflow/api_permission.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
diff --git a/airflow/api_plugin.go b/airflow/api_plugin.go
index a98f10b..f538151 100644
--- a/airflow/api_plugin.go
+++ b/airflow/api_plugin.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
diff --git a/airflow/api_pool.go b/airflow/api_pool.go
index 3ff7524..05ca15a 100644
--- a/airflow/api_pool.go
+++ b/airflow/api_pool.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
diff --git a/airflow/api_provider.go b/airflow/api_provider.go
index 13f6c1b..5d109a5 100644
--- a/airflow/api_provider.go
+++ b/airflow/api_provider.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
diff --git a/airflow/api_role.go b/airflow/api_role.go
index 86b725d..09bda36 100644
--- a/airflow/api_role.go
+++ b/airflow/api_role.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
diff --git a/airflow/api_task_instance.go b/airflow/api_task_instance.go
index 3b0df86..5e5792f 100644
--- a/airflow/api_task_instance.go
+++ b/airflow/api_task_instance.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
diff --git a/airflow/api_user.go b/airflow/api_user.go
index 1eb3178..cccc28f 100644
--- a/airflow/api_user.go
+++ b/airflow/api_user.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
@@ -45,6 +45,139 @@ var (
 // UserApiService UserApi service
 type UserApiService service
 
+type ApiDeleteUserRequest struct {
+	ctx _context.Context
+	ApiService *UserApiService
+	username string
+}
+
+
+func (r ApiDeleteUserRequest) Execute() (*_nethttp.Response, error) {
+	return r.ApiService.DeleteUserExecute(r)
+}
+
+/*
+ * DeleteUser Delete a user
+ * @param ctx _context.Context - for authentication, logging, cancellation, deadlines, tracing, etc. Passed from http.Request or context.Background().
+ * @param username The username of the user
+ * @return ApiDeleteUserRequest
+ */
+func (a *UserApiService) DeleteUser(ctx _context.Context, username string) ApiDeleteUserRequest {
+	return ApiDeleteUserRequest{
+		ApiService: a,
+		ctx: ctx,
+		username: username,
+	}
+}
+
+/*
+ * Execute executes the request
+ */
+func (a *UserApiService) DeleteUserExecute(r ApiDeleteUserRequest) (*_nethttp.Response, error) {
+	var (
+		localVarHTTPMethod   = _nethttp.MethodDelete
+		localVarPostBody     interface{}
+		localVarFormFileName string
+		localVarFileName     string
+		localVarFileBytes    []byte
+	)
+
+	localBasePath, err := a.client.cfg.ServerURLWithContext(r.ctx, "UserApiService.DeleteUser")
+	if err != nil {
+		return nil, GenericOpenAPIError{error: err.Error()}
+	}
+
+	localVarPath := localBasePath + "/users/{username}"
+	localVarPath = strings.Replace(localVarPath, "{"+"username"+"}", _neturl.PathEscape(parameterToString(r.username, "")), -1)
+
+	localVarHeaderParams := make(map[string]string)
+	localVarQueryParams := _neturl.Values{}
+	localVarFormParams := _neturl.Values{}
+
+	// to determine the Content-Type header
+	localVarHTTPContentTypes := []string{}
+
+	// set Content-Type header
+	localVarHTTPContentType := selectHeaderContentType(localVarHTTPContentTypes)
+	if localVarHTTPContentType != "" {
+		localVarHeaderParams["Content-Type"] = localVarHTTPContentType
+	}
+
+	// to determine the Accept header
+	localVarHTTPHeaderAccepts := []string{"application/json"}
+
+	// set Accept header
+	localVarHTTPHeaderAccept := selectHeaderAccept(localVarHTTPHeaderAccepts)
+	if localVarHTTPHeaderAccept != "" {
+		localVarHeaderParams["Accept"] = localVarHTTPHeaderAccept
+	}
+	req, err := a.client.prepareRequest(r.ctx, localVarPath, localVarHTTPMethod, localVarPostBody, localVarHeaderParams, localVarQueryParams, localVarFormParams, localVarFormFileName, localVarFileName, localVarFileBytes)
+	if err != nil {
+		return nil, err
+	}
+
+	localVarHTTPResponse, err := a.client.callAPI(req)
+	if err != nil || localVarHTTPResponse == nil {
+		return localVarHTTPResponse, err
+	}
+
+	localVarBody, err := _ioutil.ReadAll(localVarHTTPResponse.Body)
+	localVarHTTPResponse.Body.Close()
+	localVarHTTPResponse.Body = _ioutil.NopCloser(bytes.NewBuffer(localVarBody))
+	if err != nil {
+		return localVarHTTPResponse, err
+	}
+
+	if localVarHTTPResponse.StatusCode >= 300 {
+		newErr := GenericOpenAPIError{
+			body:  localVarBody,
+			error: localVarHTTPResponse.Status,
+		}
+		if localVarHTTPResponse.StatusCode == 400 {
+			var v Error
+			err = a.client.decode(&v, localVarBody, localVarHTTPResponse.Header.Get("Content-Type"))
+			if err != nil {
+				newErr.error = err.Error()
+				return localVarHTTPResponse, newErr
+			}
+			newErr.model = v
+			return localVarHTTPResponse, newErr
+		}
+		if localVarHTTPResponse.StatusCode == 401 {
+			var v Error
+			err = a.client.decode(&v, localVarBody, localVarHTTPResponse.Header.Get("Content-Type"))
+			if err != nil {
+				newErr.error = err.Error()
+				return localVarHTTPResponse, newErr
+			}
+			newErr.model = v
+			return localVarHTTPResponse, newErr
+		}
+		if localVarHTTPResponse.StatusCode == 403 {
+			var v Error
+			err = a.client.decode(&v, localVarBody, localVarHTTPResponse.Header.Get("Content-Type"))
+			if err != nil {
+				newErr.error = err.Error()
+				return localVarHTTPResponse, newErr
+			}
+			newErr.model = v
+			return localVarHTTPResponse, newErr
+		}
+		if localVarHTTPResponse.StatusCode == 404 {
+			var v Error
+			err = a.client.decode(&v, localVarBody, localVarHTTPResponse.Header.Get("Content-Type"))
+			if err != nil {
+				newErr.error = err.Error()
+				return localVarHTTPResponse, newErr
+			}
+			newErr.model = v
+		}
+		return localVarHTTPResponse, newErr
+	}
+
+	return localVarHTTPResponse, nil
+}
+
 type ApiGetUserRequest struct {
 	ctx _context.Context
 	ApiService *UserApiService
@@ -322,3 +455,315 @@ func (a *UserApiService) GetUsersExecute(r ApiGetUsersRequest) (UserCollection,
 
 	return localVarReturnValue, localVarHTTPResponse, nil
 }
+
+type ApiPatchUserRequest struct {
+	ctx _context.Context
+	ApiService *UserApiService
+	username string
+	user *User
+	updateMask *[]string
+}
+
+func (r ApiPatchUserRequest) User(user User) ApiPatchUserRequest {
+	r.user = &user
+	return r
+}
+func (r ApiPatchUserRequest) UpdateMask(updateMask []string) ApiPatchUserRequest {
+	r.updateMask = &updateMask
+	return r
+}
+
+func (r ApiPatchUserRequest) Execute() (Role, *_nethttp.Response, error) {
+	return r.ApiService.PatchUserExecute(r)
+}
+
+/*
+ * PatchUser Update a user
+ * @param ctx _context.Context - for authentication, logging, cancellation, deadlines, tracing, etc. Passed from http.Request or context.Background().
+ * @param username The username of the user
+ * @return ApiPatchUserRequest
+ */
+func (a *UserApiService) PatchUser(ctx _context.Context, username string) ApiPatchUserRequest {
+	return ApiPatchUserRequest{
+		ApiService: a,
+		ctx: ctx,
+		username: username,
+	}
+}
+
+/*
+ * Execute executes the request
+ * @return Role
+ */
+func (a *UserApiService) PatchUserExecute(r ApiPatchUserRequest) (Role, *_nethttp.Response, error) {
+	var (
+		localVarHTTPMethod   = _nethttp.MethodPatch
+		localVarPostBody     interface{}
+		localVarFormFileName string
+		localVarFileName     string
+		localVarFileBytes    []byte
+		localVarReturnValue  Role
+	)
+
+	localBasePath, err := a.client.cfg.ServerURLWithContext(r.ctx, "UserApiService.PatchUser")
+	if err != nil {
+		return localVarReturnValue, nil, GenericOpenAPIError{error: err.Error()}
+	}
+
+	localVarPath := localBasePath + "/users/{username}"
+	localVarPath = strings.Replace(localVarPath, "{"+"username"+"}", _neturl.PathEscape(parameterToString(r.username, "")), -1)
+
+	localVarHeaderParams := make(map[string]string)
+	localVarQueryParams := _neturl.Values{}
+	localVarFormParams := _neturl.Values{}
+	if r.user == nil {
+		return localVarReturnValue, nil, reportError("user is required and must be specified")
+	}
+
+	if r.updateMask != nil {
+		localVarQueryParams.Add("update_mask", parameterToString(*r.updateMask, "csv"))
+	}
+	// to determine the Content-Type header
+	localVarHTTPContentTypes := []string{"application/json"}
+
+	// set Content-Type header
+	localVarHTTPContentType := selectHeaderContentType(localVarHTTPContentTypes)
+	if localVarHTTPContentType != "" {
+		localVarHeaderParams["Content-Type"] = localVarHTTPContentType
+	}
+
+	// to determine the Accept header
+	localVarHTTPHeaderAccepts := []string{"application/json"}
+
+	// set Accept header
+	localVarHTTPHeaderAccept := selectHeaderAccept(localVarHTTPHeaderAccepts)
+	if localVarHTTPHeaderAccept != "" {
+		localVarHeaderParams["Accept"] = localVarHTTPHeaderAccept
+	}
+	// body params
+	localVarPostBody = r.user
+	req, err := a.client.prepareRequest(r.ctx, localVarPath, localVarHTTPMethod, localVarPostBody, localVarHeaderParams, localVarQueryParams, localVarFormParams, localVarFormFileName, localVarFileName, localVarFileBytes)
+	if err != nil {
+		return localVarReturnValue, nil, err
+	}
+
+	localVarHTTPResponse, err := a.client.callAPI(req)
+	if err != nil || localVarHTTPResponse == nil {
+		return localVarReturnValue, localVarHTTPResponse, err
+	}
+
+	localVarBody, err := _ioutil.ReadAll(localVarHTTPResponse.Body)
+	localVarHTTPResponse.Body.Close()
+	localVarHTTPResponse.Body = _ioutil.NopCloser(bytes.NewBuffer(localVarBody))
+	if err != nil {
+		return localVarReturnValue, localVarHTTPResponse, err
+	}
+
+	if localVarHTTPResponse.StatusCode >= 300 {
+		newErr := GenericOpenAPIError{
+			body:  localVarBody,
+			error: localVarHTTPResponse.Status,
+		}
+		if localVarHTTPResponse.StatusCode == 400 {
+			var v Error
+			err = a.client.decode(&v, localVarBody, localVarHTTPResponse.Header.Get("Content-Type"))
+			if err != nil {
+				newErr.error = err.Error()
+				return localVarReturnValue, localVarHTTPResponse, newErr
+			}
+			newErr.model = v
+			return localVarReturnValue, localVarHTTPResponse, newErr
+		}
+		if localVarHTTPResponse.StatusCode == 401 {
+			var v Error
+			err = a.client.decode(&v, localVarBody, localVarHTTPResponse.Header.Get("Content-Type"))
+			if err != nil {
+				newErr.error = err.Error()
+				return localVarReturnValue, localVarHTTPResponse, newErr
+			}
+			newErr.model = v
+			return localVarReturnValue, localVarHTTPResponse, newErr
+		}
+		if localVarHTTPResponse.StatusCode == 403 {
+			var v Error
+			err = a.client.decode(&v, localVarBody, localVarHTTPResponse.Header.Get("Content-Type"))
+			if err != nil {
+				newErr.error = err.Error()
+				return localVarReturnValue, localVarHTTPResponse, newErr
+			}
+			newErr.model = v
+			return localVarReturnValue, localVarHTTPResponse, newErr
+		}
+		if localVarHTTPResponse.StatusCode == 404 {
+			var v Error
+			err = a.client.decode(&v, localVarBody, localVarHTTPResponse.Header.Get("Content-Type"))
+			if err != nil {
+				newErr.error = err.Error()
+				return localVarReturnValue, localVarHTTPResponse, newErr
+			}
+			newErr.model = v
+		}
+		return localVarReturnValue, localVarHTTPResponse, newErr
+	}
+
+	err = a.client.decode(&localVarReturnValue, localVarBody, localVarHTTPResponse.Header.Get("Content-Type"))
+	if err != nil {
+		newErr := GenericOpenAPIError{
+			body:  localVarBody,
+			error: err.Error(),
+		}
+		return localVarReturnValue, localVarHTTPResponse, newErr
+	}
+
+	return localVarReturnValue, localVarHTTPResponse, nil
+}
+
+type ApiPostUserRequest struct {
+	ctx _context.Context
+	ApiService *UserApiService
+	user *User
+}
+
+func (r ApiPostUserRequest) User(user User) ApiPostUserRequest {
+	r.user = &user
+	return r
+}
+
+func (r ApiPostUserRequest) Execute() (User, *_nethttp.Response, error) {
+	return r.ApiService.PostUserExecute(r)
+}
+
+/*
+ * PostUser Create a user
+ * @param ctx _context.Context - for authentication, logging, cancellation, deadlines, tracing, etc. Passed from http.Request or context.Background().
+ * @return ApiPostUserRequest
+ */
+func (a *UserApiService) PostUser(ctx _context.Context) ApiPostUserRequest {
+	return ApiPostUserRequest{
+		ApiService: a,
+		ctx: ctx,
+	}
+}
+
+/*
+ * Execute executes the request
+ * @return User
+ */
+func (a *UserApiService) PostUserExecute(r ApiPostUserRequest) (User, *_nethttp.Response, error) {
+	var (
+		localVarHTTPMethod   = _nethttp.MethodPost
+		localVarPostBody     interface{}
+		localVarFormFileName string
+		localVarFileName     string
+		localVarFileBytes    []byte
+		localVarReturnValue  User
+	)
+
+	localBasePath, err := a.client.cfg.ServerURLWithContext(r.ctx, "UserApiService.PostUser")
+	if err != nil {
+		return localVarReturnValue, nil, GenericOpenAPIError{error: err.Error()}
+	}
+
+	localVarPath := localBasePath + "/users"
+
+	localVarHeaderParams := make(map[string]string)
+	localVarQueryParams := _neturl.Values{}
+	localVarFormParams := _neturl.Values{}
+	if r.user == nil {
+		return localVarReturnValue, nil, reportError("user is required and must be specified")
+	}
+
+	// to determine the Content-Type header
+	localVarHTTPContentTypes := []string{"application/json"}
+
+	// set Content-Type header
+	localVarHTTPContentType := selectHeaderContentType(localVarHTTPContentTypes)
+	if localVarHTTPContentType != "" {
+		localVarHeaderParams["Content-Type"] = localVarHTTPContentType
+	}
+
+	// to determine the Accept header
+	localVarHTTPHeaderAccepts := []string{"application/json"}
+
+	// set Accept header
+	localVarHTTPHeaderAccept := selectHeaderAccept(localVarHTTPHeaderAccepts)
+	if localVarHTTPHeaderAccept != "" {
+		localVarHeaderParams["Accept"] = localVarHTTPHeaderAccept
+	}
+	// body params
+	localVarPostBody = r.user
+	req, err := a.client.prepareRequest(r.ctx, localVarPath, localVarHTTPMethod, localVarPostBody, localVarHeaderParams, localVarQueryParams, localVarFormParams, localVarFormFileName, localVarFileName, localVarFileBytes)
+	if err != nil {
+		return localVarReturnValue, nil, err
+	}
+
+	localVarHTTPResponse, err := a.client.callAPI(req)
+	if err != nil || localVarHTTPResponse == nil {
+		return localVarReturnValue, localVarHTTPResponse, err
+	}
+
+	localVarBody, err := _ioutil.ReadAll(localVarHTTPResponse.Body)
+	localVarHTTPResponse.Body.Close()
+	localVarHTTPResponse.Body = _ioutil.NopCloser(bytes.NewBuffer(localVarBody))
+	if err != nil {
+		return localVarReturnValue, localVarHTTPResponse, err
+	}
+
+	if localVarHTTPResponse.StatusCode >= 300 {
+		newErr := GenericOpenAPIError{
+			body:  localVarBody,
+			error: localVarHTTPResponse.Status,
+		}
+		if localVarHTTPResponse.StatusCode == 400 {
+			var v Error
+			err = a.client.decode(&v, localVarBody, localVarHTTPResponse.Header.Get("Content-Type"))
+			if err != nil {
+				newErr.error = err.Error()
+				return localVarReturnValue, localVarHTTPResponse, newErr
+			}
+			newErr.model = v
+			return localVarReturnValue, localVarHTTPResponse, newErr
+		}
+		if localVarHTTPResponse.StatusCode == 401 {
+			var v Error
+			err = a.client.decode(&v, localVarBody, localVarHTTPResponse.Header.Get("Content-Type"))
+			if err != nil {
+				newErr.error = err.Error()
+				return localVarReturnValue, localVarHTTPResponse, newErr
+			}
+			newErr.model = v
+			return localVarReturnValue, localVarHTTPResponse, newErr
+		}
+		if localVarHTTPResponse.StatusCode == 403 {
+			var v Error
+			err = a.client.decode(&v, localVarBody, localVarHTTPResponse.Header.Get("Content-Type"))
+			if err != nil {
+				newErr.error = err.Error()
+				return localVarReturnValue, localVarHTTPResponse, newErr
+			}
+			newErr.model = v
+			return localVarReturnValue, localVarHTTPResponse, newErr
+		}
+		if localVarHTTPResponse.StatusCode == 409 {
+			var v Error
+			err = a.client.decode(&v, localVarBody, localVarHTTPResponse.Header.Get("Content-Type"))
+			if err != nil {
+				newErr.error = err.Error()
+				return localVarReturnValue, localVarHTTPResponse, newErr
+			}
+			newErr.model = v
+		}
+		return localVarReturnValue, localVarHTTPResponse, newErr
+	}
+
+	err = a.client.decode(&localVarReturnValue, localVarBody, localVarHTTPResponse.Header.Get("Content-Type"))
+	if err != nil {
+		newErr := GenericOpenAPIError{
+			body:  localVarBody,
+			error: err.Error(),
+		}
+		return localVarReturnValue, localVarHTTPResponse, newErr
+	}
+
+	return localVarReturnValue, localVarHTTPResponse, nil
+}
diff --git a/airflow/api_variable.go b/airflow/api_variable.go
index 6f93751..c6b14cf 100644
--- a/airflow/api_variable.go
+++ b/airflow/api_variable.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
diff --git a/airflow/api_x_com.go b/airflow/api_x_com.go
index 17b5ce0..c99f1a7 100644
--- a/airflow/api_x_com.go
+++ b/airflow/api_x_com.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
diff --git a/airflow/client.go b/airflow/client.go
index 1f3f31d..a0c80f2 100644
--- a/airflow/client.go
+++ b/airflow/client.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
diff --git a/airflow/configuration.go b/airflow/configuration.go
index 71ad298..b295a2f 100644
--- a/airflow/configuration.go
+++ b/airflow/configuration.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
diff --git a/airflow/docs/Connection.md b/airflow/docs/Connection.md
index 0efdf14..6f6cb8f 100644
--- a/airflow/docs/Connection.md
+++ b/airflow/docs/Connection.md
@@ -29,7 +29,7 @@ Name | Type | Description | Notes
 **Login** | Pointer to **NullableString** | Login of the connection. | [optional] 
 **Schema** | Pointer to **NullableString** | Schema of the connection. | [optional] 
 **Port** | Pointer to **NullableInt32** | Port of the connection. | [optional] 
-**Password** | Pointer to **string** | Paasword of the connection. | [optional] 
+**Password** | Pointer to **string** | Password of the connection. | [optional] 
 **Extra** | Pointer to **NullableString** | Other values that cannot be put into another field, e.g. RSA keys. | [optional] 
 
 ## Methods
diff --git a/airflow/docs/ConnectionAllOf.md b/airflow/docs/ConnectionAllOf.md
index fb1e5d2..1136962 100644
--- a/airflow/docs/ConnectionAllOf.md
+++ b/airflow/docs/ConnectionAllOf.md
@@ -23,7 +23,7 @@
 
 Name | Type | Description | Notes
 ------------ | ------------- | ------------- | -------------
-**Password** | Pointer to **string** | Paasword of the connection. | [optional] 
+**Password** | Pointer to **string** | Password of the connection. | [optional] 
 **Extra** | Pointer to **NullableString** | Other values that cannot be put into another field, e.g. RSA keys. | [optional] 
 
 ## Methods
diff --git a/airflow/docs/ConnectionApi.md b/airflow/docs/ConnectionApi.md
index 90177a2..11bba9e 100644
--- a/airflow/docs/ConnectionApi.md
+++ b/airflow/docs/ConnectionApi.md
@@ -28,6 +28,7 @@ Method | HTTP request | Description
 [**GetConnections**](ConnectionApi.md#GetConnections) | **Get** /connections | List connections
 [**PatchConnection**](ConnectionApi.md#PatchConnection) | **Patch** /connections/{connection_id} | Update a connection
 [**PostConnection**](ConnectionApi.md#PostConnection) | **Post** /connections | Create a connection
+[**TestConnection**](ConnectionApi.md#TestConnection) | **Post** /connections/test | Test a connection
 
 
 
@@ -368,3 +369,67 @@ No authorization required
 [[Back to Model list]](../README.md#documentation-for-models)
 [[Back to README]](../README.md)
 
+
+## TestConnection
+
+> ConnectionTest TestConnection(ctx).Connection(connection).Execute()
+
+Test a connection
+
+### Example
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+    openapiclient "./openapi"
+)
+
+func main() {
+    connection := *openapiclient.NewConnection() // Connection | 
+
+    configuration := openapiclient.NewConfiguration()
+    api_client := openapiclient.NewAPIClient(configuration)
+    resp, r, err := api_client.ConnectionApi.TestConnection(context.Background()).Connection(connection).Execute()
+    if err != nil {
+        fmt.Fprintf(os.Stderr, "Error when calling `ConnectionApi.TestConnection``: %v\n", err)
+        fmt.Fprintf(os.Stderr, "Full HTTP response: %v\n", r)
+    }
+    // response from `TestConnection`: ConnectionTest
+    fmt.Fprintf(os.Stdout, "Response from `ConnectionApi.TestConnection`: %v\n", resp)
+}
+```
+
+### Path Parameters
+
+
+
+### Other Parameters
+
+Other parameters are passed through a pointer to a apiTestConnectionRequest struct via the builder pattern
+
+
+Name | Type | Description  | Notes
+------------- | ------------- | ------------- | -------------
+ **connection** | [**Connection**](Connection.md) |  | 
+
+### Return type
+
+[**ConnectionTest**](ConnectionTest.md)
+
+### Authorization
+
+No authorization required
+
+### HTTP request headers
+
+- **Content-Type**: application/json
+- **Accept**: application/json
+
+[[Back to top]](#) [[Back to API list]](../README.md#documentation-for-api-endpoints)
+[[Back to Model list]](../README.md#documentation-for-models)
+[[Back to README]](../README.md)
+
diff --git a/airflow/docs/ConnectionTest.md b/airflow/docs/ConnectionTest.md
new file mode 100644
index 0000000..da001ac
--- /dev/null
+++ b/airflow/docs/ConnectionTest.md
@@ -0,0 +1,101 @@
+<!--
+ Licensed to the Apache Software Foundation (ASF) under one
+ or more contributor license agreements.  See the NOTICE file
+ distributed with this work for additional information
+ regarding copyright ownership.  The ASF licenses this file
+ to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance
+ with the License.  You may obtain a copy of the License at
+
+   http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing,
+ software distributed under the License is distributed on an
+ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ KIND, either express or implied.  See the License for the
+ specific language governing permissions and limitations
+ under the License.
+ -->
+
+# ConnectionTest
+
+## Properties
+
+Name | Type | Description | Notes
+------------ | ------------- | ------------- | -------------
+**Status** | Pointer to **bool** | The status of the request. | [optional] 
+**Message** | Pointer to **string** | The success or failure message of the request. | [optional] 
+
+## Methods
+
+### NewConnectionTest
+
+`func NewConnectionTest() *ConnectionTest`
+
+NewConnectionTest instantiates a new ConnectionTest object
+This constructor will assign default values to properties that have it defined,
+and makes sure properties required by API are set, but the set of arguments
+will change when the set of required properties is changed
+
+### NewConnectionTestWithDefaults
+
+`func NewConnectionTestWithDefaults() *ConnectionTest`
+
+NewConnectionTestWithDefaults instantiates a new ConnectionTest object
+This constructor will only assign default values to properties that have it defined,
+but it doesn't guarantee that properties required by API are set
+
+### GetStatus
+
+`func (o *ConnectionTest) GetStatus() bool`
+
+GetStatus returns the Status field if non-nil, zero value otherwise.
+
+### GetStatusOk
+
+`func (o *ConnectionTest) GetStatusOk() (*bool, bool)`
+
+GetStatusOk returns a tuple with the Status field if it's non-nil, zero value otherwise
+and a boolean to check if the value has been set.
+
+### SetStatus
+
+`func (o *ConnectionTest) SetStatus(v bool)`
+
+SetStatus sets Status field to given value.
+
+### HasStatus
+
+`func (o *ConnectionTest) HasStatus() bool`
+
+HasStatus returns a boolean if a field has been set.
+
+### GetMessage
+
+`func (o *ConnectionTest) GetMessage() string`
+
+GetMessage returns the Message field if non-nil, zero value otherwise.
+
+### GetMessageOk
+
+`func (o *ConnectionTest) GetMessageOk() (*string, bool)`
+
+GetMessageOk returns a tuple with the Message field if it's non-nil, zero value otherwise
+and a boolean to check if the value has been set.
+
+### SetMessage
+
+`func (o *ConnectionTest) SetMessage(v string)`
+
+SetMessage sets Message field to given value.
+
+### HasMessage
+
+`func (o *ConnectionTest) HasMessage() bool`
+
+HasMessage returns a boolean if a field has been set.
+
+
+[[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md)
+
+
diff --git a/airflow/docs/DAGApi.md b/airflow/docs/DAGApi.md
index adc7b1f..42afb9d 100644
--- a/airflow/docs/DAGApi.md
+++ b/airflow/docs/DAGApi.md
@@ -23,6 +23,7 @@ All URIs are relative to *http://localhost/api/v1*
 
 Method | HTTP request | Description
 ------------- | ------------- | -------------
+[**DeleteDag**](DAGApi.md#DeleteDag) | **Delete** /dags/{dag_id} | Delete a DAG
 [**GetDag**](DAGApi.md#GetDag) | **Get** /dags/{dag_id} | Get basic information about a DAG
 [**GetDagDetails**](DAGApi.md#GetDagDetails) | **Get** /dags/{dag_id}/details | Get a simplified representation of DAG
 [**GetDagSource**](DAGApi.md#GetDagSource) | **Get** /dagSources/{file_token} | Get a source code
@@ -35,6 +36,74 @@ Method | HTTP request | Description
 
 
 
+## DeleteDag
+
+> DeleteDag(ctx, dagId).Execute()
+
+Delete a DAG
+
+
+
+### Example
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+    openapiclient "./openapi"
+)
+
+func main() {
+    dagId := "dagId_example" // string | The DAG ID.
+
+    configuration := openapiclient.NewConfiguration()
+    api_client := openapiclient.NewAPIClient(configuration)
+    resp, r, err := api_client.DAGApi.DeleteDag(context.Background(), dagId).Execute()
+    if err != nil {
+        fmt.Fprintf(os.Stderr, "Error when calling `DAGApi.DeleteDag``: %v\n", err)
+        fmt.Fprintf(os.Stderr, "Full HTTP response: %v\n", r)
+    }
+}
+```
+
+### Path Parameters
+
+
+Name | Type | Description  | Notes
+------------- | ------------- | ------------- | -------------
+**ctx** | **context.Context** | context for authentication, logging, cancellation, deadlines, tracing, etc.
+**dagId** | **string** | The DAG ID. | 
+
+### Other Parameters
+
+Other parameters are passed through a pointer to a apiDeleteDagRequest struct via the builder pattern
+
+
+Name | Type | Description  | Notes
+------------- | ------------- | ------------- | -------------
+
+
+### Return type
+
+ (empty response body)
+
+### Authorization
+
+No authorization required
+
+### HTTP request headers
+
+- **Content-Type**: Not defined
+- **Accept**: application/json
+
+[[Back to top]](#) [[Back to API list]](../README.md#documentation-for-api-endpoints)
+[[Back to Model list]](../README.md#documentation-for-models)
+[[Back to README]](../README.md)
+
+
 ## GetDag
 
 > DAG GetDag(ctx, dagId).Execute()
@@ -247,7 +316,7 @@ No authorization required
 
 ## GetDags
 
-> DAGCollection GetDags(ctx).Limit(limit).Offset(offset).OrderBy(orderBy).Execute()
+> DAGCollection GetDags(ctx).Limit(limit).Offset(offset).OrderBy(orderBy).Tags(tags).OnlyActive(onlyActive).Execute()
 
 List DAGs
 
@@ -267,10 +336,12 @@ func main() {
     limit := int32(56) // int32 | The numbers of items to return. (optional) (default to 100)
     offset := int32(56) // int32 | The number of items to skip before starting to collect the result set. (optional)
     orderBy := "orderBy_example" // string | The name of the field to order the results by. Prefix a field name with `-` to reverse the sort order.  (optional)
+    tags := []string{"Inner_example"} // []string | List of tags to filter results (optional)
+    onlyActive := true // bool | Only return active DAGs. (optional) (default to true)
 
     configuration := openapiclient.NewConfiguration()
     api_client := openapiclient.NewAPIClient(configuration)
-    resp, r, err := api_client.DAGApi.GetDags(context.Background()).Limit(limit).Offset(offset).OrderBy(orderBy).Execute()
+    resp, r, err := api_client.DAGApi.GetDags(context.Background()).Limit(limit).Offset(offset).OrderBy(orderBy).Tags(tags).OnlyActive(onlyActive).Execute()
     if err != nil {
         fmt.Fprintf(os.Stderr, "Error when calling `DAGApi.GetDags``: %v\n", err)
         fmt.Fprintf(os.Stderr, "Full HTTP response: %v\n", r)
@@ -294,6 +365,8 @@ Name | Type | Description  | Notes
  **limit** | **int32** | The numbers of items to return. | [default to 100]
  **offset** | **int32** | The number of items to skip before starting to collect the result set. | 
  **orderBy** | **string** | The name of the field to order the results by. Prefix a field name with &#x60;-&#x60; to reverse the sort order.  | 
+ **tags** | **[]string** | List of tags to filter results | 
+ **onlyActive** | **bool** | Only return active DAGs. | [default to true]
 
 ### Return type
 
diff --git a/airflow/docs/DAGRunApi.md b/airflow/docs/DAGRunApi.md
index 037d55a..cebc1e1 100644
--- a/airflow/docs/DAGRunApi.md
+++ b/airflow/docs/DAGRunApi.md
@@ -28,6 +28,7 @@ Method | HTTP request | Description
 [**GetDagRuns**](DAGRunApi.md#GetDagRuns) | **Get** /dags/{dag_id}/dagRuns | List DAG runs
 [**GetDagRunsBatch**](DAGRunApi.md#GetDagRunsBatch) | **Post** /dags/~/dagRuns/list | List DAG runs (batch)
 [**PostDagRun**](DAGRunApi.md#PostDagRun) | **Post** /dags/{dag_id}/dagRuns | Trigger a new DAG run
+[**UpdateDagRunState**](DAGRunApi.md#UpdateDagRunState) | **Patch** /dags/{dag_id}/dagRuns/{dag_run_id} | Modify a DAG run
 
 
 
@@ -395,3 +396,78 @@ No authorization required
 [[Back to Model list]](../README.md#documentation-for-models)
 [[Back to README]](../README.md)
 
+
+## UpdateDagRunState
+
+> DAGRun UpdateDagRunState(ctx, dagId, dagRunId).UpdateDagRunState(updateDagRunState).Execute()
+
+Modify a DAG run
+
+
+
+### Example
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+    openapiclient "./openapi"
+)
+
+func main() {
+    dagId := "dagId_example" // string | The DAG ID.
+    dagRunId := "dagRunId_example" // string | The DAG run ID.
+    updateDagRunState := *openapiclient.NewUpdateDagRunState() // UpdateDagRunState | 
+
+    configuration := openapiclient.NewConfiguration()
+    api_client := openapiclient.NewAPIClient(configuration)
+    resp, r, err := api_client.DAGRunApi.UpdateDagRunState(context.Background(), dagId, dagRunId).UpdateDagRunState(updateDagRunState).Execute()
+    if err != nil {
+        fmt.Fprintf(os.Stderr, "Error when calling `DAGRunApi.UpdateDagRunState``: %v\n", err)
+        fmt.Fprintf(os.Stderr, "Full HTTP response: %v\n", r)
+    }
+    // response from `UpdateDagRunState`: DAGRun
+    fmt.Fprintf(os.Stdout, "Response from `DAGRunApi.UpdateDagRunState`: %v\n", resp)
+}
+```
+
+### Path Parameters
+
+
+Name | Type | Description  | Notes
+------------- | ------------- | ------------- | -------------
+**ctx** | **context.Context** | context for authentication, logging, cancellation, deadlines, tracing, etc.
+**dagId** | **string** | The DAG ID. | 
+**dagRunId** | **string** | The DAG run ID. | 
+
+### Other Parameters
+
+Other parameters are passed through a pointer to a apiUpdateDagRunStateRequest struct via the builder pattern
+
+
+Name | Type | Description  | Notes
+------------- | ------------- | ------------- | -------------
+
+
+ **updateDagRunState** | [**UpdateDagRunState**](UpdateDagRunState.md) |  | 
+
+### Return type
+
+[**DAGRun**](DAGRun.md)
+
+### Authorization
+
+No authorization required
+
+### HTTP request headers
+
+- **Content-Type**: application/json
+- **Accept**: application/json
+
+[[Back to top]](#) [[Back to API list]](../README.md#documentation-for-api-endpoints)
+[[Back to Model list]](../README.md#documentation-for-models)
+[[Back to README]](../README.md)
+
diff --git a/airflow/docs/Dag.md b/airflow/docs/Dag.md
index 3805178..06cd302 100644
--- a/airflow/docs/Dag.md
+++ b/airflow/docs/Dag.md
@@ -26,6 +26,7 @@ Name | Type | Description | Notes
 **DagId** | Pointer to **string** | The ID of the DAG. | [optional] [readonly] 
 **RootDagId** | Pointer to **NullableString** | If the DAG is SubDAG then it is the top level DAG identifier. Otherwise, null. | [optional] [readonly] 
 **IsPaused** | Pointer to **NullableBool** | Whether the DAG is paused. | [optional] 
+**IsActive** | Pointer to **NullableBool** | Whether the DAG is currently seen by the scheduler(s). | [optional] [readonly] 
 **IsSubdag** | Pointer to **bool** | Whether the DAG is SubDAG. | [optional] [readonly] 
 **Fileloc** | Pointer to **string** | The absolute path to the file. | [optional] [readonly] 
 **FileToken** | Pointer to **string** | The key containing the encrypted path to the file. Encryption and decryption take place only on the server. This prevents the client from reading an non-DAG file. This also ensures API extensibility, because the format of encrypted data may change.  | [optional] [readonly] 
@@ -148,6 +149,41 @@ HasIsPaused returns a boolean if a field has been set.
 `func (o *DAG) UnsetIsPaused()`
 
 UnsetIsPaused ensures that no value is present for IsPaused, not even an explicit nil
+### GetIsActive
+
+`func (o *DAG) GetIsActive() bool`
+
+GetIsActive returns the IsActive field if non-nil, zero value otherwise.
+
+### GetIsActiveOk
+
+`func (o *DAG) GetIsActiveOk() (*bool, bool)`
+
+GetIsActiveOk returns a tuple with the IsActive field if it's non-nil, zero value otherwise
+and a boolean to check if the value has been set.
+
+### SetIsActive
+
+`func (o *DAG) SetIsActive(v bool)`
+
+SetIsActive sets IsActive field to given value.
+
+### HasIsActive
+
+`func (o *DAG) HasIsActive() bool`
+
+HasIsActive returns a boolean if a field has been set.
+
+### SetIsActiveNil
+
+`func (o *DAG) SetIsActiveNil(b bool)`
+
+ SetIsActiveNil sets the value for IsActive to be an explicit nil
+
+### UnsetIsActive
+`func (o *DAG) UnsetIsActive()`
+
+UnsetIsActive ensures that no value is present for IsActive, not even an explicit nil
 ### GetIsSubdag
 
 `func (o *DAG) GetIsSubdag() bool`
diff --git a/airflow/docs/DagDetail.md b/airflow/docs/DagDetail.md
index e17709c..3f618b4 100644
--- a/airflow/docs/DagDetail.md
+++ b/airflow/docs/DagDetail.md
@@ -26,6 +26,7 @@ Name | Type | Description | Notes
 **DagId** | Pointer to **string** | The ID of the DAG. | [optional] [readonly] 
 **RootDagId** | Pointer to **NullableString** | If the DAG is SubDAG then it is the top level DAG identifier. Otherwise, null. | [optional] [readonly] 
 **IsPaused** | Pointer to **NullableBool** | Whether the DAG is paused. | [optional] 
+**IsActive** | Pointer to **NullableBool** | Whether the DAG is currently seen by the scheduler(s). | [optional] [readonly] 
 **IsSubdag** | Pointer to **bool** | Whether the DAG is SubDAG. | [optional] [readonly] 
 **Fileloc** | Pointer to **string** | The absolute path to the file. | [optional] [readonly] 
 **FileToken** | Pointer to **string** | The key containing the encrypted path to the file. Encryption and decryption take place only on the server. This prevents the client from reading an non-DAG file. This also ensures API extensibility, because the format of encrypted data may change.  | [optional] [readonly] 
@@ -157,6 +158,41 @@ HasIsPaused returns a boolean if a field has been set.
 `func (o *DAGDetail) UnsetIsPaused()`
 
 UnsetIsPaused ensures that no value is present for IsPaused, not even an explicit nil
+### GetIsActive
+
+`func (o *DAGDetail) GetIsActive() bool`
+
+GetIsActive returns the IsActive field if non-nil, zero value otherwise.
+
+### GetIsActiveOk
+
+`func (o *DAGDetail) GetIsActiveOk() (*bool, bool)`
+
+GetIsActiveOk returns a tuple with the IsActive field if it's non-nil, zero value otherwise
+and a boolean to check if the value has been set.
+
+### SetIsActive
+
+`func (o *DAGDetail) SetIsActive(v bool)`
+
+SetIsActive sets IsActive field to given value.
+
+### HasIsActive
+
+`func (o *DAGDetail) HasIsActive() bool`
+
+HasIsActive returns a boolean if a field has been set.
+
+### SetIsActiveNil
+
+`func (o *DAGDetail) SetIsActiveNil(b bool)`
+
+ SetIsActiveNil sets the value for IsActive to be an explicit nil
+
+### UnsetIsActive
+`func (o *DAGDetail) UnsetIsActive()`
+
+UnsetIsActive ensures that no value is present for IsActive, not even an explicit nil
 ### GetIsSubdag
 
 `func (o *DAGDetail) GetIsSubdag() bool`
diff --git a/airflow/docs/DagRun.md b/airflow/docs/DagRun.md
index b4f0c85..f148e73 100644
--- a/airflow/docs/DagRun.md
+++ b/airflow/docs/DagRun.md
@@ -25,8 +25,9 @@ Name | Type | Description | Notes
 ------------ | ------------- | ------------- | -------------
 **DagRunId** | Pointer to **NullableString** | Run ID.  The value of this field can be set only when creating the object. If you try to modify the field of an existing object, the request fails with an BAD_REQUEST error.  If not provided, a value will be generated based on execution_date.  If the specified dag_run_id is in use, the creation request fails with an ALREADY_EXISTS error.  This together with DAG_ID are a unique key.  | [optional] 
 **DagId** | **string** |  | [readonly] 
-**ExecutionDate** | Pointer to **time.Time** | The execution date. This is the time when the DAG run should be started according to the DAG definition. The value of this field can be set only when creating the object. If you try to modify the field of an existing object, the request fails with an BAD_REQUEST error. This together with DAG_ID are a unique key.  | [optional] 
-**StartDate** | Pointer to **time.Time** | The start time. The time when DAG run was actually created.  | [optional] [readonly] 
+**LogicalDate** | Pointer to **NullableTime** | The logical date (previously called execution date). This is the time or interval covered by this DAG run, according to the DAG definition.  The value of this field can be set only when creating the object. If you try to modify the field of an existing object, the request fails with an BAD_REQUEST error.  This together with DAG_ID are a unique key.  | [optional] 
+**ExecutionDate** | Pointer to **NullableTime** | The execution date. This is the same as logical_date, kept for backwards compatibility. If both this field and logical_date are provided but with different values, the request will fail with an BAD_REQUEST error.  | [optional] 
+**StartDate** | Pointer to **NullableTime** | The start time. The time when DAG run was actually created.  | [optional] [readonly] 
 **EndDate** | Pointer to **NullableTime** |  | [optional] [readonly] 
 **State** | Pointer to [**DagState**](DagState.md) |  | [optional] 
 **ExternalTrigger** | Pointer to **bool** |  | [optional] [readonly] [default to true]
@@ -106,6 +107,41 @@ and a boolean to check if the value has been set.
 SetDagId sets DagId field to given value.
 
 
+### GetLogicalDate
+
+`func (o *DAGRun) GetLogicalDate() time.Time`
+
+GetLogicalDate returns the LogicalDate field if non-nil, zero value otherwise.
+
+### GetLogicalDateOk
+
+`func (o *DAGRun) GetLogicalDateOk() (*time.Time, bool)`
+
+GetLogicalDateOk returns a tuple with the LogicalDate field if it's non-nil, zero value otherwise
+and a boolean to check if the value has been set.
+
+### SetLogicalDate
+
+`func (o *DAGRun) SetLogicalDate(v time.Time)`
+
+SetLogicalDate sets LogicalDate field to given value.
+
+### HasLogicalDate
+
+`func (o *DAGRun) HasLogicalDate() bool`
+
+HasLogicalDate returns a boolean if a field has been set.
+
+### SetLogicalDateNil
+
+`func (o *DAGRun) SetLogicalDateNil(b bool)`
+
+ SetLogicalDateNil sets the value for LogicalDate to be an explicit nil
+
+### UnsetLogicalDate
+`func (o *DAGRun) UnsetLogicalDate()`
+
+UnsetLogicalDate ensures that no value is present for LogicalDate, not even an explicit nil
 ### GetExecutionDate
 
 `func (o *DAGRun) GetExecutionDate() time.Time`
@@ -131,6 +167,16 @@ SetExecutionDate sets ExecutionDate field to given value.
 
 HasExecutionDate returns a boolean if a field has been set.
 
+### SetExecutionDateNil
+
+`func (o *DAGRun) SetExecutionDateNil(b bool)`
+
+ SetExecutionDateNil sets the value for ExecutionDate to be an explicit nil
+
+### UnsetExecutionDate
+`func (o *DAGRun) UnsetExecutionDate()`
+
+UnsetExecutionDate ensures that no value is present for ExecutionDate, not even an explicit nil
 ### GetStartDate
 
 `func (o *DAGRun) GetStartDate() time.Time`
@@ -156,6 +202,16 @@ SetStartDate sets StartDate field to given value.
 
 HasStartDate returns a boolean if a field has been set.
 
+### SetStartDateNil
+
+`func (o *DAGRun) SetStartDateNil(b bool)`
+
+ SetStartDateNil sets the value for StartDate to be an explicit nil
+
+### UnsetStartDate
+`func (o *DAGRun) UnsetStartDate()`
+
+UnsetStartDate ensures that no value is present for StartDate, not even an explicit nil
 ### GetEndDate
 
 `func (o *DAGRun) GetEndDate() time.Time`
diff --git a/airflow/docs/DagState.md b/airflow/docs/DagState.md
index 3d111f7..389be7f 100644
--- a/airflow/docs/DagState.md
+++ b/airflow/docs/DagState.md
@@ -22,10 +22,12 @@
 ## Enum
 
 
-* `SUCCESS` (value: `"success"`)
+* `QUEUED` (value: `"queued"`)
 
 * `RUNNING` (value: `"running"`)
 
+* `SUCCESS` (value: `"success"`)
+
 * `FAILED` (value: `"failed"`)
 
 
diff --git a/airflow/docs/TaskInstance.md b/airflow/docs/TaskInstance.md
index d720b56..ffdc0e7 100644
--- a/airflow/docs/TaskInstance.md
+++ b/airflow/docs/TaskInstance.md
@@ -38,7 +38,7 @@ Name | Type | Description | Notes
 **PoolSlots** | Pointer to **int32** |  | [optional] 
 **Queue** | Pointer to **string** |  | [optional] 
 **PriorityWeight** | Pointer to **int32** |  | [optional] 
-**Operator** | Pointer to **string** |  | [optional] 
+**Operator** | Pointer to **NullableString** |  | [optional] 
 **QueuedWhen** | Pointer to **NullableString** |  | [optional] 
 **Pid** | Pointer to **NullableInt32** |  | [optional] 
 **ExecutorConfig** | Pointer to **string** |  | [optional] 
@@ -493,6 +493,16 @@ SetOperator sets Operator field to given value.
 
 HasOperator returns a boolean if a field has been set.
 
+### SetOperatorNil
+
+`func (o *TaskInstance) SetOperatorNil(b bool)`
+
+ SetOperatorNil sets the value for Operator to be an explicit nil
+
+### UnsetOperator
+`func (o *TaskInstance) UnsetOperator()`
+
+UnsetOperator ensures that no value is present for Operator, not even an explicit nil
 ### GetQueuedWhen
 
 `func (o *TaskInstance) GetQueuedWhen() string`
diff --git a/airflow/docs/TaskState.md b/airflow/docs/TaskState.md
index 0c59037..df485e4 100644
--- a/airflow/docs/TaskState.md
+++ b/airflow/docs/TaskState.md
@@ -42,6 +42,10 @@
 
 * `SCHEDULED` (value: `"scheduled"`)
 
+* `DEFERRED` (value: `"deferred"`)
+
+* `SENSING` (value: `"sensing"`)
+
 * `REMOVED` (value: `"removed"`)
 
 
diff --git a/airflow/docs/TriggerRule.md b/airflow/docs/TriggerRule.md
index 9f696a0..83c3bcc 100644
--- a/airflow/docs/TriggerRule.md
+++ b/airflow/docs/TriggerRule.md
@@ -38,6 +38,8 @@
 
 * `NONE_FAILED_OR_SKIPPED` (value: `"none_failed_or_skipped"`)
 
+* `NONE_FAILED_MIN_ONE_SUCCESS` (value: `"none_failed_min_one_success"`)
+
 * `DUMMY` (value: `"dummy"`)
 
 
diff --git a/airflow/docs/UpdateDagRunState.md b/airflow/docs/UpdateDagRunState.md
new file mode 100644
index 0000000..c6ffb25
--- /dev/null
+++ b/airflow/docs/UpdateDagRunState.md
@@ -0,0 +1,75 @@
+<!--
+ Licensed to the Apache Software Foundation (ASF) under one
+ or more contributor license agreements.  See the NOTICE file
+ distributed with this work for additional information
+ regarding copyright ownership.  The ASF licenses this file
+ to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance
+ with the License.  You may obtain a copy of the License at
+
+   http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing,
+ software distributed under the License is distributed on an
+ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ KIND, either express or implied.  See the License for the
+ specific language governing permissions and limitations
+ under the License.
+ -->
+
+# UpdateDagRunState
+
+## Properties
+
+Name | Type | Description | Notes
+------------ | ------------- | ------------- | -------------
+**State** | Pointer to **string** | The state to set this DagRun | [optional] 
+
+## Methods
+
+### NewUpdateDagRunState
+
+`func NewUpdateDagRunState() *UpdateDagRunState`
+
+NewUpdateDagRunState instantiates a new UpdateDagRunState object
+This constructor will assign default values to properties that have it defined,
+and makes sure properties required by API are set, but the set of arguments
+will change when the set of required properties is changed
+
+### NewUpdateDagRunStateWithDefaults
+
+`func NewUpdateDagRunStateWithDefaults() *UpdateDagRunState`
+
+NewUpdateDagRunStateWithDefaults instantiates a new UpdateDagRunState object
+This constructor will only assign default values to properties that have it defined,
+but it doesn't guarantee that properties required by API are set
+
+### GetState
+
+`func (o *UpdateDagRunState) GetState() string`
+
+GetState returns the State field if non-nil, zero value otherwise.
+
+### GetStateOk
+
+`func (o *UpdateDagRunState) GetStateOk() (*string, bool)`
+
+GetStateOk returns a tuple with the State field if it's non-nil, zero value otherwise
+and a boolean to check if the value has been set.
+
+### SetState
+
+`func (o *UpdateDagRunState) SetState(v string)`
+
+SetState sets State field to given value.
+
+### HasState
+
+`func (o *UpdateDagRunState) HasState() bool`
+
+HasState returns a boolean if a field has been set.
+
+
+[[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md)
+
+
diff --git a/airflow/docs/User.md b/airflow/docs/User.md
index 6aa8a14..ba0fb3e 100644
--- a/airflow/docs/User.md
+++ b/airflow/docs/User.md
@@ -31,7 +31,7 @@ Name | Type | Description | Notes
 **LastLogin** | Pointer to **NullableString** | The last user login | [optional] [readonly] 
 **LoginCount** | Pointer to **NullableInt32** | The login count | [optional] [readonly] 
 **FailedLoginCount** | Pointer to **NullableInt32** | The number of times the login failed | [optional] [readonly] 
-**Roles** | Pointer to [**[]UserCollectionItemRoles**](UserCollectionItemRoles.md) | User roles | [optional] [readonly] 
+**Roles** | Pointer to [**[]UserCollectionItemRoles**](UserCollectionItemRoles.md) | User roles | [optional] 
 **CreatedOn** | Pointer to **NullableString** | The date user was created | [optional] [readonly] 
 **ChangedOn** | Pointer to **NullableString** | The date user was changed | [optional] [readonly] 
 **Password** | Pointer to **string** |  | [optional] 
diff --git a/airflow/docs/UserApi.md b/airflow/docs/UserApi.md
index 3c85996..4df0c6d 100644
--- a/airflow/docs/UserApi.md
+++ b/airflow/docs/UserApi.md
@@ -23,11 +23,80 @@ All URIs are relative to *http://localhost/api/v1*
 
 Method | HTTP request | Description
 ------------- | ------------- | -------------
+[**DeleteUser**](UserApi.md#DeleteUser) | **Delete** /users/{username} | Delete a user
 [**GetUser**](UserApi.md#GetUser) | **Get** /users/{username} | Get a user
 [**GetUsers**](UserApi.md#GetUsers) | **Get** /users | List users
+[**PatchUser**](UserApi.md#PatchUser) | **Patch** /users/{username} | Update a user
+[**PostUser**](UserApi.md#PostUser) | **Post** /users | Create a user
 
 
 
+## DeleteUser
+
+> DeleteUser(ctx, username).Execute()
+
+Delete a user
+
+### Example
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+    openapiclient "./openapi"
+)
+
+func main() {
+    username := "username_example" // string | The username of the user
+
+    configuration := openapiclient.NewConfiguration()
+    api_client := openapiclient.NewAPIClient(configuration)
+    resp, r, err := api_client.UserApi.DeleteUser(context.Background(), username).Execute()
+    if err != nil {
+        fmt.Fprintf(os.Stderr, "Error when calling `UserApi.DeleteUser``: %v\n", err)
+        fmt.Fprintf(os.Stderr, "Full HTTP response: %v\n", r)
+    }
+}
+```
+
+### Path Parameters
+
+
+Name | Type | Description  | Notes
+------------- | ------------- | ------------- | -------------
+**ctx** | **context.Context** | context for authentication, logging, cancellation, deadlines, tracing, etc.
+**username** | **string** | The username of the user | 
+
+### Other Parameters
+
+Other parameters are passed through a pointer to a apiDeleteUserRequest struct via the builder pattern
+
+
+Name | Type | Description  | Notes
+------------- | ------------- | ------------- | -------------
+
+
+### Return type
+
+ (empty response body)
+
+### Authorization
+
+No authorization required
+
+### HTTP request headers
+
+- **Content-Type**: Not defined
+- **Accept**: application/json
+
+[[Back to top]](#) [[Back to API list]](../README.md#documentation-for-api-endpoints)
+[[Back to Model list]](../README.md#documentation-for-models)
+[[Back to README]](../README.md)
+
+
 ## GetUser
 
 > UserCollectionItem GetUser(ctx, username).Execute()
@@ -163,3 +232,139 @@ No authorization required
 [[Back to Model list]](../README.md#documentation-for-models)
 [[Back to README]](../README.md)
 
+
+## PatchUser
+
+> Role PatchUser(ctx, username).User(user).UpdateMask(updateMask).Execute()
+
+Update a user
+
+### Example
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+    openapiclient "./openapi"
+)
+
+func main() {
+    username := "username_example" // string | The username of the user
+    user := *openapiclient.NewUser() // User | 
+    updateMask := []string{"Inner_example"} // []string | The fields to update on the resource. If absent or empty, all modifiable fields are updated. A comma-separated list of fully qualified names of fields.  (optional)
+
+    configuration := openapiclient.NewConfiguration()
+    api_client := openapiclient.NewAPIClient(configuration)
+    resp, r, err := api_client.UserApi.PatchUser(context.Background(), username).User(user).UpdateMask(updateMask).Execute()
+    if err != nil {
+        fmt.Fprintf(os.Stderr, "Error when calling `UserApi.PatchUser``: %v\n", err)
+        fmt.Fprintf(os.Stderr, "Full HTTP response: %v\n", r)
+    }
+    // response from `PatchUser`: Role
+    fmt.Fprintf(os.Stdout, "Response from `UserApi.PatchUser`: %v\n", resp)
+}
+```
+
+### Path Parameters
+
+
+Name | Type | Description  | Notes
+------------- | ------------- | ------------- | -------------
+**ctx** | **context.Context** | context for authentication, logging, cancellation, deadlines, tracing, etc.
+**username** | **string** | The username of the user | 
+
+### Other Parameters
+
+Other parameters are passed through a pointer to a apiPatchUserRequest struct via the builder pattern
+
+
+Name | Type | Description  | Notes
+------------- | ------------- | ------------- | -------------
+
+ **user** | [**User**](User.md) |  | 
+ **updateMask** | **[]string** | The fields to update on the resource. If absent or empty, all modifiable fields are updated. A comma-separated list of fully qualified names of fields.  | 
+
+### Return type
+
+[**Role**](Role.md)
+
+### Authorization
+
+No authorization required
+
+### HTTP request headers
+
+- **Content-Type**: application/json
+- **Accept**: application/json
+
+[[Back to top]](#) [[Back to API list]](../README.md#documentation-for-api-endpoints)
+[[Back to Model list]](../README.md#documentation-for-models)
+[[Back to README]](../README.md)
+
+
+## PostUser
+
+> User PostUser(ctx).User(user).Execute()
+
+Create a user
+
+### Example
+
+```go
+package main
+
+import (
+    "context"
+    "fmt"
+    "os"
+    openapiclient "./openapi"
+)
+
+func main() {
+    user := *openapiclient.NewUser() // User | 
+
+    configuration := openapiclient.NewConfiguration()
+    api_client := openapiclient.NewAPIClient(configuration)
+    resp, r, err := api_client.UserApi.PostUser(context.Background()).User(user).Execute()
+    if err != nil {
+        fmt.Fprintf(os.Stderr, "Error when calling `UserApi.PostUser``: %v\n", err)
+        fmt.Fprintf(os.Stderr, "Full HTTP response: %v\n", r)
+    }
+    // response from `PostUser`: User
+    fmt.Fprintf(os.Stdout, "Response from `UserApi.PostUser`: %v\n", resp)
+}
+```
+
+### Path Parameters
+
+
+
+### Other Parameters
+
+Other parameters are passed through a pointer to a apiPostUserRequest struct via the builder pattern
+
+
+Name | Type | Description  | Notes
+------------- | ------------- | ------------- | -------------
+ **user** | [**User**](User.md) |  | 
+
+### Return type
+
+[**User**](User.md)
+
+### Authorization
+
+No authorization required
+
+### HTTP request headers
+
+- **Content-Type**: application/json
+- **Accept**: application/json
+
+[[Back to top]](#) [[Back to API list]](../README.md#documentation-for-api-endpoints)
+[[Back to Model list]](../README.md#documentation-for-models)
+[[Back to README]](../README.md)
+
diff --git a/airflow/docs/UserCollectionItem.md b/airflow/docs/UserCollectionItem.md
index 5f25dfb..b2ee2bf 100644
--- a/airflow/docs/UserCollectionItem.md
+++ b/airflow/docs/UserCollectionItem.md
@@ -31,7 +31,7 @@ Name | Type | Description | Notes
 **LastLogin** | Pointer to **NullableString** | The last user login | [optional] [readonly] 
 **LoginCount** | Pointer to **NullableInt32** | The login count | [optional] [readonly] 
 **FailedLoginCount** | Pointer to **NullableInt32** | The number of times the login failed | [optional] [readonly] 
-**Roles** | Pointer to [**[]UserCollectionItemRoles**](UserCollectionItemRoles.md) | User roles | [optional] [readonly] 
+**Roles** | Pointer to [**[]UserCollectionItemRoles**](UserCollectionItemRoles.md) | User roles | [optional] 
 **CreatedOn** | Pointer to **NullableString** | The date user was created | [optional] [readonly] 
 **ChangedOn** | Pointer to **NullableString** | The date user was changed | [optional] [readonly] 
 
diff --git a/airflow/model_action.go b/airflow/model_action.go
index a1846d7..a304eea 100644
--- a/airflow/model_action.go
+++ b/airflow/model_action.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
diff --git a/airflow/model_action_collection.go b/airflow/model_action_collection.go
index 7033697..5c4b710 100644
--- a/airflow/model_action_collection.go
+++ b/airflow/model_action_collection.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
diff --git a/airflow/model_action_collection_all_of.go b/airflow/model_action_collection_all_of.go
index 7f9e144..ff7407e 100644
--- a/airflow/model_action_collection_all_of.go
+++ b/airflow/model_action_collection_all_of.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
diff --git a/airflow/model_action_resource.go b/airflow/model_action_resource.go
index e9462e4..e4e1f7d 100644
--- a/airflow/model_action_resource.go
+++ b/airflow/model_action_resource.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
diff --git a/airflow/model_class_reference.go b/airflow/model_class_reference.go
index 4d6eeb8..88e8d58 100644
--- a/airflow/model_class_reference.go
+++ b/airflow/model_class_reference.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
diff --git a/airflow/model_clear_task_instance.go b/airflow/model_clear_task_instance.go
index 78b5001..a4ed996 100644
--- a/airflow/model_clear_task_instance.go
+++ b/airflow/model_clear_task_instance.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
diff --git a/airflow/model_collection_info.go b/airflow/model_collection_info.go
index 0b9b662..24aa726 100644
--- a/airflow/model_collection_info.go
+++ b/airflow/model_collection_info.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
diff --git a/airflow/model_config.go b/airflow/model_config.go
index c62d60c..e498271 100644
--- a/airflow/model_config.go
+++ b/airflow/model_config.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
diff --git a/airflow/model_config_option.go b/airflow/model_config_option.go
index df13389..f09a7e4 100644
--- a/airflow/model_config_option.go
+++ b/airflow/model_config_option.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
diff --git a/airflow/model_config_section.go b/airflow/model_config_section.go
index 18ef6a9..6b1ad47 100644
--- a/airflow/model_config_section.go
+++ b/airflow/model_config_section.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
diff --git a/airflow/model_connection.go b/airflow/model_connection.go
index 95a79fc..cd8f038 100644
--- a/airflow/model_connection.go
+++ b/airflow/model_connection.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
@@ -46,7 +46,7 @@ type Connection struct {
 	Schema NullableString `json:"schema,omitempty"`
 	// Port of the connection.
 	Port NullableInt32 `json:"port,omitempty"`
-	// Paasword of the connection.
+	// Password of the connection.
 	Password *string `json:"password,omitempty"`
 	// Other values that cannot be put into another field, e.g. RSA keys.
 	Extra NullableString `json:"extra,omitempty"`
diff --git a/airflow/model_connection_all_of.go b/airflow/model_connection_all_of.go
index 270c61b..b240efe 100644
--- a/airflow/model_connection_all_of.go
+++ b/airflow/model_connection_all_of.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
@@ -34,7 +34,7 @@ import (
 
 // ConnectionAllOf struct for ConnectionAllOf
 type ConnectionAllOf struct {
-	// Paasword of the connection.
+	// Password of the connection.
 	Password *string `json:"password,omitempty"`
 	// Other values that cannot be put into another field, e.g. RSA keys.
 	Extra NullableString `json:"extra,omitempty"`
diff --git a/airflow/model_connection_collection.go b/airflow/model_connection_collection.go
index 9e35737..4845af0 100644
--- a/airflow/model_connection_collection.go
+++ b/airflow/model_connection_collection.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
diff --git a/airflow/model_connection_collection_all_of.go b/airflow/model_connection_collection_all_of.go
index f3bc98e..91f6a57 100644
--- a/airflow/model_connection_collection_all_of.go
+++ b/airflow/model_connection_collection_all_of.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
diff --git a/airflow/model_connection_collection_item.go b/airflow/model_connection_collection_item.go
index 348e267..a3d61c9 100644
--- a/airflow/model_connection_collection_item.go
+++ b/airflow/model_connection_collection_item.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
diff --git a/airflow/model_metadatabase_status.go b/airflow/model_connection_test_.go
similarity index 53%
copy from airflow/model_metadatabase_status.go
copy to airflow/model_connection_test_.go
index 4c69e8b..9f22140 100644
--- a/airflow/model_metadatabase_status.go
+++ b/airflow/model_connection_test_.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
@@ -32,32 +32,35 @@ import (
 	"encoding/json"
 )
 
-// MetadatabaseStatus The status of the metadatabase.
-type MetadatabaseStatus struct {
-	Status *HealthStatus `json:"status,omitempty"`
+// ConnectionTest Connection test results.
+type ConnectionTest struct {
+	// The status of the request.
+	Status *bool `json:"status,omitempty"`
+	// The success or failure message of the request.
+	Message *string `json:"message,omitempty"`
 }
 
-// NewMetadatabaseStatus instantiates a new MetadatabaseStatus object
+// NewConnectionTest instantiates a new ConnectionTest object
 // This constructor will assign default values to properties that have it defined,
 // and makes sure properties required by API are set, but the set of arguments
 // will change when the set of required properties is changed
-func NewMetadatabaseStatus() *MetadatabaseStatus {
-	this := MetadatabaseStatus{}
+func NewConnectionTest() *ConnectionTest {
+	this := ConnectionTest{}
 	return &this
 }
 
-// NewMetadatabaseStatusWithDefaults instantiates a new MetadatabaseStatus object
+// NewConnectionTestWithDefaults instantiates a new ConnectionTest object
 // This constructor will only assign default values to properties that have it defined,
 // but it doesn't guarantee that properties required by API are set
-func NewMetadatabaseStatusWithDefaults() *MetadatabaseStatus {
-	this := MetadatabaseStatus{}
+func NewConnectionTestWithDefaults() *ConnectionTest {
+	this := ConnectionTest{}
 	return &this
 }
 
 // GetStatus returns the Status field value if set, zero value otherwise.
-func (o *MetadatabaseStatus) GetStatus() HealthStatus {
+func (o *ConnectionTest) GetStatus() bool {
 	if o == nil || o.Status == nil {
-		var ret HealthStatus
+		var ret bool
 		return ret
 	}
 	return *o.Status
@@ -65,7 +68,7 @@ func (o *MetadatabaseStatus) GetStatus() HealthStatus {
 
 // GetStatusOk returns a tuple with the Status field value if set, nil otherwise
 // and a boolean to check if the value has been set.
-func (o *MetadatabaseStatus) GetStatusOk() (*HealthStatus, bool) {
+func (o *ConnectionTest) GetStatusOk() (*bool, bool) {
 	if o == nil || o.Status == nil {
 		return nil, false
 	}
@@ -73,7 +76,7 @@ func (o *MetadatabaseStatus) GetStatusOk() (*HealthStatus, bool) {
 }
 
 // HasStatus returns a boolean if a field has been set.
-func (o *MetadatabaseStatus) HasStatus() bool {
+func (o *ConnectionTest) HasStatus() bool {
 	if o != nil && o.Status != nil {
 		return true
 	}
@@ -81,51 +84,86 @@ func (o *MetadatabaseStatus) HasStatus() bool {
 	return false
 }
 
-// SetStatus gets a reference to the given HealthStatus and assigns it to the Status field.
-func (o *MetadatabaseStatus) SetStatus(v HealthStatus) {
+// SetStatus gets a reference to the given bool and assigns it to the Status field.
+func (o *ConnectionTest) SetStatus(v bool) {
 	o.Status = &v
 }
 
-func (o MetadatabaseStatus) MarshalJSON() ([]byte, error) {
+// GetMessage returns the Message field value if set, zero value otherwise.
+func (o *ConnectionTest) GetMessage() string {
+	if o == nil || o.Message == nil {
+		var ret string
+		return ret
+	}
+	return *o.Message
+}
+
+// GetMessageOk returns a tuple with the Message field value if set, nil otherwise
+// and a boolean to check if the value has been set.
+func (o *ConnectionTest) GetMessageOk() (*string, bool) {
+	if o == nil || o.Message == nil {
+		return nil, false
+	}
+	return o.Message, true
+}
+
+// HasMessage returns a boolean if a field has been set.
+func (o *ConnectionTest) HasMessage() bool {
+	if o != nil && o.Message != nil {
+		return true
+	}
+
+	return false
+}
+
+// SetMessage gets a reference to the given string and assigns it to the Message field.
+func (o *ConnectionTest) SetMessage(v string) {
+	o.Message = &v
+}
+
+func (o ConnectionTest) MarshalJSON() ([]byte, error) {
 	toSerialize := map[string]interface{}{}
 	if o.Status != nil {
 		toSerialize["status"] = o.Status
 	}
+	if o.Message != nil {
+		toSerialize["message"] = o.Message
+	}
 	return json.Marshal(toSerialize)
 }
 
-type NullableMetadatabaseStatus struct {
-	value *MetadatabaseStatus
+type NullableConnectionTest struct {
+	value *ConnectionTest
 	isSet bool
 }
 
-func (v NullableMetadatabaseStatus) Get() *MetadatabaseStatus {
+func (v NullableConnectionTest) Get() *ConnectionTest {
 	return v.value
 }
 
-func (v *NullableMetadatabaseStatus) Set(val *MetadatabaseStatus) {
+func (v *NullableConnectionTest) Set(val *ConnectionTest) {
 	v.value = val
 	v.isSet = true
 }
 
-func (v NullableMetadatabaseStatus) IsSet() bool {
+func (v NullableConnectionTest) IsSet() bool {
 	return v.isSet
 }
 
-func (v *NullableMetadatabaseStatus) Unset() {
+func (v *NullableConnectionTest) Unset() {
 	v.value = nil
 	v.isSet = false
 }
 
-func NewNullableMetadatabaseStatus(val *MetadatabaseStatus) *NullableMetadatabaseStatus {
-	return &NullableMetadatabaseStatus{value: val, isSet: true}
+func NewNullableConnectionTest(val *ConnectionTest) *NullableConnectionTest {
+	return &NullableConnectionTest{value: val, isSet: true}
 }
 
-func (v NullableMetadatabaseStatus) MarshalJSON() ([]byte, error) {
+func (v NullableConnectionTest) MarshalJSON() ([]byte, error) {
 	return json.Marshal(v.value)
 }
 
-func (v *NullableMetadatabaseStatus) UnmarshalJSON(src []byte) error {
+func (v *NullableConnectionTest) UnmarshalJSON(src []byte) error {
 	v.isSet = true
 	return json.Unmarshal(src, &v.value)
 }
diff --git a/airflow/model_cron_expression.go b/airflow/model_cron_expression.go
index bb83617..27322a4 100644
--- a/airflow/model_cron_expression.go
+++ b/airflow/model_cron_expression.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
diff --git a/airflow/model_dag.go b/airflow/model_dag.go
index b630ab2..f423871 100644
--- a/airflow/model_dag.go
+++ b/airflow/model_dag.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
@@ -40,6 +40,8 @@ type DAG struct {
 	RootDagId NullableString `json:"root_dag_id,omitempty"`
 	// Whether the DAG is paused.
 	IsPaused NullableBool `json:"is_paused,omitempty"`
+	// Whether the DAG is currently seen by the scheduler(s).
+	IsActive NullableBool `json:"is_active,omitempty"`
 	// Whether the DAG is SubDAG.
 	IsSubdag *bool `json:"is_subdag,omitempty"`
 	// The absolute path to the file.
@@ -187,6 +189,48 @@ func (o *DAG) UnsetIsPaused() {
 	o.IsPaused.Unset()
 }
 
+// GetIsActive returns the IsActive field value if set, zero value otherwise (both if not set or set to explicit null).
+func (o *DAG) GetIsActive() bool {
+	if o == nil || o.IsActive.Get() == nil {
+		var ret bool
+		return ret
+	}
+	return *o.IsActive.Get()
+}
+
+// GetIsActiveOk returns a tuple with the IsActive field value if set, nil otherwise
+// and a boolean to check if the value has been set.
+// NOTE: If the value is an explicit nil, `nil, true` will be returned
+func (o *DAG) GetIsActiveOk() (*bool, bool) {
+	if o == nil  {
+		return nil, false
+	}
+	return o.IsActive.Get(), o.IsActive.IsSet()
+}
+
+// HasIsActive returns a boolean if a field has been set.
+func (o *DAG) HasIsActive() bool {
+	if o != nil && o.IsActive.IsSet() {
+		return true
+	}
+
+	return false
+}
+
+// SetIsActive gets a reference to the given NullableBool and assigns it to the IsActive field.
+func (o *DAG) SetIsActive(v bool) {
+	o.IsActive.Set(&v)
+}
+// SetIsActiveNil sets the value for IsActive to be an explicit nil
+func (o *DAG) SetIsActiveNil() {
+	o.IsActive.Set(nil)
+}
+
+// UnsetIsActive ensures that no value is present for IsActive, not even an explicit nil
+func (o *DAG) UnsetIsActive() {
+	o.IsActive.Unset()
+}
+
 // GetIsSubdag returns the IsSubdag field value if set, zero value otherwise.
 func (o *DAG) GetIsSubdag() bool {
 	if o == nil || o.IsSubdag == nil {
@@ -433,6 +477,9 @@ func (o DAG) MarshalJSON() ([]byte, error) {
 	if o.IsPaused.IsSet() {
 		toSerialize["is_paused"] = o.IsPaused.Get()
 	}
+	if o.IsActive.IsSet() {
+		toSerialize["is_active"] = o.IsActive.Get()
+	}
 	if o.IsSubdag != nil {
 		toSerialize["is_subdag"] = o.IsSubdag
 	}
diff --git a/airflow/model_dag_collection.go b/airflow/model_dag_collection.go
index 2eeac8f..e41e041 100644
--- a/airflow/model_dag_collection.go
+++ b/airflow/model_dag_collection.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
diff --git a/airflow/model_dag_collection_all_of.go b/airflow/model_dag_collection_all_of.go
index 9e6e7e2..b0ef4f2 100644
--- a/airflow/model_dag_collection_all_of.go
+++ b/airflow/model_dag_collection_all_of.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
diff --git a/airflow/model_dag_detail.go b/airflow/model_dag_detail.go
index fddfeea..048c32e 100644
--- a/airflow/model_dag_detail.go
+++ b/airflow/model_dag_detail.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
@@ -41,6 +41,8 @@ type DAGDetail struct {
 	RootDagId NullableString `json:"root_dag_id,omitempty"`
 	// Whether the DAG is paused.
 	IsPaused NullableBool `json:"is_paused,omitempty"`
+	// Whether the DAG is currently seen by the scheduler(s).
+	IsActive NullableBool `json:"is_active,omitempty"`
 	// Whether the DAG is SubDAG.
 	IsSubdag *bool `json:"is_subdag,omitempty"`
 	// The absolute path to the file.
@@ -197,6 +199,48 @@ func (o *DAGDetail) UnsetIsPaused() {
 	o.IsPaused.Unset()
 }
 
+// GetIsActive returns the IsActive field value if set, zero value otherwise (both if not set or set to explicit null).
+func (o *DAGDetail) GetIsActive() bool {
+	if o == nil || o.IsActive.Get() == nil {
+		var ret bool
+		return ret
+	}
+	return *o.IsActive.Get()
+}
+
+// GetIsActiveOk returns a tuple with the IsActive field value if set, nil otherwise
+// and a boolean to check if the value has been set.
+// NOTE: If the value is an explicit nil, `nil, true` will be returned
+func (o *DAGDetail) GetIsActiveOk() (*bool, bool) {
+	if o == nil  {
+		return nil, false
+	}
+	return o.IsActive.Get(), o.IsActive.IsSet()
+}
+
+// HasIsActive returns a boolean if a field has been set.
+func (o *DAGDetail) HasIsActive() bool {
+	if o != nil && o.IsActive.IsSet() {
+		return true
+	}
+
+	return false
+}
+
+// SetIsActive gets a reference to the given NullableBool and assigns it to the IsActive field.
+func (o *DAGDetail) SetIsActive(v bool) {
+	o.IsActive.Set(&v)
+}
+// SetIsActiveNil sets the value for IsActive to be an explicit nil
+func (o *DAGDetail) SetIsActiveNil() {
+	o.IsActive.Set(nil)
+}
+
+// UnsetIsActive ensures that no value is present for IsActive, not even an explicit nil
+func (o *DAGDetail) UnsetIsActive() {
+	o.IsActive.Unset()
+}
+
 // GetIsSubdag returns the IsSubdag field value if set, zero value otherwise.
 func (o *DAGDetail) GetIsSubdag() bool {
 	if o == nil || o.IsSubdag == nil {
@@ -751,6 +795,9 @@ func (o DAGDetail) MarshalJSON() ([]byte, error) {
 	if o.IsPaused.IsSet() {
 		toSerialize["is_paused"] = o.IsPaused.Get()
 	}
+	if o.IsActive.IsSet() {
+		toSerialize["is_active"] = o.IsActive.Get()
+	}
 	if o.IsSubdag != nil {
 		toSerialize["is_subdag"] = o.IsSubdag
 	}
diff --git a/airflow/model_dag_detail_all_of.go b/airflow/model_dag_detail_all_of.go
index 4aeed6b..dd0878b 100644
--- a/airflow/model_dag_detail_all_of.go
+++ b/airflow/model_dag_detail_all_of.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
diff --git a/airflow/model_dag_run.go b/airflow/model_dag_run.go
index 814e275..96406ca 100644
--- a/airflow/model_dag_run.go
+++ b/airflow/model_dag_run.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
@@ -38,10 +38,12 @@ type DAGRun struct {
 	// Run ID.  The value of this field can be set only when creating the object. If you try to modify the field of an existing object, the request fails with an BAD_REQUEST error.  If not provided, a value will be generated based on execution_date.  If the specified dag_run_id is in use, the creation request fails with an ALREADY_EXISTS error.  This together with DAG_ID are a unique key. 
 	DagRunId NullableString `json:"dag_run_id,omitempty"`
 	DagId string `json:"dag_id"`
-	// The execution date. This is the time when the DAG run should be started according to the DAG definition. The value of this field can be set only when creating the object. If you try to modify the field of an existing object, the request fails with an BAD_REQUEST error. This together with DAG_ID are a unique key. 
-	ExecutionDate *time.Time `json:"execution_date,omitempty"`
+	// The logical date (previously called execution date). This is the time or interval covered by this DAG run, according to the DAG definition.  The value of this field can be set only when creating the object. If you try to modify the field of an existing object, the request fails with an BAD_REQUEST error.  This together with DAG_ID are a unique key. 
+	LogicalDate NullableTime `json:"logical_date,omitempty"`
+	// The execution date. This is the same as logical_date, kept for backwards compatibility. If both this field and logical_date are provided but with different values, the request will fail with an BAD_REQUEST error. 
+	ExecutionDate NullableTime `json:"execution_date,omitempty"`
 	// The start time. The time when DAG run was actually created. 
-	StartDate *time.Time `json:"start_date,omitempty"`
+	StartDate NullableTime `json:"start_date,omitempty"`
 	EndDate NullableTime `json:"end_date,omitempty"`
 	State *DagState `json:"state,omitempty"`
 	ExternalTrigger *bool `json:"external_trigger,omitempty"`
@@ -137,68 +139,130 @@ func (o *DAGRun) SetDagId(v string) {
 	o.DagId = v
 }
 
-// GetExecutionDate returns the ExecutionDate field value if set, zero value otherwise.
+// GetLogicalDate returns the LogicalDate field value if set, zero value otherwise (both if not set or set to explicit null).
+func (o *DAGRun) GetLogicalDate() time.Time {
+	if o == nil || o.LogicalDate.Get() == nil {
+		var ret time.Time
+		return ret
+	}
+	return *o.LogicalDate.Get()
+}
+
+// GetLogicalDateOk returns a tuple with the LogicalDate field value if set, nil otherwise
+// and a boolean to check if the value has been set.
+// NOTE: If the value is an explicit nil, `nil, true` will be returned
+func (o *DAGRun) GetLogicalDateOk() (*time.Time, bool) {
+	if o == nil  {
+		return nil, false
+	}
+	return o.LogicalDate.Get(), o.LogicalDate.IsSet()
+}
+
+// HasLogicalDate returns a boolean if a field has been set.
+func (o *DAGRun) HasLogicalDate() bool {
+	if o != nil && o.LogicalDate.IsSet() {
+		return true
+	}
+
+	return false
+}
+
+// SetLogicalDate gets a reference to the given NullableTime and assigns it to the LogicalDate field.
+func (o *DAGRun) SetLogicalDate(v time.Time) {
+	o.LogicalDate.Set(&v)
+}
+// SetLogicalDateNil sets the value for LogicalDate to be an explicit nil
+func (o *DAGRun) SetLogicalDateNil() {
+	o.LogicalDate.Set(nil)
+}
+
+// UnsetLogicalDate ensures that no value is present for LogicalDate, not even an explicit nil
+func (o *DAGRun) UnsetLogicalDate() {
+	o.LogicalDate.Unset()
+}
+
+// GetExecutionDate returns the ExecutionDate field value if set, zero value otherwise (both if not set or set to explicit null).
 func (o *DAGRun) GetExecutionDate() time.Time {
-	if o == nil || o.ExecutionDate == nil {
+	if o == nil || o.ExecutionDate.Get() == nil {
 		var ret time.Time
 		return ret
 	}
-	return *o.ExecutionDate
+	return *o.ExecutionDate.Get()
 }
 
 // GetExecutionDateOk returns a tuple with the ExecutionDate field value if set, nil otherwise
 // and a boolean to check if the value has been set.
+// NOTE: If the value is an explicit nil, `nil, true` will be returned
 func (o *DAGRun) GetExecutionDateOk() (*time.Time, bool) {
-	if o == nil || o.ExecutionDate == nil {
+	if o == nil  {
 		return nil, false
 	}
-	return o.ExecutionDate, true
+	return o.ExecutionDate.Get(), o.ExecutionDate.IsSet()
 }
 
 // HasExecutionDate returns a boolean if a field has been set.
 func (o *DAGRun) HasExecutionDate() bool {
-	if o != nil && o.ExecutionDate != nil {
+	if o != nil && o.ExecutionDate.IsSet() {
 		return true
 	}
 
 	return false
 }
 
-// SetExecutionDate gets a reference to the given time.Time and assigns it to the ExecutionDate field.
+// SetExecutionDate gets a reference to the given NullableTime and assigns it to the ExecutionDate field.
 func (o *DAGRun) SetExecutionDate(v time.Time) {
-	o.ExecutionDate = &v
+	o.ExecutionDate.Set(&v)
+}
+// SetExecutionDateNil sets the value for ExecutionDate to be an explicit nil
+func (o *DAGRun) SetExecutionDateNil() {
+	o.ExecutionDate.Set(nil)
 }
 
-// GetStartDate returns the StartDate field value if set, zero value otherwise.
+// UnsetExecutionDate ensures that no value is present for ExecutionDate, not even an explicit nil
+func (o *DAGRun) UnsetExecutionDate() {
+	o.ExecutionDate.Unset()
+}
+
+// GetStartDate returns the StartDate field value if set, zero value otherwise (both if not set or set to explicit null).
 func (o *DAGRun) GetStartDate() time.Time {
-	if o == nil || o.StartDate == nil {
+	if o == nil || o.StartDate.Get() == nil {
 		var ret time.Time
 		return ret
 	}
-	return *o.StartDate
+	return *o.StartDate.Get()
 }
 
 // GetStartDateOk returns a tuple with the StartDate field value if set, nil otherwise
 // and a boolean to check if the value has been set.
+// NOTE: If the value is an explicit nil, `nil, true` will be returned
 func (o *DAGRun) GetStartDateOk() (*time.Time, bool) {
-	if o == nil || o.StartDate == nil {
+	if o == nil  {
 		return nil, false
 	}
-	return o.StartDate, true
+	return o.StartDate.Get(), o.StartDate.IsSet()
 }
 
 // HasStartDate returns a boolean if a field has been set.
 func (o *DAGRun) HasStartDate() bool {
-	if o != nil && o.StartDate != nil {
+	if o != nil && o.StartDate.IsSet() {
 		return true
 	}
 
 	return false
 }
 
-// SetStartDate gets a reference to the given time.Time and assigns it to the StartDate field.
+// SetStartDate gets a reference to the given NullableTime and assigns it to the StartDate field.
 func (o *DAGRun) SetStartDate(v time.Time) {
-	o.StartDate = &v
+	o.StartDate.Set(&v)
+}
+// SetStartDateNil sets the value for StartDate to be an explicit nil
+func (o *DAGRun) SetStartDateNil() {
+	o.StartDate.Set(nil)
+}
+
+// UnsetStartDate ensures that no value is present for StartDate, not even an explicit nil
+func (o *DAGRun) UnsetStartDate() {
+	o.StartDate.Unset()
 }
 
 // GetEndDate returns the EndDate field value if set, zero value otherwise (both if not set or set to explicit null).
@@ -347,11 +411,14 @@ func (o DAGRun) MarshalJSON() ([]byte, error) {
 	if true {
 		toSerialize["dag_id"] = o.DagId
 	}
-	if o.ExecutionDate != nil {
-		toSerialize["execution_date"] = o.ExecutionDate
+	if o.LogicalDate.IsSet() {
+		toSerialize["logical_date"] = o.LogicalDate.Get()
+	}
+	if o.ExecutionDate.IsSet() {
+		toSerialize["execution_date"] = o.ExecutionDate.Get()
 	}
-	if o.StartDate != nil {
-		toSerialize["start_date"] = o.StartDate
+	if o.StartDate.IsSet() {
+		toSerialize["start_date"] = o.StartDate.Get()
 	}
 	if o.EndDate.IsSet() {
 		toSerialize["end_date"] = o.EndDate.Get()
diff --git a/airflow/model_dag_run_collection.go b/airflow/model_dag_run_collection.go
index a02efd5..c89bd6f 100644
--- a/airflow/model_dag_run_collection.go
+++ b/airflow/model_dag_run_collection.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
diff --git a/airflow/model_dag_run_collection_all_of.go b/airflow/model_dag_run_collection_all_of.go
index 13219fb..92a90ac 100644
--- a/airflow/model_dag_run_collection_all_of.go
+++ b/airflow/model_dag_run_collection_all_of.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
diff --git a/airflow/model_dag_state.go b/airflow/model_dag_state.go
index 7fb578c..aa0cd33 100644
--- a/airflow/model_dag_state.go
+++ b/airflow/model_dag_state.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
@@ -38,14 +38,16 @@ type DagState string
 
 // List of DagState
 const (
-	DAGSTATE_SUCCESS DagState = "success"
+	DAGSTATE_QUEUED DagState = "queued"
 	DAGSTATE_RUNNING DagState = "running"
+	DAGSTATE_SUCCESS DagState = "success"
 	DAGSTATE_FAILED DagState = "failed"
 )
 
 var allowedDagStateEnumValues = []DagState{
-	"success",
+	"queued",
 	"running",
+	"success",
 	"failed",
 }
 
diff --git a/airflow/model_error.go b/airflow/model_error.go
index fda1eb2..481cac9 100644
--- a/airflow/model_error.go
+++ b/airflow/model_error.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
diff --git a/airflow/model_event_log.go b/airflow/model_event_log.go
index a2dec08..646df44 100644
--- a/airflow/model_event_log.go
+++ b/airflow/model_event_log.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
diff --git a/airflow/model_event_log_collection.go b/airflow/model_event_log_collection.go
index 60a3724..6fe5cd9 100644
--- a/airflow/model_event_log_collection.go
+++ b/airflow/model_event_log_collection.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
diff --git a/airflow/model_event_log_collection_all_of.go b/airflow/model_event_log_collection_all_of.go
index 968bc33..b8d0188 100644
--- a/airflow/model_event_log_collection_all_of.go
+++ b/airflow/model_event_log_collection_all_of.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
diff --git a/airflow/model_extra_link.go b/airflow/model_extra_link.go
index 7f14061..bd6d5a7 100644
--- a/airflow/model_extra_link.go
+++ b/airflow/model_extra_link.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
diff --git a/airflow/model_extra_link_collection.go b/airflow/model_extra_link_collection.go
index af76bbb..40729ee 100644
--- a/airflow/model_extra_link_collection.go
+++ b/airflow/model_extra_link_collection.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
diff --git a/airflow/model_health_info.go b/airflow/model_health_info.go
index 8a7d467..1484bf3 100644
--- a/airflow/model_health_info.go
+++ b/airflow/model_health_info.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
diff --git a/airflow/model_health_status.go b/airflow/model_health_status.go
index f90e480..a195288 100644
--- a/airflow/model_health_status.go
+++ b/airflow/model_health_status.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
diff --git a/airflow/model_import_error.go b/airflow/model_import_error.go
index c684256..024bf36 100644
--- a/airflow/model_import_error.go
+++ b/airflow/model_import_error.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
diff --git a/airflow/model_import_error_collection.go b/airflow/model_import_error_collection.go
index 553b242..0de3c32 100644
--- a/airflow/model_import_error_collection.go
+++ b/airflow/model_import_error_collection.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
diff --git a/airflow/model_import_error_collection_all_of.go b/airflow/model_import_error_collection_all_of.go
index 3fce58e..fc0a12b 100644
--- a/airflow/model_import_error_collection_all_of.go
+++ b/airflow/model_import_error_collection_all_of.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
diff --git a/airflow/model_inline_response_200.go b/airflow/model_inline_response_200.go
index be51e5b..45373e9 100644
--- a/airflow/model_inline_response_200.go
+++ b/airflow/model_inline_response_200.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
diff --git a/airflow/model_inline_response_200_1.go b/airflow/model_inline_response_200_1.go
index 700aed6..9f510c3 100644
--- a/airflow/model_inline_response_200_1.go
+++ b/airflow/model_inline_response_200_1.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
diff --git a/airflow/model_list_dag_runs_form.go b/airflow/model_list_dag_runs_form.go
index 78f7fac..74a021e 100644
--- a/airflow/model_list_dag_runs_form.go
+++ b/airflow/model_list_dag_runs_form.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
diff --git a/airflow/model_list_task_instance_form.go b/airflow/model_list_task_instance_form.go
index d47dd52..d482a3c 100644
--- a/airflow/model_list_task_instance_form.go
+++ b/airflow/model_list_task_instance_form.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
diff --git a/airflow/model_metadatabase_status.go b/airflow/model_metadatabase_status.go
index 4c69e8b..9563a2f 100644
--- a/airflow/model_metadatabase_status.go
+++ b/airflow/model_metadatabase_status.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
diff --git a/airflow/model_plugin_collection.go b/airflow/model_plugin_collection.go
index 3a55c6b..3286813 100644
--- a/airflow/model_plugin_collection.go
+++ b/airflow/model_plugin_collection.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
diff --git a/airflow/model_plugin_collection_all_of.go b/airflow/model_plugin_collection_all_of.go
index a85de89..e2f8706 100644
--- a/airflow/model_plugin_collection_all_of.go
+++ b/airflow/model_plugin_collection_all_of.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
diff --git a/airflow/model_plugin_collection_item.go b/airflow/model_plugin_collection_item.go
index 73e7179..90b5d58 100644
--- a/airflow/model_plugin_collection_item.go
+++ b/airflow/model_plugin_collection_item.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
diff --git a/airflow/model_pool.go b/airflow/model_pool.go
index d6134f2..52f72f8 100644
--- a/airflow/model_pool.go
+++ b/airflow/model_pool.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
diff --git a/airflow/model_pool_collection.go b/airflow/model_pool_collection.go
index 3609416..bc54d7c 100644
--- a/airflow/model_pool_collection.go
+++ b/airflow/model_pool_collection.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
diff --git a/airflow/model_pool_collection_all_of.go b/airflow/model_pool_collection_all_of.go
index bf86f2f..e914351 100644
--- a/airflow/model_pool_collection_all_of.go
+++ b/airflow/model_pool_collection_all_of.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
diff --git a/airflow/model_provider.go b/airflow/model_provider.go
index d772fb7..600735d 100644
--- a/airflow/model_provider.go
+++ b/airflow/model_provider.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
diff --git a/airflow/model_provider_collection.go b/airflow/model_provider_collection.go
index 50903fc..f7ff0c6 100644
--- a/airflow/model_provider_collection.go
+++ b/airflow/model_provider_collection.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
diff --git a/airflow/model_relative_delta.go b/airflow/model_relative_delta.go
index 97a2ea7..59f9afe 100644
--- a/airflow/model_relative_delta.go
+++ b/airflow/model_relative_delta.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
diff --git a/airflow/model_resource.go b/airflow/model_resource.go
index d88e9d6..f6b9516 100644
--- a/airflow/model_resource.go
+++ b/airflow/model_resource.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
diff --git a/airflow/model_role.go b/airflow/model_role.go
index d250a9f..09ddac2 100644
--- a/airflow/model_role.go
+++ b/airflow/model_role.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
diff --git a/airflow/model_role_collection.go b/airflow/model_role_collection.go
index db46294..06272f6 100644
--- a/airflow/model_role_collection.go
+++ b/airflow/model_role_collection.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
diff --git a/airflow/model_role_collection_all_of.go b/airflow/model_role_collection_all_of.go
index f50104c..458a3b4 100644
--- a/airflow/model_role_collection_all_of.go
+++ b/airflow/model_role_collection_all_of.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
diff --git a/airflow/model_schedule_interval.go b/airflow/model_schedule_interval.go
index 02248c5..97937c3 100644
--- a/airflow/model_schedule_interval.go
+++ b/airflow/model_schedule_interval.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
diff --git a/airflow/model_scheduler_status.go b/airflow/model_scheduler_status.go
index 608e0a8..ad2e5fe 100644
--- a/airflow/model_scheduler_status.go
+++ b/airflow/model_scheduler_status.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
diff --git a/airflow/model_sla_miss.go b/airflow/model_sla_miss.go
index f03264c..26177a4 100644
--- a/airflow/model_sla_miss.go
+++ b/airflow/model_sla_miss.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
diff --git a/airflow/model_tag.go b/airflow/model_tag.go
index 5efb9ba..1d1ef16 100644
--- a/airflow/model_tag.go
+++ b/airflow/model_tag.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
diff --git a/airflow/model_task.go b/airflow/model_task.go
index 65248f4..5c96d6c 100644
--- a/airflow/model_task.go
+++ b/airflow/model_task.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
diff --git a/airflow/model_task_collection.go b/airflow/model_task_collection.go
index 23f0535..9b10b82 100644
--- a/airflow/model_task_collection.go
+++ b/airflow/model_task_collection.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
diff --git a/airflow/model_task_extra_links.go b/airflow/model_task_extra_links.go
index 322070e..52a2d27 100644
--- a/airflow/model_task_extra_links.go
+++ b/airflow/model_task_extra_links.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
diff --git a/airflow/model_task_instance.go b/airflow/model_task_instance.go
index 9dc4b84..b6daa5e 100644
--- a/airflow/model_task_instance.go
+++ b/airflow/model_task_instance.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
@@ -49,7 +49,7 @@ type TaskInstance struct {
 	PoolSlots *int32 `json:"pool_slots,omitempty"`
 	Queue *string `json:"queue,omitempty"`
 	PriorityWeight *int32 `json:"priority_weight,omitempty"`
-	Operator *string `json:"operator,omitempty"`
+	Operator NullableString `json:"operator,omitempty"`
 	QueuedWhen NullableString `json:"queued_when,omitempty"`
 	Pid NullableInt32 `json:"pid,omitempty"`
 	ExecutorConfig *string `json:"executor_config,omitempty"`
@@ -583,36 +583,46 @@ func (o *TaskInstance) SetPriorityWeight(v int32) {
 	o.PriorityWeight = &v
 }
 
-// GetOperator returns the Operator field value if set, zero value otherwise.
+// GetOperator returns the Operator field value if set, zero value otherwise (both if not set or set to explicit null).
 func (o *TaskInstance) GetOperator() string {
-	if o == nil || o.Operator == nil {
+	if o == nil || o.Operator.Get() == nil {
 		var ret string
 		return ret
 	}
-	return *o.Operator
+	return *o.Operator.Get()
 }
 
 // GetOperatorOk returns a tuple with the Operator field value if set, nil otherwise
 // and a boolean to check if the value has been set.
+// NOTE: If the value is an explicit nil, `nil, true` will be returned
 func (o *TaskInstance) GetOperatorOk() (*string, bool) {
-	if o == nil || o.Operator == nil {
+	if o == nil  {
 		return nil, false
 	}
-	return o.Operator, true
+	return o.Operator.Get(), o.Operator.IsSet()
 }
 
 // HasOperator returns a boolean if a field has been set.
 func (o *TaskInstance) HasOperator() bool {
-	if o != nil && o.Operator != nil {
+	if o != nil && o.Operator.IsSet() {
 		return true
 	}
 
 	return false
 }
 
-// SetOperator gets a reference to the given string and assigns it to the Operator field.
+// SetOperator gets a reference to the given NullableString and assigns it to the Operator field.
 func (o *TaskInstance) SetOperator(v string) {
-	o.Operator = &v
+	o.Operator.Set(&v)
+}
+// SetOperatorNil sets the value for Operator to be an explicit nil
+func (o *TaskInstance) SetOperatorNil() {
+	o.Operator.Set(nil)
+}
+
+// UnsetOperator ensures that no value is present for Operator, not even an explicit nil
+func (o *TaskInstance) UnsetOperator() {
+	o.Operator.Unset()
 }
 
 // GetQueuedWhen returns the QueuedWhen field value if set, zero value otherwise (both if not set or set to explicit null).
@@ -810,8 +820,8 @@ func (o TaskInstance) MarshalJSON() ([]byte, error) {
 	if o.PriorityWeight != nil {
 		toSerialize["priority_weight"] = o.PriorityWeight
 	}
-	if o.Operator != nil {
-		toSerialize["operator"] = o.Operator
+	if o.Operator.IsSet() {
+		toSerialize["operator"] = o.Operator.Get()
 	}
 	if o.QueuedWhen.IsSet() {
 		toSerialize["queued_when"] = o.QueuedWhen.Get()
diff --git a/airflow/model_task_instance_collection.go b/airflow/model_task_instance_collection.go
index dd3531d..42b1dc9 100644
--- a/airflow/model_task_instance_collection.go
+++ b/airflow/model_task_instance_collection.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
diff --git a/airflow/model_task_instance_collection_all_of.go b/airflow/model_task_instance_collection_all_of.go
index 1d9176c..9ed1e31 100644
--- a/airflow/model_task_instance_collection_all_of.go
+++ b/airflow/model_task_instance_collection_all_of.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
diff --git a/airflow/model_task_instance_reference.go b/airflow/model_task_instance_reference.go
index c8240a8..3331257 100644
--- a/airflow/model_task_instance_reference.go
+++ b/airflow/model_task_instance_reference.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
diff --git a/airflow/model_task_instance_reference_collection.go b/airflow/model_task_instance_reference_collection.go
index 1eb194a..7a03a69 100644
--- a/airflow/model_task_instance_reference_collection.go
+++ b/airflow/model_task_instance_reference_collection.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
diff --git a/airflow/model_task_state.go b/airflow/model_task_state.go
index 3d9903d..2e6b11f 100644
--- a/airflow/model_task_state.go
+++ b/airflow/model_task_state.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
@@ -48,6 +48,8 @@ const (
 	TASKSTATE_QUEUED TaskState = "queued"
 	TASKSTATE_NONE TaskState = "none"
 	TASKSTATE_SCHEDULED TaskState = "scheduled"
+	TASKSTATE_DEFERRED TaskState = "deferred"
+	TASKSTATE_SENSING TaskState = "sensing"
 	TASKSTATE_REMOVED TaskState = "removed"
 )
 
@@ -62,6 +64,8 @@ var allowedTaskStateEnumValues = []TaskState{
 	"queued",
 	"none",
 	"scheduled",
+	"deferred",
+	"sensing",
 	"removed",
 }
 
diff --git a/airflow/model_time_delta.go b/airflow/model_time_delta.go
index 9d28395..cbe66c6 100644
--- a/airflow/model_time_delta.go
+++ b/airflow/model_time_delta.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
diff --git a/airflow/model_trigger_rule.go b/airflow/model_trigger_rule.go
index 88fe6f7..4dcbec8 100644
--- a/airflow/model_trigger_rule.go
+++ b/airflow/model_trigger_rule.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
@@ -46,6 +46,7 @@ const (
 	TRIGGERRULE_NONE_FAILED TriggerRule = "none_failed"
 	TRIGGERRULE_NONE_SKIPPED TriggerRule = "none_skipped"
 	TRIGGERRULE_NONE_FAILED_OR_SKIPPED TriggerRule = "none_failed_or_skipped"
+	TRIGGERRULE_NONE_FAILED_MIN_ONE_SUCCESS TriggerRule = "none_failed_min_one_success"
 	TRIGGERRULE_DUMMY TriggerRule = "dummy"
 )
 
@@ -58,6 +59,7 @@ var allowedTriggerRuleEnumValues = []TriggerRule{
 	"none_failed",
 	"none_skipped",
 	"none_failed_or_skipped",
+	"none_failed_min_one_success",
 	"dummy",
 }
 
diff --git a/airflow/model_variable_all_of.go b/airflow/model_update_dag_run_state.go
similarity index 53%
copy from airflow/model_variable_all_of.go
copy to airflow/model_update_dag_run_state.go
index 4868e89..31a99d0 100644
--- a/airflow/model_variable_all_of.go
+++ b/airflow/model_update_dag_run_state.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
@@ -32,100 +32,101 @@ import (
 	"encoding/json"
 )
 
-// VariableAllOf struct for VariableAllOf
-type VariableAllOf struct {
-	Value *string `json:"value,omitempty"`
+// UpdateDagRunState struct for UpdateDagRunState
+type UpdateDagRunState struct {
+	// The state to set this DagRun
+	State *string `json:"state,omitempty"`
 }
 
-// NewVariableAllOf instantiates a new VariableAllOf object
+// NewUpdateDagRunState instantiates a new UpdateDagRunState object
 // This constructor will assign default values to properties that have it defined,
 // and makes sure properties required by API are set, but the set of arguments
 // will change when the set of required properties is changed
-func NewVariableAllOf() *VariableAllOf {
-	this := VariableAllOf{}
+func NewUpdateDagRunState() *UpdateDagRunState {
+	this := UpdateDagRunState{}
 	return &this
 }
 
-// NewVariableAllOfWithDefaults instantiates a new VariableAllOf object
+// NewUpdateDagRunStateWithDefaults instantiates a new UpdateDagRunState object
 // This constructor will only assign default values to properties that have it defined,
 // but it doesn't guarantee that properties required by API are set
-func NewVariableAllOfWithDefaults() *VariableAllOf {
-	this := VariableAllOf{}
+func NewUpdateDagRunStateWithDefaults() *UpdateDagRunState {
+	this := UpdateDagRunState{}
 	return &this
 }
 
-// GetValue returns the Value field value if set, zero value otherwise.
-func (o *VariableAllOf) GetValue() string {
-	if o == nil || o.Value == nil {
+// GetState returns the State field value if set, zero value otherwise.
+func (o *UpdateDagRunState) GetState() string {
+	if o == nil || o.State == nil {
 		var ret string
 		return ret
 	}
-	return *o.Value
+	return *o.State
 }
 
-// GetValueOk returns a tuple with the Value field value if set, nil otherwise
+// GetStateOk returns a tuple with the State field value if set, nil otherwise
 // and a boolean to check if the value has been set.
-func (o *VariableAllOf) GetValueOk() (*string, bool) {
-	if o == nil || o.Value == nil {
+func (o *UpdateDagRunState) GetStateOk() (*string, bool) {
+	if o == nil || o.State == nil {
 		return nil, false
 	}
-	return o.Value, true
+	return o.State, true
 }
 
-// HasValue returns a boolean if a field has been set.
-func (o *VariableAllOf) HasValue() bool {
-	if o != nil && o.Value != nil {
+// HasState returns a boolean if a field has been set.
+func (o *UpdateDagRunState) HasState() bool {
+	if o != nil && o.State != nil {
 		return true
 	}
 
 	return false
 }
 
-// SetValue gets a reference to the given string and assigns it to the Value field.
-func (o *VariableAllOf) SetValue(v string) {
-	o.Value = &v
+// SetState gets a reference to the given string and assigns it to the State field.
+func (o *UpdateDagRunState) SetState(v string) {
+	o.State = &v
 }
 
-func (o VariableAllOf) MarshalJSON() ([]byte, error) {
+func (o UpdateDagRunState) MarshalJSON() ([]byte, error) {
 	toSerialize := map[string]interface{}{}
-	if o.Value != nil {
-		toSerialize["value"] = o.Value
+	if o.State != nil {
+		toSerialize["state"] = o.State
 	}
 	return json.Marshal(toSerialize)
 }
 
-type NullableVariableAllOf struct {
-	value *VariableAllOf
+type NullableUpdateDagRunState struct {
+	value *UpdateDagRunState
 	isSet bool
 }
 
-func (v NullableVariableAllOf) Get() *VariableAllOf {
+func (v NullableUpdateDagRunState) Get() *UpdateDagRunState {
 	return v.value
 }
 
-func (v *NullableVariableAllOf) Set(val *VariableAllOf) {
+func (v *NullableUpdateDagRunState) Set(val *UpdateDagRunState) {
 	v.value = val
 	v.isSet = true
 }
 
-func (v NullableVariableAllOf) IsSet() bool {
+func (v NullableUpdateDagRunState) IsSet() bool {
 	return v.isSet
 }
 
-func (v *NullableVariableAllOf) Unset() {
+func (v *NullableUpdateDagRunState) Unset() {
 	v.value = nil
 	v.isSet = false
 }
 
-func NewNullableVariableAllOf(val *VariableAllOf) *NullableVariableAllOf {
-	return &NullableVariableAllOf{value: val, isSet: true}
+func NewNullableUpdateDagRunState(val *UpdateDagRunState) *NullableUpdateDagRunState {
+	return &NullableUpdateDagRunState{value: val, isSet: true}
 }
 
-func (v NullableVariableAllOf) MarshalJSON() ([]byte, error) {
+func (v NullableUpdateDagRunState) MarshalJSON() ([]byte, error) {
 	return json.Marshal(v.value)
 }
 
-func (v *NullableVariableAllOf) UnmarshalJSON(src []byte) error {
+func (v *NullableUpdateDagRunState) UnmarshalJSON(src []byte) error {
 	v.isSet = true
 	return json.Unmarshal(src, &v.value)
 }
diff --git a/airflow/model_update_task_instances_state.go b/airflow/model_update_task_instances_state.go
index b180826..79b6582 100644
--- a/airflow/model_update_task_instances_state.go
+++ b/airflow/model_update_task_instances_state.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
diff --git a/airflow/model_user.go b/airflow/model_user.go
index a4a6fb2..3cd08a7 100644
--- a/airflow/model_user.go
+++ b/airflow/model_user.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
diff --git a/airflow/model_user_all_of.go b/airflow/model_user_all_of.go
index 77cf425..8c4875d 100644
--- a/airflow/model_user_all_of.go
+++ b/airflow/model_user_all_of.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
diff --git a/airflow/model_user_collection.go b/airflow/model_user_collection.go
index 7ca254d..5c8e70b 100644
--- a/airflow/model_user_collection.go
+++ b/airflow/model_user_collection.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
diff --git a/airflow/model_user_collection_all_of.go b/airflow/model_user_collection_all_of.go
index 3461cde..612511d 100644
--- a/airflow/model_user_collection_all_of.go
+++ b/airflow/model_user_collection_all_of.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
diff --git a/airflow/model_user_collection_item.go b/airflow/model_user_collection_item.go
index 17105c7..bfb4756 100644
--- a/airflow/model_user_collection_item.go
+++ b/airflow/model_user_collection_item.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
diff --git a/airflow/model_user_collection_item_roles.go b/airflow/model_user_collection_item_roles.go
index 041127e..b79a79a 100644
--- a/airflow/model_user_collection_item_roles.go
+++ b/airflow/model_user_collection_item_roles.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
diff --git a/airflow/model_variable.go b/airflow/model_variable.go
index fedd49a..adcb971 100644
--- a/airflow/model_variable.go
+++ b/airflow/model_variable.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
diff --git a/airflow/model_variable_all_of.go b/airflow/model_variable_all_of.go
index 4868e89..c0f19d8 100644
--- a/airflow/model_variable_all_of.go
+++ b/airflow/model_variable_all_of.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
diff --git a/airflow/model_variable_collection.go b/airflow/model_variable_collection.go
index 988bdf9..0497b03 100644
--- a/airflow/model_variable_collection.go
+++ b/airflow/model_variable_collection.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
diff --git a/airflow/model_variable_collection_all_of.go b/airflow/model_variable_collection_all_of.go
index 73ef79a..e55affc 100644
--- a/airflow/model_variable_collection_all_of.go
+++ b/airflow/model_variable_collection_all_of.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
diff --git a/airflow/model_variable_collection_item.go b/airflow/model_variable_collection_item.go
index ac3d4a8..4edf71f 100644
--- a/airflow/model_variable_collection_item.go
+++ b/airflow/model_variable_collection_item.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
diff --git a/airflow/model_version_info.go b/airflow/model_version_info.go
index 358d1ef..534f114 100644
--- a/airflow/model_version_info.go
+++ b/airflow/model_version_info.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
diff --git a/airflow/model_weight_rule.go b/airflow/model_weight_rule.go
index b1472d1..d972e42 100644
--- a/airflow/model_weight_rule.go
+++ b/airflow/model_weight_rule.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
diff --git a/airflow/model_x_com.go b/airflow/model_x_com.go
index db4567b..fe4af35 100644
--- a/airflow/model_x_com.go
+++ b/airflow/model_x_com.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
diff --git a/airflow/model_x_com_all_of.go b/airflow/model_x_com_all_of.go
index afc82e9..339f9f5 100644
--- a/airflow/model_x_com_all_of.go
+++ b/airflow/model_x_com_all_of.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
diff --git a/airflow/model_x_com_collection.go b/airflow/model_x_com_collection.go
index 0881d9e..e431f76 100644
--- a/airflow/model_x_com_collection.go
+++ b/airflow/model_x_com_collection.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
diff --git a/airflow/model_x_com_collection_all_of.go b/airflow/model_x_com_collection_all_of.go
index e20fc24..9c3d24f 100644
--- a/airflow/model_x_com_collection_all_of.go
+++ b/airflow/model_x_com_collection_all_of.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
diff --git a/airflow/model_x_com_collection_item.go b/airflow/model_x_com_collection_item.go
index c3b1de6..492a143 100644
--- a/airflow/model_x_com_collection_item.go
+++ b/airflow/model_x_com_collection_item.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
diff --git a/airflow/response.go b/airflow/response.go
index bf0a7ee..750ad79 100644
--- a/airflow/response.go
+++ b/airflow/response.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org
diff --git a/airflow/utils.go b/airflow/utils.go
index ca4f4bf..f75f84d 100644
--- a/airflow/utils.go
+++ b/airflow/utils.go
@@ -18,7 +18,7 @@
 /*
  * Airflow API (Stable)
  *
- * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
+ * # Overview  To facilitate management, Apache Airflow supports a range of REST API endpoints across its objects. This section provides an overview of the API design, methods, and supported use cases.  Most of the endpoints accept `JSON` as input and return `JSON` responses. This means that you must usually add the following headers to your request: ``` Content-type: application/json Accept: application/json ```  ## Resources  The term `resource` refers to a single type of object in the [...]
  *
  * API version: 1.0.0
  * Contact: dev@airflow.apache.org