You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Subscription ID can be obtained by running the `az login` command
50
54
-`azure_vault_name`is optional and uses a random value by default
51
55
- The Fabric Capacity SKU String can be found in Fabric's [Admin portal](https://app.fabric.microsoft.com/admin-portal/capacities/capacitiesList/trial?experience=fabric-developer) page.
56
+
- The values for `initSyncBatchSize`, `incrementalSyncBatchSize` and `incrementalSyncMaxTimeInterval` can be teaked through these parameters.
52
57
53
-
Variables can be stored on the `terraform.tfvars` file, or provided when `terraform plan` is executed.
58
+
Variables can be stored on the `terraform.tfvars` file, or provided when `terraform plan` is executed. You can copy the file `terraform_tfvars.example` as `terraform.tfvars` and update the values.
54
59
55
60
### Deploying without Secure network communication ###
56
61
@@ -108,7 +113,7 @@ Run `terraform plan --out plan_name.tfplan`, then `terraform apply "plan_name.tf
108
113
|Microsoft Azure|vault-\[randomid\]|Key vault|
109
114
|Microsoft Azure|mongodb-atlas-fabric-service-plan|App Service plan|
Most of the resources will have the `-[random-value]` suffix to avoid conflict incase the solution is deployed in more than one region on Azure.
136
+
130
137
# Deleting the deployed resources #
131
138
132
139
The deployed solution can be deleted using the Terraform CLI ```terraform destroy``` command, which will remove all resources from Fabric, Azure and MongoDB Atlas. The database will not be affected by this action.
0 commit comments