Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Arcbox 3.0 remove terraform from docs #342

Merged
merged 2 commits into from
Jul 3, 2024
+5 −267
Merged

Arcbox 3.0 remove terraform from docs #342

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
7769ab8
Merge pull request #10 from Azure/canary
sebassem Jul 1, 2024
b94df80
remove terraform references
sebassem Jul 1, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
68 changes: 1 addition & 67 deletions docs/azure_jumpstart_arcbox/DataOps/_index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@

## Overview

ArcBox for DataOps is a special "flavor" of ArcBox that is intended for users who want to experience Azure Arc-enabled SQL Managed Instance capabilities in a sandbox environment.

Check failure on line 11 in docs/azure_jumpstart_arcbox/DataOps/_index.md

View workflow job for this annotation

GitHub Actions / lint 

[vale] reported by reviewdog 🐶
[Microsoft.Contractions] Use 'that's' instead of 'that is'.

Raw Output:
{"message": "[Microsoft.Contractions] Use 'that's' instead of 'that is'.", "location": {"path": "docs/azure_jumpstart_arcbox/DataOps/_index.md", "range": {"start": {"line": 11, "column": 52}}}, "severity": "ERROR"}

![Screenshot showing ArcBox architecture diagram](./arch_dataops.png)

Expand All @@ -27,9 +27,9 @@

ArcBox for DataOps deploys three Kubernetes clusters to give you multiple options for exploring Azure Arc-enabled Kubernetes capabilities and potential integrations.

