... | ... | @@ -35,4 +35,10 @@ At the time of writing, there was no unified, platform approach to logging and r |
|
|
|
|
|
Where possible, ensure business logic code that has reusable characteristics is placed in a common DAG library for other community members to use. Also, consider if the functionality you're placing in a DAG operator is better off as an OSDU Data Platform service.
|
|
|
|
|
|
There are also recommended version standards for development. See this [ADR](https://community.opengroup.org/osdu/platform/data-flow/ingestion/ingestion-workflow/-/issues/74). |
|
|
\ No newline at end of file |
|
|
There are also recommended version standards for development. See this [ADR](https://community.opengroup.org/osdu/platform/data-flow/ingestion/ingestion-workflow/-/issues/74).
|
|
|
|
|
|
**Useful External References**
|
|
|
|
|
|
* Astronomer guide for Airflow DAG authoring - [here](https://www.astronomer.io/guides/dag-best-practices#:~:text=%20DAG%20Writing%20Best%20Practices%20in%20Apache%20Airflow,its%20own%20container%20with%20limited%20memory...%20More%20)
|
|
|
* Apache best practices guide - not much, but a few pointers [here](https://airflow.apache.org/docs/apache-airflow/stable/best-practices.html)
|
|
|
* Jinja macros, testing tips - automation tests [here](https://towardsdatascience.com/best-practices-for-airflow-developers-990c8a04f7c6) |
|
|
\ No newline at end of file |