Integrating Customization Changes without Rebuild#

Note

This section assumes that the custom changes are made in a yaml file. Eg: my_override_values.yaml based off the values.yaml file of the locally downloaded helm chart of choice. The steps below describe integrating the change by upgrading an already deployed helm chart.

  1. Save the custom changes to your my_override_values.yaml file.

  2. Point to the location of your locally saved my_override_values.yaml file in the config-template.yml of your deployment script as the value for spec > app > configs > app_settings > helm_chart > local > user_value_override_files. Note that the helm chart path to be provided is the path to the locally downloaded/saved helm chart. Refer to Deployment for options on deployment script. A snippet of the relevant section in the config-template.yaml is provided below.

app:
  configs:
    app_settings:
      # k8s_namespace:   '<replace-with-k8s-namespace-for-app-chart-to-deploy-defaults-to-app>'
      # helm_chart:
        # local:
          #  enable: true
          #  path: '<absolute-path-of-helm-chart-present-locally>'
          #  release_name:   '<replace-with-release-name-for-helm-deploy-defaults-to-'tokkio-app'  >'
          #  user_value_override_files:   ['list-of-absolute-path-of-value-override-files']

  1. Run the deployment script to reflect the changes. Use the correct path and name for your config-template in the command shown below:

    ./envbuild.sh install --component app --config-file ./config-template.yml