In order to start deploying your with CAF landing zones, you need an Azure subscription (Trial, MSDN, etc.) and you need to install the following components on your machine:
- Visual Studio Code
- Docker Desktop or Rancher Desktop in dockerd mode.
- Git
You can deploy it easily on Windows and MacOS with the following software managers:
MacOS | Windows |
---|---|
brew cask install visual-studio-code docker brew install git |
Install Chocolatey (https://chocolatey.org/docs/installation) choco install git vscode docker-desktop |
Once installed, open Visual Studio Code and install "Remote Development" extension as follow:
The starter repository contains the basic configuration files and scenarios. It will allow you to compose your configuration files in the integrated environment. You can find more information on the platform starter repository Clone the repository using the following command:
git clone https://github.com/Azure/caf-terraform-landingzones-platform-starter.git
Open the repository you've just cloned in Visual Studio Code, click on the lower bar, green sign and in the palette opening on the top of Visual Studio Code Window, select "Open Folder in container" or "Reopen in container"
This should take a while, in the meantime, feel free to click on Details to see the container being downloaded from the registry and being connected to yur local environment:
You will have to accept local mapping to your filesystem when Docker prompts you (here's how you reconfigure Docker Desktop to allow fileshares ), so that you can access your files from your container.
After a while, your environment is ready, note on the lower left part of Visual Studio Code, that you are now in your Azure CAF rover, which is your environment to use Azure landing zones.
You must be authenticated first: For that we will rely on Azure authentication as completed by Azure Cli, via browser method:
rover login
We recommend that you verify the output of the login and make sure the subscription selected by default is the one you want to work on. If not, you can use the following switch:
az account set --subscription <subscription_GUID>
Please refer to instructions and documentation on the central documentation
Happy deployment with Azure landing zones, let us know your feedback and how you need it to evolve!