Azure Data Services Go Fast Codebase

Introduction

The Azure Data Services Go Fast Codebase is a combination of Microsoft components designed to shorten the "time to value" when deploying an Azure Data Platform. Key features include:

• Infrastructure as code (IAC) deployment of MVP Azure Data Platform
• "Out of the box" Continuous Integration and Continuous Deployment framework
• Enterprise grade security and monitoring with full support for Key Vault, VNETS, Private Endpoints and Managed Service Identities
• Codeless Ingestion from commonly used enterprise source systems into an enterprise data lake
• Users can interact with capabilities through a webpage and embedded dashboards.

This project is composed of Microsoft components and Open-Source Software (OSS) and is provided to customers and partners at no charge.

At its core this project is intended to be an accelerator. As such, it is designed to accelerate the “time to value” in using the Microsoft components. As an accelerator, is it not for sale, nor is it a supported product.

Getting Started

Getting started is always the hardest part of any process so to help clients & partners get started with this repository we provide a set of online, on-boarding and upskilling workshops. Spaces in these workshops are limited and subject to an application process. If you are interested then please nominate yourself at https://forms.office.com/r/qbQrU6jFsj.

Prerequisites

Deployment of this project requires a variety of services across Azure. Please ensure that you have access to these services before continuing on to the deployment section of this guide.

To get started you will need the following:

• An active Azure Subscription & Empty Resource Group*
• Owner rights on the Azure Resource Group
• Power BI Workspace (Optional)

*Note that for a fully functioning deployment the deployment process will create a Deployment Service principal and two Azure Application Registrations within the Azure Active Directory (AAD) domain that is connected to your Azure subscription. It is recommended that you use an Azure subscription and AAD on which you have the necessary privileges to perform these operations.

You can sign up for an Azure subscription here

Once you have your Prerequisite items, please move on to the Deployment Configuration step.

Deployment Configuration

You will also need some development tools to edit and run the deployment scripts provided. It is recommended you use the following:

• A windows based computer (local or cloud)
• Visual Studio Code
• Docker Desktop
• Windows Store Ubuntu 18.04 LTS

The deployment uses a concept of Developing inside a Container to containerize all the necessary pre-requisite components without requiring them to be installed on the local machine. Follow our Configuring your System for Development Containers guide.

Once you have set up these pre-requisites you will then need to Clone this repository to your local machine.

🚩 If you want a stable deployment it is highly recommended that you checkout one of the official release tags. For example, if you wish to deploy v1.0.2 run the line below from within the directory into which you cloned the repository.

git checkout tags/v2.0.1

Deployment

To deploy the solution open Visual Studio Code and carry out the following steps.

• ✅ From the menu select "File" then "Open Folder". Navigate the directory into which you cloned the solution. It should look like the image below with a ".devcontainer" folder at the root. Open this folder in Visual Studio Code.

• ✅ Next, from the Visual Studio Code menu, select "View", "Command Palette". When the search box opens type "Remote-Containers: Reopen in Container". Note that Docker Desktop needs to be running before you perform this step.
• ✅ From the menu select "Terminal", "New Terminal". A new Powershell Core window will open at the bottom of your screen. You are now running within the Docker container.
• ✅ You are now in the development and deployment environment. Within the new terminal window navigate to the DeploymentV2 directory using the commands below:

cd ./solution/DeploymentV2

• ✅ You are now ready to begin the IAC deployment. To do so follow this detailed guide.

#️⃣ Code Composition

See below for the a "Cloc" generated breakdown of the source code files by format:

Post Deployment Set-up and Instructions

======= Coming Soon.

Cost Estimator

Coming Soon.

Navigating the Source Code

This has the following structure:

Contributing

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.

When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.

Recommended Maintenance activities when contributing:

1. Check Azure Cli for new versions - upgrade, test and remediate where necessary
2. Check Terraform Providers for new versions - upgrade, test and remediate where necessary
3. Check Dependecny Libraies for Function Application and Web Application for new versions - upgrade, test and remediate where necessary

Security

Microsoft takes the security of our software products and services seriously, which includes all source code repositories managed through our GitHub organizations, which include Microsoft, Azure, DotNet, AspNet, Xamarin, and our GitHub organizations. Please review this repository's security section for more details.

Privacy

Microsoft values your privacy. See the Microsoft Privacy Statement for more information

Trademarks

This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft trademarks or logos is subject to and must follow Microsoft's Trademark & Brand Guidelines. Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship. Any use of third-party trademarks or logos are subject to those third-party's policies.