Skip to content

Commit

Permalink
Add to FAQs
Browse files Browse the repository at this point in the history
  • Loading branch information
jaredfholgate committed Sep 16, 2023
1 parent c60a3d5 commit 889068f
Showing 1 changed file with 14 additions and 1 deletion.
15 changes: 14 additions & 1 deletion docs/wiki/Frequently-Asked-Questions.md
Original file line number Diff line number Diff line change
Expand Up @@ -36,4 +36,17 @@ After the Terraform apply has been complete there is an opportunity to remove th
1. Terraform will show a plan and prompt you to continue by typing `yes` and hitting enter.
1. Terraform will destroy all the resoources it created in the boostrap.

You'll not be able to delete the `./v#.#.#` folder and run the `New-ALZEnvironment` command again.
You'll not be able to delete the `./v#.#.#` folder and run the `New-ALZEnvironment` command again.

## Multiple landing zone deployments

### I want to deploy multiple landing zones, but the PowerShell command keeps trying to overrwrite 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 thr `-Output` parameter. For example:

- Deployment 1: `New-ALZEnvironment -IaC "terraform" -Cicd "azuredevops" -Output "./deployment1"`
- Deployment 2: `New-ALZEnvironment -IaC "terraform" -Cicd "azuredevops" -Output "./deployment2"`

You can then deploy as many times as you like without interferring with a previous deployment.

0 comments on commit 889068f

Please sign in to comment.