bitcoincros.blogg.se - Airflow github examples

Airflow github examples license#

Framework :: Apache Airflow :: Provider.

The following standard classifiers should be used in addition to any others you may choose to include: To improve discoverability of your provider package on PyPI, it is recommended to add classifiers to the package's metadata. Use the sample pyproject.toml file in this repository as a starting point for your own project. Your pyproject.toml file should contain all of the appropriate metadata and dependencies required to build your package. If you followed the formatting guidelines above, you're now ready to start editing files to include standard package functionality. └── test_sample_sensor.py Development Standards

├── pyproject.toml # A file to define dependencies and how the package is built and shipped. This will contain all Airflow modules and example DAGs. ├── sample_provider # Your package import directory.

Airflow github examples license#

├── LICENSE # A license is required, MIT or Apache is preferred. The highest level directory in the provider package should be named in the following format: Here, you'll find information on requirements and best practices for key aspects of your project:īefore writing and testing the functionality of your provider package, ensure that your project follows these formatting conventions. Ensure that all of these requirements have been met before submitting a provider package for community review. Provider repositories must be public on Github and follow the structural and technical guidelines laid out in this Readme. This repository provides best practices for building, structuring, and deploying Airflow provider packages as independent python modules available on PyPI. Guidelines on building, deploying, and maintaining provider packages that will help Airflow users interface with external systems.