# Update EDITable Container Instance (for 3.x users)

This guide details the steps required to update the EDITable container instance within an Azure on-premises environment. Please follow these instructions carefully to ensure a smooth and successful update. 

## **1. Edit the CNI Configuration**

1. Open your Azure CLI window and run the following command:

{% code overflow="wrap" %}

```bash
az container export -g <resource group name> -n <container instance name > --file output_file
```

{% endcode %}

![Launch Azure CLI and execute the command](/files/INJCh0Fh5jncBgQBfJC9)

2. To download the output file, click **Manage files -> Download** and enter the path of the output file. Click **Download**.

<figure><img src="/files/BBuWYyLjQ5obqI8YB4F9" alt=""><figcaption><p>Download the output file</p></figcaption></figure>

3. Click on the output file to download it to your local system.

![Download locally](/files/YVrQT5p3ToD6nfiBPhlt)

4. Now configure the below-listed container configurations in this file for EDITable container deployment.

### **Containers Instance List**

The following are the set of containers required for the EDITable deployment of Azure container instance.

{% hint style="info" %}
**Note: Transition from Default Azure Domain to Custom Domain**

When transitioning to a custom domain (e.g., <https://webapp.inforiver.com>) from the default Azure domain (e.g., <https://webapp.azurewebsites.net>), it is necessary to update the URL in the configuration settings of both the Azure App Service and the associated Container Instances. Specifically, ensure the environment variable `ADMIN_PORTAL_URL` is updated to reflect the new custom domain in both services.
{% endhint %}

#### **i) Inforiver Cron**

```yaml
- name: inforiver-cron-container
    properties:
      configMap:
        keyValuePairs: {}
      environmentVariables:
      - name: ADMIN_PORTAL_URL
        value: <Admin Portal URL>
      image: turing.azurecr.io/turing-cron:<tag>
      ports: []
      resources:
        requests:
          cpu: 0.25
          memoryInGB: 0.5
```

#### **ii) Inforiver Audit**

```yaml
- name: inforiver-audit-container
    properties:
      configMap:
        keyValuePairs: {}
      environmentVariables:
      - name: ADMIN_PORTAL_URL
        value: <Admin Portal URL>
      image: turing.azurecr.io/turing-audit:<tag>
      ports: []
      resources:
        requests:
          cpu: 0.25
          memoryInGB: 0.5
```

#### **iii) Inforiver Worker**

```yaml
- name: inforiver-worker-container
    properties:
      configMap:
        keyValuePairs: {}
      environmentVariables:
      - name: ADMIN_PORTAL_URL
        value: <Admin Portal URL>
      image: turing.azurecr.io/turing-worker:<tag>
      ports: []
      resources:
        requests:
          cpu: 0.25
          memoryInGB: 2.0
```

#### **iv) Inforiver Orchestrator**

```yaml
- name: inforiver-orchestrator-container
    properties:
      configMap:
        keyValuePairs: {}
      environmentVariables:
      - name: ADMIN_PORTAL_URL
        value: <Admin Portal URL>
      image: turing.azurecr.io/turing-orchestrator:<tag>
      ports: []
      resources:
        requests:
          cpu: 0.25
          memoryInGB: 1.0
```

#### **v) Inforiver Comment Worker**

```yaml
- name: inforiver-comment-worker-container
    properties:
      configMap:
        keyValuePairs: {}
      environmentVariables:
      - name: ADMIN_PORTAL_URL
        value: <Admin Portal URL>
      - name: SERVICE_NAME
        value: "commentWorker"
      image: turing.azurecr.io/turing-worker:<tag>
      ports: []
      resources:
        requests:
          cpu: 0.25
          memoryInGB: 1.0
```

#### **vi) MDM Worker**

```yaml
- name: mdm-worker-container
    properties:
      configMap:
        keyValuePairs: {}
      environmentVariables:
      - name: ADMIN_PORTAL_URL
        value: <Admin Portal URL>
      - name: PRODUCT_BUILD
        value: mde
      image: turing.azurecr.io/turing-mdm-worker:<tag>
      ports: []
      resources:
        requests:
          cpu: 1
          memoryInGB: 3.0
```

#### vii) EDITable Visual Worker

```yaml
- name: editable-visual-worker-container
    properties:
      configMap:
        keyValuePairs: {}
      environmentVariables:
      - name: ADMIN_PORTAL_URL
        value: <Admin Portal URL>
      - name: PRODUCT_BUILD
        value: mde
      image: turing.azurecr.io/turing-visual-worker:<tag>
      ports: []
      resources:
        requests:
          cpu: 0.25
          memoryInGB: 3.0
```

5. After adding the list of container configurations correctly in the container instances, verify the steps.
6. Provide the username and password for pulling the image from the registry. You would have received this information during the initial deployment. If not, please get in touch with our support team.
7. Remove the IP configuration section from the configuration file from the ACI.

<figure><img src="/files/eUpfElgyKyin2G3X0EZN" alt=""><figcaption><p>Remove the IP configuration</p></figcaption></figure>

8. Update the API version as specified below.

apiVersion: '2023-02-01-preview'

## **2. Create ACI**

Add the listed set of **EDITable** containers into a configuration file and create an ACI named **editablecontainerinstance.**

After adding all the containers in the configuration file, execute the following command to create a container instance.

{% code overflow="wrap" %}

```bash
az container create -g <resource group name> -n <container instance name> --file output_file
```

{% endcode %}

The CNI will start provisioning with the latest configuration.&#x20;

<figure><img src="/files/uyMljmMkykxysM4lCxbe" alt=""><figcaption><p>Create container instance</p></figcaption></figure>

Please wait until the status is complete.

By following the steps outlined in this guide, you will be able to successfully update your EDITable container instance. This update brings enhanced features and improvements that will benefit your Azure on-premises environment.

Ensure all steps are completed carefully and refer to the provided screenshots for additional assistance. If you encounter any issues or need further assistance, please contact our technical support team [here](https://inforiver.com/contact-us/).


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.inforiver.com/inforiver-enterprise-on-prem/upgrade/for-legacy-versions-updating-container-instances/update-editable-container-instance-for-3.x-users.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.