You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/integrations/airflow.md
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -155,3 +155,7 @@ default_scheduler:
155
155
type: mwaa
156
156
environment: <The MWAA Environment Name>
157
157
```
158
+
159
+
### YC Airflow
160
+
161
+
SQLMesh fully supports Airflow hosted on Yandex [managed Airflow instances](https://yandex.cloud/en/services/managed-airflow) - see the [configuration reference page](../reference/configuration.md#yc-airflow) for more information.
Copy file name to clipboardExpand all lines: docs/reference/configuration.md
+11Lines changed: 11 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -227,6 +227,17 @@ See [Airflow Integration Guide](../integrations/airflow.md) for information abou
227
227
228
228
The Google Cloud Composer scheduler type shares the same configuration options as the `airflow` type, except for `username` and `password`. Cloud Composer relies on `gcloud` authentication, so the `username` and `password` options are not required.
229
229
230
+
#### YC Airflow
231
+
232
+
**Type:** `yc_airflow`
233
+
234
+
Yandex Managed Airflow shares similar configuration options with the standard `airflow` type, with the following exceptions:
235
+
236
+
- `max_snapshot_ids_per_request`: This option is deprecated and not supported.
237
+
- Authentication: YC Airflow requires additional credentials, including both a `token` and a combination of `username` and `password`.
238
+
239
+
Unlike the `airflow` type, YC Airflow leverages Yandex Cloud's internal authentication mechanisms. Therefore, all requests to the Airflow API must include a valid Yandex Cloud IAM-token for authentication.
240
+
230
241
## Gateway/connection defaults
231
242
232
243
The default gateway and connection keys specify what should happen when gateways or connections are not explicitly specified. Find additional details in the configuration overview page [gateway/connection defaults section](../guides/configuration.md#gatewayconnection-defaults).
0 commit comments