- _**ArcBox-CAPI-Data-xxxx**_ - A single-node Rancher K3s cluster which is then transformed to a [Cluster API](https://cluster-api.sigs.k8s.io/user/concepts.html) management cluster using the Cluster API Provider for Azure (CAPZ), and a workload cluster (_ArcBox-CAPI-Data_) is deployed onto the management cluster. The workload cluster is onboarded as an Azure Arc-enabled Kubernetes resource. ArcBox automatically deploys an Azure Arc Data Controller, an Active Directory connector and an Azure Arc-enabled SQL Managed Instance on top of the connected cluster.

Check failure on line 30 in docs/azure_jumpstart_arcbox/DataOps/_index.md

View workflow job for this annotation

GitHub Actions / lint 

[vale] reported by reviewdog 🐶
[Vale.Spelling] Did you really mean 'onboarded'?

Raw Output:
{"message": "[Vale.Spelling] Did you really mean 'onboarded'?", "location": {"path": "docs/azure_jumpstart_arcbox/DataOps/_index.md", "range": {"start": {"line": 30, "column": 341}}}, "severity": "ERROR"}
- _**ArcBox-AKS-Data-xxxx**_ - An AKS cluster that is connected to Azure as an Azure Arc-enabled Kubernetes resource. ArcBox automatically deploys an Azure Arc Data Controller, an Active Directory connector and an Azure Arc-enabled SQL Managed Instance on top of the connected cluster.

Check failure on line 31 in docs/azure_jumpstart_arcbox/DataOps/_index.md

View workflow job for this annotation

GitHub Actions / lint 

[vale] reported by reviewdog 🐶
[Microsoft.Contractions] Use 'that's' instead of 'that is'.

Raw Output:
{"message": "[Microsoft.Contractions] Use 'that's' instead of 'that is'.", "location": {"path": "docs/azure_jumpstart_arcbox/DataOps/_index.md", "range": {"start": {"line": 31, "column": 47}}}, "severity": "ERROR"}
- _**ArcBox-AKS-DR-Data-xxxx**_ - An AKS cluster that is deployed in a separate virtual network, designating a disaster recovery site. This cluster is then connected to Azure as an Azure Arc-enabled Kubernetes resource. ArcBox automatically deploys an Azure Arc Data Controller, an Active Directory connector and an Azure Arc-enabled SQL Managed Instance on top of the connected cluster. This cluster is then configured with _ArcBox-CAPI-Data-xxxx_ to be part of a distributed availability group for disaster recovery.

Check failure on line 32 in docs/azure_jumpstart_arcbox/DataOps/_index.md

View workflow job for this annotation

GitHub Actions / lint 

[vale] reported by reviewdog 🐶
[Microsoft.Contractions] Use 'that's' instead of 'that is'.

Raw Output:
{"message": "[Microsoft.Contractions] Use 'that's' instead of 'that is'.", "location": {"path": "docs/azure_jumpstart_arcbox/DataOps/_index.md", "range": {"start": {"line": 32, "column": 50}}}, "severity": "ERROR"}

### Sample applications

Expand All @@ -37,13 +37,13 @@

The sample applications included in ArcBox are:

- **The Bookstore Application** - An MVC web application. ArcBox will deploy **one Kubernetes pod replica** of the _Bookstore_ application in the _arc_ namespace onto the _ArcBox-CAPI-Data-xxxx_ and the _ArcBox-AKS-DR-Data-xxxx_ clusters.

Check failure on line 40 in docs/azure_jumpstart_arcbox/DataOps/_index.md

View workflow job for this annotation

GitHub Actions / lint 

[vale] reported by reviewdog 🐶
[Vale.Terms] Use 'Arc' instead of 'arc'.

Raw Output:
{"message": "[Vale.Terms] Use 'Arc' instead of 'arc'.", "location": {"path": "docs/azure_jumpstart_arcbox/DataOps/_index.md", "range": {"start": {"line": 40, "column": 148}}}, "severity": "ERROR"}

Check failure on line 40 in docs/azure_jumpstart_arcbox/DataOps/_index.md

View workflow job for this annotation

GitHub Actions / lint 

[vale] reported by reviewdog 🐶
[Vale.Spelling] Did you really mean 'namespace'?

Raw Output:
{"message": "[Vale.Spelling] Did you really mean 'namespace'?", "location": {"path": "docs/azure_jumpstart_arcbox/DataOps/_index.md", "range": {"start": {"line": 40, "column": 153}}}, "severity": "ERROR"}

- **DB Connection Application** - An MVC application. ArcBox will deploy **one Kubernetes pod replica** as part of the DB connection app and an Ingress controller to demonstrate the active connections to the different Azure Arc-enabled SQL Managed Instances replicas.

### Azure Monitor integration

ArcBox deploys metrics and logs upload to Azure Monitor for the deployed data services, in addition to the out-of-the-box Grafana and Kibana dashboards that get deployed as part of Arc-enabled Data services.

Check failure on line 46 in docs/azure_jumpstart_arcbox/DataOps/_index.md

View workflow job for this annotation

GitHub Actions / lint 

[vale] reported by reviewdog 🐶
[Vale.Spelling] Did you really mean 'Kibana'?

Raw Output:
{"message": "[Vale.Spelling] Did you really mean 'Kibana'?", "location": {"path": "docs/azure_jumpstart_arcbox/DataOps/_index.md", "range": {"start": {"line": 46, "column": 135}}}, "severity": "ERROR"}

### Hybrid Unified Operations

Expand All @@ -60,16 +60,13 @@
- Azure portal
- ARM template via Azure CLI
- Azure Bicep
- HashiCorp Terraform

![Deployment flow diagram for ARM-based deployments](./deployment_flow.png)

![Deployment flow diagram for Terraform-based deployments](./deployment_flow_tf.png)

ArcBox uses an advanced automation flow to deploy and configure all necessary resources with minimal user interaction. The previous diagrams provide an overview of the deployment flow. A high-level summary of the deployment is:

- User deploys the primary ARM template (_azuredeploy.json_), Bicep file (_main.bicep_), or Terraform plan (_main.tf_). These objects contain several nested objects that will run simultaneously.
- User deploys the primary ARM template (_azuredeploy.json_) or Bicep file (_main.bicep_). These objects contain several nested objects that will run simultaneously.
- Client virtual machine ARM template/plan - deploys a domain-joined Client Windows VM. This is a Windows Server VM that comes preconfigured with kubeconfig files to work with the three Kubernetes clusters, as well multiple tools such as VSCode, Azure Data Studio and SQL Server Management Studio to make working with ArcBox simple and easy.

Check failure on line 69 in docs/azure_jumpstart_arcbox/DataOps/_index.md

View workflow job for this annotation

GitHub Actions / lint 

[vale] reported by reviewdog 🐶
[Vale.Spelling] Did you really mean 'preconfigured'?

Raw Output:
{"message": "[Vale.Spelling] Did you really mean 'preconfigured'?", "location": {"path": "docs/azure_jumpstart_arcbox/DataOps/_index.md", "range": {"start": {"line": 69, "column": 130}}}, "severity": "ERROR"}

Check failure on line 69 in docs/azure_jumpstart_arcbox/DataOps/_index.md

View workflow job for this annotation

GitHub Actions / lint 

[vale] reported by reviewdog 🐶
[Vale.Spelling] Did you really mean 'VSCode'?

Raw Output:
{"message": "[Vale.Spelling] Did you really mean 'VSCode'?", "location": {"path": "docs/azure_jumpstart_arcbox/DataOps/_index.md", "range": {"start": {"line": 69, "column": 241}}}, "severity": "ERROR"}
- Storage account template/plan - used for staging files in automation scripts.
- Management artifacts template/plan - deploys Azure Log Analytics workspace, its required Solutions, a domain controller and two virtual networks.
- User remotes into the Client Windows VM using domain credentials, which automatically kicks off multiple scripts that:
Expand Down Expand Up @@ -292,69 +289,7 @@
az group create --name "<resource-group-name>" --location "<preferred-location>"
az deployment group create -g "<resource-group-name>" -f "main.bicep" -p "main.parameters.json"
```

> **Note:** The deployment can take up to 45 minutes. If it keeps running for more than that, please check the [troubleshooting guide](#basic-troubleshooting).

## Deployment Option 4: HashiCorp Terraform Deployment

- Clone the Azure Arc Jumpstart repository

```shell
git clone https://github.com/microsoft/azure_arc.git
```

- Download and install the latest version of Terraform [here](https://www.terraform.io/downloads.html)

> **Note:** Terraform 1.x or higher is supported for this deployment. Tested with Terraform v1.0.9+.

- Create a `terraform.tfvars` file in the root of the terraform folder and supply some values for your environment.

```HCL
azure_location = "westus2"
resource_group_name = "ArcBoxDataOps"
spn_client_id = "1414133c-9786-53a4-b231-f87c143ebdb1"
spn_client_secret = "fakeSecretValue123458125712ahjeacjh"
spn_tenant_id = "33572583-d294-5b56-c4e6-dcf9a297ec17"
client_admin_ssh = "C:/Temp/rsa.pub"
deployment_flavor = "DataOps"
deploy_bastion = false
```

- Variable Reference:
- **_`azure_location`_** - Azure location code (e.g. 'eastus', 'westus2', etc.)
- **_`resource_group_name`_** - Resource group which will contain all of the ArcBox artifacts
- **_`spn_client_id`_** - Your Azure service principal id
- **_`spn_client_secret`_** - Your Azure service principal secret
- **_`spn_tenant_id`_** - Your Azure tenant id
- **_`client_admin_ssh`_** - SSH public key path, used for Linux VMs
- **_`deployment_flavor`_** - Use the value "DataOps" to specify that you want to deploy the DataOps flavor of ArcBox
- _`deployBastion`_ - Set to *`true`* if you want to use Azure Bastion to connect to _ArcBox-Client_
- _`client_admin_username`_ - Admin username for Windows & Linux VMs
- _`client_admin_password`_ - Admin password for Windows VMs. Password must have 3 of the following: 1 lower case character, 1 upper case character, 1 number, and 1 special character. The value must be between 12 and 123 characters long.
- **_`workspace_name`_** - Unique name for the ArcBox Log Analytics workspace that will be created

> **Note:** Any variables in bold are required. If any optional parameters are not provided, defaults will be used.

- Now you will deploy the Terraform file. Navigate to the local cloned [deployment folder](https://github.com/microsoft/azure_arc/tree/main/azure_jumpstart_arcbox/bicep) and run the commands below:

```shell
terraform init
terraform plan -out=infra.out
terraform apply "infra.out"
```

- Example output from `terraform init`:

![terraform init](./terraform_init.png)

- Example output from `terraform plan -out=infra.out`:

![terraform plan](./terraform_plan.png)

- Example output from `terraform apply "infra.out"`:

![terraform plan](./terraform_apply.png)

> **Note:** The deployment can take up to 45 minutes. If it keeps running for more than that, please check the [troubleshooting guide](#basic-troubleshooting).

## Start post-deployment automation
Expand Down Expand Up @@ -816,7 +751,6 @@
- SQL StressTest application
- Putty
- 7zip
- Terraform
- Git
- ZoomIt

Expand Down
Binary file removed docs/azure_jumpstart_arcbox/DataOps/terraform_apply.png
View file
Open in desktop
Binary file not shown.
Binary file removed docs/azure_jumpstart_arcbox/DataOps/terraform_init.png
View file
Open in desktop
Binary file not shown.
Binary file removed docs/azure_jumpstart_arcbox/DataOps/terraform_plan.png
View file
Open in desktop
Binary file not shown.
70 changes: 1 addition & 69 deletions docs/azure_jumpstart_arcbox/DevOps/_index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -93,15 +93,12 @@ ArcBox provides multiple paths for deploying and configuring ArcBox resources. D
- Azure portal
- ARM template via Azure CLI
- Azure Bicep
- HashiCorp Terraform

![Deployment flow diagram for ARM-based deployments](./deployment_flow.png)

![Deployment flow diagram for Terraform-based deployments](./deployment_flow_tf.png)

ArcBox uses an advanced automation flow to deploy and configure all necessary resources with minimal user interaction. The previous diagrams provide an overview of the deployment flow. A high-level summary of the deployment is:

- User deploys the primary ARM template (_azuredeploy.json_), Bicep file (_main.bicep_), or Terraform plan (_main.tf_). These objects contain several nested objects that will run simultaneously.
- User deploys the primary ARM template (_azuredeploy.json_) or Bicep file (_main.bicep_). These objects contain several nested objects that will run simultaneously.
- Client virtual machine ARM template/plan - deploys the Client Windows VM. This is a Windows Server VM that comes preconfigured with kubeconfig files to work with the two Kubernetes clusters, as well multiple tools such as VSCode to make working with ArcBox simple and easy.
- Storage account template/plan - used for staging files in automation scripts.
- Management artifacts template/plan - deploys Azure Log Analytics workspace, its required Solutions, and Azure Policy artifacts.
Expand Down Expand Up @@ -328,70 +325,6 @@ ArcBox uses an advanced automation flow to deploy and configure all necessary re

> **Note:** If you see any failure in the deployment, please check the [troubleshooting guide](#basic-troubleshooting).

## Deployment Option 4: HashiCorp Terraform Deployment

- Clone the Azure Arc Jumpstart repository

```shell
git clone https://github.com/microsoft/azure_arc.git
```

- Download and install the latest version of Terraform [here](https://www.terraform.io/downloads.html)

> **Note:** Terraform 1.x or higher is supported for this deployment. Tested with Terraform v1.0.9+.

- Create a `terraform.tfvars` file in the root of the terraform folder and supply some values for your environment.

```HCL
azure_location = "westus2"
resource_group_name = "ArcBoxDevOps"
spn_client_id = "1414133c-9786-53a4-b231-f87c143ebdb1"
spn_client_secret = "fakeSecretValue123458125712ahjeacjh"
spn_tenant_id = "33572583-d294-5b56-c4e6-dcf9a297ec17"
client_admin_ssh = "C:/Temp/rsa.pub"
deployment_flavor = "DevOps"
deploy_bastion = false
github_username = "GitHubUser"
```

- Variable Reference:
- **_`azure_location`_** - Azure location code (e.g. 'eastus', 'westus2', etc.)
- **_`resource_group_name`_** - Resource group which will contain all of the ArcBox artifacts
- **_`spn_client_id`_** - Your Azure service principal id
- **_`spn_client_secret`_** - Your Azure service principal secret
- **_`spn_tenant_id`_** - Your Azure tenant id
- **_`client_admin_ssh`_** - SSH public key path, used for Linux VMs
- **_`deployment_flavor`_** - Use the value "DevOps" to specify that you want to deploy the DevOps flavor of ArcBox
- _`deployBastion`_ - Set to *`true`* if you want to use Azure Bastion to connect to _ArcBox-Client_
- _`client_admin_username`_ - Admin username for Windows & Linux VMs
- _`client_admin_password`_ - Admin password for Windows VMs. Password must have 3 of the following: 1 lower case character, 1 upper case character, 1 number, and 1 special character. The value must be between 12 and 123 characters long.
- **_`workspace_name`_** - Unique name for the ArcBox Log Analytics workspace
- _`github_username`_ - Specify the name of your GitHub account where you cloned the Sample Apps repo

> **Note:** Any variables in bold are required. If any optional parameters are not provided, defaults will be used.

- Now you will deploy the Terraform file. Navigate to the local cloned [deployment folder](https://github.com/microsoft/azure_arc/tree/main/azure_jumpstart_arcbox/bicep) and run the commands below:

```shell
terraform init
terraform plan -out=infra.out
terraform apply "infra.out"
```

- Example output from `terraform init`:

![terraform init](./terraform_init.png)

- Example output from `terraform plan -out=infra.out`:

![terraform plan](./terraform_plan.png)

- Example output from `terraform apply "infra.out"`:

![terraform plan](./terraform_apply.png)

> **Note:** If you see any failure in the deployment, please check the [troubleshooting guide](#basic-troubleshooting).

## Start post-deployment automation

Once your deployment is complete, you can open the Azure portal and see the ArcBox resources inside your resource group. You will be using the _ArcBox-Client_ Azure virtual machine to explore various capabilities of ArcBox such as GitOps configurations and Key Vault integration. You will need to remotely access _ArcBox-Client_.
Expand Down Expand Up @@ -847,7 +780,6 @@ The following tools are including on the _ArcBox-Client_ VM.
- Visual Studio Code
- Putty
- 7zip
- Terraform
- Git
- ZoomIt

Expand Down
Binary file removed docs/azure_jumpstart_arcbox/DevOps/terraform_apply.png
View file
Open in desktop
Binary file not shown.
Binary file removed docs/azure_jumpstart_arcbox/DevOps/terraform_init.png
View file
Open in desktop
Binary file not shown.
Binary file removed docs/azure_jumpstart_arcbox/DevOps/terraform_plan.png
View file
Open in desktop
Binary file not shown.
65 changes: 1 addition & 64 deletions docs/azure_jumpstart_arcbox/Full/_index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -58,15 +58,12 @@ ArcBox provides multiple paths for deploying and configuring ArcBox resources. D
- Azure portal
- ARM template via Azure CLI
- Bicep
- Terraform

![Deployment flow diagram for ARM-based deployments](./deploymentflow.png)

![Deployment flow diagram for Terraform-based deployments](./deploymentflow_tf.png)

ArcBox uses an advanced automation flow to deploy and configure all necessary resources with minimal user interaction. The previous diagrams provide an overview of the deployment flow. A high-level summary of the deployment is:

- User deploys the primary ARM template (_azuredeploy.json_), Bicep file (_main.bicep_), or Terraform plan (_main.tf_). These objects contain several nested objects that will run simultaneously.
- User deploys the primary ARM template (_azuredeploy.json_) or Bicep file (_main.bicep_). These objects contain several nested objects that will run simultaneously.
- ClientVM ARM template/plan - deploys the Client Windows VM. This is the Hyper-V host VM where all user interactions with the environment are made from.
- Storage account template/plan - used for staging files in automation scripts
- Management artifacts template/plan - deploys Azure Log Analytics workspace and solutions and Azure Policy artifacts
Expand Down Expand Up @@ -280,65 +277,6 @@ ArcBox uses an advanced automation flow to deploy and configure all necessary re

> **Note:** If you see any failure in the deployment, please check the [troubleshooting guide](#basic-troubleshooting).

## Deployment Option 4: Terraform Deployment

- Clone the Azure Arc Jumpstart repository

```shell
git clone https://github.com/microsoft/azure_arc.git
```

- Download and install the latest version of Terraform [here](https://www.terraform.io/downloads.html)

> **Note:** Terraform 1.x or higher is supported for this deployment. Tested with Terraform v1.011.

- Create a `terraform.tfvars` file in the root of the terraform folder and supply some values for your environment.

```HCL
azure_location = "westus2"
spn_client_id = "1414133c-9786-53a4-b231-f87c143ebdb1"
spn_client_secret = "fakeSecretValue123458125712ahjeacjh"
spn_tenant_id = "33572583-d294-5b56-c4e6-dcf9a297ec17"
client_admin_ssh = "C:/Temp/rsa.pub"
deployment_flavor = "Full"
```

- Variable Reference:
- **_`azure_location`_** - Azure location code (e.g. 'eastus', 'westus2', etc.)
- **_`resource_group_name`_** - Resource group which will contain all of the ArcBox artifacts
- **_`spn_client_id`_** - Your Azure service principal id
- **_`spn_client_secret`_** - Your Azure service principal secret
- **_`spn_tenant_id`_** - Your Azure tenant id
- **_`client_admin_ssh`_** - SSH public key path, used for Linux VMs
- **_`deployment_flavor`_** - Use the value "Full" to specify that you want to deploy the full version of ArcBox
- _`client_admin_username`_ - Admin username for Windows & Linux VMs
- _`client_admin_password`_ - Admin password for Windows VMs. Password must have 3 of the following: 1 lower case character, 1 upper case character, 1 number, and 1 special character. The value must be between 12 and 123 characters long.
- **_`workspace_name`_** - Unique name for the ArcBox Log Analytics workspace

> **Note:** Any variables in bold are required. If any optional parameters are not provided, defaults will be used.

- Now you will deploy the Terraform file. Navigate to the local cloned [deployment folder](https://github.com/microsoft/azure_arc/tree/main/azure_jumpstart_arcbox/terraform) and run the commands below:

```shell
terraform init
terraform plan -out=infra.out
terraform apply "infra.out"
```

- Example output from `terraform init`:

![terraform init](./terraform_init.png)

- Example output from `terraform plan -out=infra.out`:

![terraform plan](./terraform_plan.png)

- Example output from `terraform apply "infra.out"`:

![terraform plan](./terraform_apply.png)

> **Note:** If you see any failure in the deployment, please check the [troubleshooting guide](#basic-troubleshooting).

## Start post-deployment automation

Once your deployment is complete, you can open the Azure portal and see the ArcBox resources inside your resource group. You will be using the _ArcBox-Client_ Azure virtual machine to explore various capabilities of ArcBox such as GitOps configurations and Key Vault integration. You will need to remotely access _ArcBox-Client_.
Expand Down Expand Up @@ -622,7 +560,6 @@ The following tools are included in the _ArcBox-Client_ VM.
- Visual Studio Code
- Putty
- 7zip
- Terraform
- Git
- SqlQueryStress

Expand Down
Binary file removed docs/azure_jumpstart_arcbox/Full/terraform_apply.png
View file
Open in desktop
Binary file not shown.
Binary file removed docs/azure_jumpstart_arcbox/Full/terraform_init.png
View file
Open in desktop
Binary file not shown.
Binary file removed docs/azure_jumpstart_arcbox/Full/terraform_plan.png
View file
Open in desktop
Binary file not shown.
67 changes: 1 addition & 66 deletions docs/azure_jumpstart_arcbox/ITPro/_index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -46,15 +46,12 @@ ArcBox provides multiple paths for deploying and configuring ArcBox resources. D
- Azure portal
- ARM template via Azure CLI
- Bicep
- Terraform

![Deployment flow diagram for ARM-based deployments](./deploymentflow.png)

![Deployment flow diagram for Terraform-based deployments](./deploymentflow_tf.png)

ArcBox uses an advanced automation flow to deploy and configure all necessary resources with minimal user interaction. The previous diagrams provide an overview of the deployment flow. A high-level summary of the deployment is:

- User deploys the primary ARM template (azuredeploy.json), Bicep file (main.bicep), or Terraform plan (main.tf). These objects contain several nested objects that will run simultaneously.
- User deploys the primary ARM template (azuredeploy.json) or Bicep file (main.bicep). These objects contain several nested objects that will run simultaneously.
- ClientVM ARM template/plan - deploys the Client Windows VM. This is the Hyper-V host VM where all user interactions with the environment are made from.
- Storage account template/plan - used for staging files in automation scripts
- Management artifacts template/plan - deploys Azure Log Analytics workspace and solutions and Azure Policy artifacts
Expand Down Expand Up @@ -280,67 +277,6 @@ ArcBox uses an advanced automation flow to deploy and configure all necessary re

> **Note:** If you see any failure in the deployment, please check the [troubleshooting guide](#basic-troubleshooting).

## Deployment Option 4: Terraform Deployment

- Clone the Azure Arc Jumpstart repository

```shell
git clone https://github.com/microsoft/azure_arc.git
```

- Download and install the latest version of Terraform [here](https://www.terraform.io/downloads.html)

> **Note:** Terraform 1.x or higher is supported for this deployment. Tested with Terraform v1.011.

- Create a `terraform.tfvars` file in the root of the terraform folder and supply some values for your environment.

```HCL
azure_location = "westus2"
spn_client_id = "1414133c-9786-53a4-b231-f87c143ebdb1"
spn_client_secret = "fakeSecretValue123458125712ahjeacjh"
spn_tenant_id = "33572583-d294-5b56-c4e6-dcf9a297ec17"
user_ip_address = "99.88.99.88"
client_admin_ssh = "C:/Temp/rsa.pub"
deployment_flavor = "ITPro"
```

- Variable Reference:
- **_`azure_location`_** - Azure location code (e.g. 'eastus', 'westus2', etc.)
- **_`resource_group_name`_** - Resource group which will contain all of the ArcBox artifacts
- **_`spn_client_id`_** - Your Azure service principal id
- **_`spn_client_secret`_** - Your Azure service principal secret
- **_`spn_tenant_id`_** - Your Azure tenant id
- **_`user_ip_address`_** - Your local IP address. This is used to allow remote RDP connections to the Client Windows VM. If you don't know your public IP, you can find it [here](https://www.whatismyip.com/)
- **_`client_admin_ssh`_** - SSH public key path, used for Linux VMs
- **_`deployment_flavor`_** - Use the value "ITPro" to specify that you want to deploy ArcBox for IT Pros
- _`client_admin_username`_ - Admin username for Windows & Linux VMs
- _`client_admin_password`_ - Admin password for Windows VMs. Password must have 3 of the following: 1 lower case character, 1 upper case character, 1 number, and 1 special character. The value must be between 12 and 123 characters long.
- **_`workspace_name`_** - Unique name for the ArcBox Log Analytics workspace

> **Note:** Any variables in bold are required. If any optional parameters are not provided, defaults will be used.

- Now you will deploy the Terraform file. Navigate to the local cloned deployment folder and run the commands below:

```shell
terraform init
terraform plan -out=infra.out
terraform apply "infra.out"
```

- Example output from `terraform init`:

![terraform init](./terraform_init.png)

- Example output from `terraform plan -out=infra.out`:

![terraform plan](./terraform_plan.png)

- Example output from `terraform apply "infra.out"`:

![terraform plan](./terraform_apply.png)

> **Note:** If you see any failure in the deployment, please check the [troubleshooting guide](#basic-troubleshooting).

## Start post-deployment automation

Once your deployment is complete, you can open the Azure portal and see the ArcBox resources inside your resource group. You will be using the _ArcBox-Client_ Azure virtual machine to explore various capabilities of ArcBox such as GitOps configurations and Key Vault integration. You will need to remotely access _ArcBox-Client_.
Expand Down Expand Up @@ -557,7 +493,6 @@ The following tools are including on the _ArcBox-Client_ VM.
- Visual Studio Code
- Putty
- 7zip
- Terraform
- Git

### Next steps
Expand Down
Binary file removed docs/azure_jumpstart_arcbox/ITPro/terraform_apply.png
View file
Open in desktop
Binary file not shown.
Binary file removed docs/azure_jumpstart_arcbox/ITPro/terraform_init.png
View file
Open in desktop
Binary file not shown.
Binary file removed docs/azure_jumpstart_arcbox/ITPro/terraform_plan.png
View file
Open in desktop
Binary file not shown.
Loading
Loading