page_type | languages | products | description | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
sample |
|
|
Code samples showcasing how to apply DevOps concepts to common data engineering patterns and architectures leveraging different Microsoft data platform technologies. |
This repository contains numerous code samples and artifacts on how to apply DevOps principles to common data engineering patterns and architectures utilizing Microsoft data platform technologies.
The samples are either focused on a single microsoft service (Single-Technology Samples) or showcases an end-to-end data pipeline solution as a reference implementation (End-to-End Samples). Each sample contains code and artifacts related to one or more of the following capabilities:
- Infrastructure as Code (IaC)
- Build and Release Pipelines (CI/CD)
- Testing
- Observability / Monitoring
This sample demonstrates batch, end-to-end data pipeline utilizing Azure Data Factory and Azure Databricks built according to the medallion architecture, along with a corresponding CI/CD process, observability and automated testing.
-
This sample would demonstrate end-to-end batch data processing utilizing Microsoft Fabric built according to the medallion architecture, along with a corresponding CI/CD process, observability and automated testing.
In the current version, the sample is showcasing the deployment of Azure and Fabric resources together using Terraform. The deployment uses a service principal or managed identity for authentication where supported and falls back to Entra user authentication where it is not.
This project welcomes contributions and suggestions. Please see our Contributing guide.
The software may collect information about you and your use of the software and send it to Microsoft. Microsoft may use this information to provide services and improve our products and services. You may turn off the telemetry as described below. There are also some features in the software that may enable you and Microsoft to collect data from users of your applications. If you use these features, you must comply with applicable law, including providing appropriate notices to users of your applications together with a copy of Microsoft’s privacy statement. Our privacy statement is located here. You can learn more about data collection and use in the help documentation and our privacy statement. Your use of the software operates as your consent to these practices.
The partner_id
provider property in .tf files, AZURE_HTTP_USER_AGENT
declaration in .sh files, and attribution
resources in .bicep files enable anonymous telemetry that helps us justify ongoing investment in
maintaining and improving this repository. Keeping these values enabled supports the project and future
feature development. To opt out of this telemetry, simply remove partner_id
, AZURE_HTTP_USER_AGENT
,
or attribution
code blocks. When enabled, the specified IDs are appended to requests sent by the associated code.