CityLens | On-Premise | Urbi Documentation

Updating CityLens

  1. 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 CityLens service only, add --services=citylens 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-citylens.yaml configuration file. For more information, see the service installation instructions.


    If during a regular update of the CityLens 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-citylens.yaml configuration file.

  4. Run the command to update the service:

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

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

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