Skip to main content

Updating Urbi Pro

Updating Pro UI​

  1. Fetch new installation artifacts.

    1. In the DGCLI configuration file, specify:

      • New version of the pro component (see Urbi Pro releases).
      • Versions of core and api-platform components required to install the new Urbi Pro version (see the Dependencies subsection in the Urbi Pro releases description).

    2. Run the fetch command.

      For more settings, see DGCLI command-line arguments.

  2. Copy the path to a new manifest file from the command output and set it as a value to the dgctlStorage.manifest parameter in the values-pro-ui.yaml configuration file. For more information, see the installation guide.

    Important

    If during a regular update of the Pro UI service you do not want to import new data, use the same manifest as in the previous import. In other cases, using a new manifest is recommended.

  3. Check out breaking changes. If necessary, update other settings in the values-pro-ui.yaml configuration file.

  4. Run the command to update the service:

    helm upgrade --version=VERSION --atomic --values ./values-pro-ui.yaml pro-ui 2gis-on-premise/pro-ui

    In the --version parameter, set the new pro component version that you specified in the DGCLI configuration file.

  5. Test if the update succeeded.

Updating Pro API​

  1. (Recommended) Back up datasets uploaded by users.

  2. Fetch new installation artifacts.

    1. In the DGCLI configuration file, specify:

      • New version of the pro component (see Urbi Pro releases).
      • Versions of core and api-platform components required to install the new Urbi Pro version (see the Dependencies subsection in the Urbi Pro releases description).

    2. Run the fetch command. Additionally you can specify the following flags:

      • To update only the service image, add the --only-apps flag after the pull command.
      • To update only data, add the --only-data flag after the pull command.
      • To update both service and data, run the command without the above flags.

      For more settings, see DGCLI command-line arguments.

  3. Copy the path to a new manifest file from the command output and set it as a value to the dgctlStorage.manifest parameter in the values-pro-api.yaml configuration file. For more information, see the installation guide.

    Important

    If during a regular update of the Pro API service you do not want to import new data, use the same manifest as in the previous import. In other cases, using a new manifest is recommended.

  4. Check out breaking changes. If necessary, update other settings in the values-pro-api.yaml configuration file.

  5. Run the command to update the service:

    helm upgrade --version=VERSION --atomic --values ./values-pro-api.yaml pro-api 2gis-on-premise/pro-api

    In the --version parameter, set the pro component version:

    • To update only the service or both service and data, use the new version that you specified in the DGCLI configuration file.
    • To update only data, set the currently installed version.

  6. Test if the update succeeded.