Deploy Inforiver Writeback Matrix using Terraform

1. Prerequisites

Please ensure that you have downloaded the files provided by our team before proceeding with the deployment. The following files are required for the deployment process.

Terraform File Contents

To run Terraform commands, the user must have the appropriate subscription-level roles, such as Contributor or User Access Administrator.

2. Adding information to the 'values.tfvars' file

Open the values.tfvars file in Visual Studio Code and input the required information to complete the deployment process.

values.tfvars file

The content of the values.tfvars file is provided below, where the corresponding values need to be entered.

1. Specify the Azure region where you would like to create all the resources.

Example options include:

• "Central US"

• "East US"

• "West US"

1. Enter the project name, which will be prefixed to all resources. Ensure to use only lowercase letters and refrain from using hyphens or underscores.

Recommended naming convention: Your organization name + production name + environment

Example: "lumelinforiverdev"

1. Input your organization's Azure subscription ID. This subscription ID will be used to deploy all resources under the specified subscription.

To locate the subscription ID:

• Navigate to the search bar and type "Subscription".

• Select the desired subscription from the results.

• Copy the subscription ID displayed.

Subscription ID Page

1. Enter the tag name for the container image. Example: “OPV4.4.0.0”

2. If you are running Terraform from outside the network, set the "is_microsoftnetwork" value to "false"; if you are executing Terraform from Microsoft networks, such as Azure DevOps, Azure CLI, or any other Microsoft network, set this value to "true".

3. For creating a Virtual Network (VNet) for the application:

• Set the "create_vnet" value to "true" to create a new VNet.

• If you have an existing VNet and need resources to be deployed on it, set this value to "false".

• If this value is set to "false",

  • 6.1. Enter the Azure Resource ID of the VNet where the subnets should be created. Leave this field blank if "create_vnet" is set to "true".

  • 6.2. Enter the name of the resource group where the VNet (from Step 6.1) is located. Leave this field blank if "create_vnet" is set to "true".

  • 6.3. Enter the name of the VNet referenced in Step 6.1. Leave this field blank if "create_vnet" is set to "true".

  • 6.4. Enter the IP address blocks for each subnet (Private, Public, Background) that should be created within the VNet. Each subnet must have a minimum of a /27 IP block. Leave this field blank if "create_vnet" is set to "true".

Example:

• Private → 172.16.0.0 - 172.16.0.31

• Public → 172.16.0.32 - 172.16.0.63

• Background → 172.16.0.64 - 172.16.0.95

To find the existing VNet ID:

• Open the Azure portal.

• Type "VNet" in the search bar.

• Select the VNet you want to reference and open it.

• Navigate to the "Properties" section and copy the resource ID.

Virtual Network Page

1. Provide your Docker username and password. These credentials can be obtained from the Inforiver License Portal.

To retrieve the Docker credentials:

• Visit inforiver.com
• Log in to your account.

• Navigate to On-Prem Subscription.

• Select Docker Credentials.

1. Enter the Workspace Domain Administrator username. This user will act as the initial administrator for the workspace during the bootstrap process. Additional administrators can be added after the initial setup.

2. Enter the domain name of the Workspace. This information can be found under your license details at inforiver.com → Login → On-Prem Subscription.

3. Enter the following credentials that were created in the Entra ID App section:

• App Tenant ID

• App Client ID

• App Secret ID

1. If integration with Google services is required, provide the Google API Client ID and Secret. If Google integration is not needed, enter a placeholder value such as "NA" or "null".

2. Provide the SMTP relay configuration details. If SMTP is not being configured at this stage, leave the default values as-is.

3. Deployment Instructions

Download the Terraform configuration files provided by our team as mentioned here, if you have not already done so.

1. Open a terminal (such as PowerShell or Bash) and navigate to the directory where the configuration files are located.

2. Run the following command to initialize the Terraform working directory:

terraform init

This command initializes the required Terraform providers and sets up the backend for the deployment.

Terraform init

1. Run the following command to review the execution plan and see the resources that will be created:

terraform plan -var-file="values.tfvars"

This command evaluates the configuration and returns a detailed list of all the resources that will be provisioned using the values specified in the values.tfvars file. It enables you to verify the planned actions before making any changes.

Terraform Plan

1. Run the following command to apply the changes outlined in the Terraform plan:

terraform apply -var-file="values.tfvars"

This command will initiate the deployment process and provision the required resources in your Azure environment.

Note: If you’ve set "is_microsoftnetwork" to "false" in the values.tfvars file, use the following commands instead:

terraform plan -var-file="values.tfvars" -refresh=false

terraform apply -var-file="values.tfvars" -refresh=false

The deployment may take approximately 30 to 40 minutes to complete. A significant portion of this time may be spent provisioning the Azure Redis Cache.

1. Once the deployment is complete, proceed with the post-deployment configuration.

2. To finalize your setup and obtain your Inforiver Enterprise Edition Power BI Extension, please proceed to the steps in the Custom Visual Generation page.