Cloud Adoption Framework for Azure - Landing zones on Terraform - Rover
Microsoft Cloud Adoption Framework for Azure provides you with guidance and best practices to adopt Azure.
The CAF rover is helping you managing your enterprise Terraform deployments on Microsoft Azure and is composed of two parts:
A docker container
- Allows consistent developer experience on PC, Mac, Linux, including the right tools, git hooks and DevOps tools.
- Native integration with Visual Studio Code, GitHub Codespaces.
- Contains the versioned toolset you need to apply landing zones.
- Helps you switching components versions fast by separating the run environment and the configuration environment.
- Ensure pipeline ubiquity and abstraction run the rover everywhere, whichever pipeline technology.
A Terraform wrapper
- Helps you store and retrieve Terraform state files on Azure storage account.
- Facilitates the transition to CI/CD.
- Enables seamless experience (state connection, execution traces, etc.) locally and inside pipelines.
The rover is available from the Docker Hub in form of:
- Standalone edition: to be used for landing zones engineering or pipelines.
- Adding runner (agent) for the following platforms
- Azure DevOps
- GitHub Actions
- Terraform Cloud/Terraform Enterprise
Getting starter with CAF Terraform landing zones
If you are reading this, you are probably interested also in reading the doc as below:
Feel free to open an issue for feature or bug, or to submit a PR.
In case you have any question, you can reach out to tf-landingzones at microsoft dot com.
You can also reach us on Gitter
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.