airflow

nprasad2077/airflow

0 Fork 0

mirror of https://github.com/apache/airflow.git synced 2026-11-04 07:12:48 +00:00

Files

T

Dr Alex Mitre 5bfc14fcfc Validate Google operator templated parameters after rendering (#70534 )

CloudSpeechToTextRecognizeSpeechOperator, CloudTextToSpeechSynthesizeOperator,
and CloudFirestoreExportDatabaseOperator validate template fields inside
_validate_inputs() called from __init__, so the checks ran against
un-rendered Jinja expressions and an empty rendered value was never
caught. The validation now runs at execute time, and the raises are
narrowed from AirflowException to ValueError per the ongoing exception
clean-up.

2026-09-15 22:55:09 +03:00

.gitignore

Automatically refresh generated dependencies when needed (#49848 )

2025-04-27 15:12:14 +00:00

dep_tree.txt

…

dependency_depth.json

…

devel_deps.txt

Drop joserfc dependency (#63660 )

2026-03-15 16:36:10 +01:00

known_airflow_exceptions.txt

Validate Google operator templated parameters after rendering (#70534 )

2026-09-15 22:55:09 +03:00

known_sdk_imports_in_core.txt

Add SerializedVariableInterval for deadline alerts (#71802 )

2026-08-28 20:48:16 -07:00

provider_metadata.json

Update providers metadata 2026-09-14 (#73138 )

2026-09-15 16:54:19 +03:00

PYPI_README.md

readme add uv (#71013 )

2026-08-13 15:06:39 +02:00

README.md

Simplify tooling by switching completely to uv (#48223 )

2025-04-02 13:11:13 +02:00

README.md

NOTE! The files in this folder are generated by pre-commit based on airflow sources. They are not supposed to be manually modified.

You can read more about pre-commit hooks here.

provider_dependencies.json - is generated based on provider.yaml files in airflow/providers and based on the imports in the provider code. If you want to add new dependency to a provider, you need to modify the corresponding provider.yaml file. This file is git-ignored (used to be committed) and it is generated automatically / dynamically when needed by either breeze or pre-commit hooks.
provider_metadata.json - is generated based on provider.yaml files, airflow constraints and tags for the providers. It contains historical metadata in providers that were released - it is useful to generate information in release notes and it is used to generate SBOM information for the providers. It is manually regenerated using breeze release-management generate-providers-metadata command."
PYPI_README.md - is generated from the comprehensive README.md of the project, which contains exhaustive project details. Unlike the full README.md, PYPI_README.md is a distilled version tailored for PyPI, focusing on select sections. This subset is produced by the generate-pypi-readme pre-commit hook specified in the .pre-commit-config.yaml file. This hook triggers automatically whenever the related sections in the README.md change, ensuring alignment between the two files.
devel_deps.txt is a file containing development-only dependencies of Airflow. They were generated for Airflow 2.9.3 by running ./dev/get_devel_deps.sh script.
dep_tree.txt is a file containing the dependency tree of Airflow. It was generated for Airflow 2.9.3 by running this inside breeze:

uv tree --no-dedupe  > /opt/airflow/generated/dep_tree.txt

dependency_depth.json is a fie containing the dependency depth of Airflow. It was generated for Airflow 2.9.3 by running this inside breeze:

cat /opt/airflow/generated/dep_tree.txt | python /opt/airflow/scripts/in_container/get_dependency_status.py >/opt/airflow/generated/dependency_depth.json