Miscellaneous FAQ
I want to deploy multiple landing zones, but the PowerShell command keeps trying to overwrite my existing environment
After bootstrapping, the PowerShell leaves the folder structure intact, including the Terraform state file. This is by design, so you have an opportunity to amend or destroy the environment.
If you want to deploy to a separate environment, the simplest approach is to specify a separate folder for each deployment using the -output parameter. For example:
E.g. Your folder structure could look like this:
📂accelerator
┣ 📂config
┃ ┣ 📂01
┃ ┃ ┃ 📜inputs.yaml
┃ ┃ ┗ 📜platform-landing-zone.tfvars
┃ ┗ 📂02
┃ ┃ 📜inputs.yaml
┃ ┗ 📜platform-landing-zone.tfvars
┣ 📂output01
┗ 📂output02
Your commands could look like this:
# Environment 01
Deploy-Accelerator `
-inputs "~/accelerator/config/01/inputs.yaml", "~/accelerator/config/01/platform-landing-zone.tfvars" `
-starterAdditionalFiles "~/accelerator/config/01/lib" `
-output "~/accelerator/output01"
# Environment 02
Deploy-Accelerator `
-inputs "~/accelerator/config/02/inputs.yaml", "~/accelerator/config/02/platform-landing-zone.tfvars" `
-starterAdditionalFiles "~/accelerator/config/02/lib" `
-output "~/accelerator/output02"
You can then deploy as many times as you like without interfering with a previous deployment.
Yes, you can skip the approval of the Terraform plan by using the -autoApprove parameter.
For example:
Deploy-Accelerator `
-inputs "~/accelerator/config/inputs.yaml", "~/accelerator/config/platform-landing-zone.tfvars" `
-starterAdditionalFiles "~/accelerator/config/lib" `
-output "~/accelerator/output" `
-autoApprove
In order to target your own domain, add the following settings to your bootstrap configuration file inputs.yaml:
github_organization_domain_name: "<enterprise name>.ghe.com"
For example:
github_organization_domain_name: "contoso.ghe.com"