396bbca113
|
||
|---|---|---|
| .devcontainer | ||
| .github | ||
| .pipelines | ||
| .vscode | ||
| configuration | ||
| documentation | ||
| enterprise_scale/construction_sets/aks/online/aks_secure_baseline | ||
| reference_implementations | ||
| .gitattributes | ||
| .gitignore | ||
| .pre-commit-config.yaml | ||
| CHANGELOG.md | ||
| CODE_OF_CONDUCT.md | ||
| LICENSE | ||
| README.md | ||
README.md
Cloud Adoption Framework landing zones for Terraform - Starter template
Microsoft Cloud Adoption Framework for Azure provides you with guidance and best practices to adopt Azure.
A landing zone is a segment of a cloud environment, that has been preprovisioned through code, and is dedicated to the support of one or more workloads. Landing zones provide access to foundational tools and controls to establish a compliant place to innovate and build new workloads in the cloud, or to migrate existing workloads to the cloud. Landing zones use defined sets of cloud services and best practices to set you up for success.
Getting started
To get started with creating your environment, you can fork this repository on your Git environment (inside your personal or organization GitHub, inside an Azure DevOps project or any other Version Control System that your company uses.)
You can then customize your environment by following the steps inside the configuration folder and review our sample configuration onboarding video here
Starter template
The purpose of this repository is to provide you with a starting point when composing your Cloud Adoption Framework for Azure landing zones on Terraform. It provides with sample files, folder structure and advices on how to get started creating and Infrastructure as Code and DevOps environment.
In CAF landing zones for Terraform, our approach is to separate the configuration repository and the logic repository:
- Configuration repository: this template is an example of configuration repository for CAF landing zones, containing definition of the configuration for your different environments. In real world, this is often separate repositories, but to simplify things, we created a repo with examples containing various environments.
- Logic repository: the Azure CAF landing zone repository
This approach allows you to easily:
- check-in your configuration in your specific Git repository.
- resync the code with the public codebase for updates.
- customize the code if needed and contribute back to the community.
Related repositories
Landing zones for Terraform are composed of multiple open-source components and projects:
| Repo | Description |
|---|---|
| caf-terraform-landingzones | landing zones repo with sample and core documentations |
| rover | devops toolset for operating landing zones |
| azure_caf_provider | custom provider for naming conventions |
| module | CAF Terraform module |
Community
Feel free to open an issue for feature or bug, or to submit a pull request.
In case you have any question, you can reach out to tf-landingzones at microsoft dot com.
You can also reach us on Gitter
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.
Code of conduct
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.