Urbi Pro | On‑Premise | 2GIS Documentation
On‑Premise

Updating Urbi Pro

  1. Fetch new installation artifacts.

    To get artifacts for the Pro UI service only, add --services=pro-ui after the pull command. Without this parameter artifacts for all services will be fetched by default.

    See the reference of 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 service installation instructions.

    Important

    If during a regular update of the Pro UI service you do not want to import new data, specify the manifest used for 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=1.32.0 --atomic --values ./values-pro-ui.yaml pro-ui 2gis-on-premise/pro-ui
    
  5. Test if the update succeeded.

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

  2. Fetch new installation artifacts.

    • 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 flags above.

    To get artifacts for the Pro API service only, add --services=pro after the pull command. Without this parameter artifacts for all services will be fetched by default.

    See the reference of 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 service installation instructions.

    Important

    If during a regular update of the Pro API service you do not want to import new data, specify the manifest used for 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:

    • To update the service only or both service and data:

      helm upgrade --version=1.32.0 --atomic --values ./values-pro-api.yaml pro-api 2gis-on-premise/pro-api
      
    • To update data only, set the currently installed On-Premise version to the --version parameter:

      helm upgrade --version=VERSION --atomic --values ./values-pro-api.yaml pro-api 2gis-on-premise/pro-api
      
  6. Test if the update succeeded.