(airflow) Configure source of Airflow pkg
- Allow a Docker build-arg to specify the source of the Airflow python package in any format supported by pip Change-Id: Ifa2dd62d91570035cff91ff07868b0fcf659add8
|2 weeks ago|
|charts/shipyard||2 weeks ago|
|doc||1 month ago|
|etc/shipyard||1 year ago|
|images||1 day ago|
|src/bin||1 day ago|
|tools||2 months ago|
|.dockerignore||1 year ago|
|.editorconfig||11 months ago|
|.gitignore||1 year ago|
|.gitreview||4 months ago|
|.zuul.yaml||3 months ago|
|LICENSE||1 year ago|
|Makefile||1 day ago|
|README.rst||11 months ago|
|requirements.readthedocs.txt||1 year ago|
|tox.ini||1 year ago|
Shipyard adopts the Falcon web framework and uses Apache Airflow as the backend engine to programmatically author, schedule and monitor workflows.
Find more documentation for Shipyard on Read the Docs.
The current workflow is as follows:
Note: This project, along with the tools used within are community-based and open sourced.
The goal for Shipyard is to provide a customizable framework for operators and developers alike. This framework will enable end-users to orchestrate and deploy a fully functional container-based Cloud.
This project is under development at the moment. We encourage anyone who is interested in Shipyard to review our documentation.
If you find a bug, please feel free to create a Storyboard issue.