Helm Configurations for Customization Init Container

The customization init image can be configured via the helm charts. A new customizationInit section is added into the helm configuration values file.

The following configuration options are available under the customizationInit section in helm values yaml file:

customizationInit.enabled: Set to true to enable the customization init container feature.
customizationInit.dataSetup.enabled: Set to true to apply database updates for the customizations as part of the db setup job. It should be set to true only when the customization init image is newly configured or updated with any customizations, if not set it to false.
customizationInit.dataSetup.includeServicePackages: This configures the custom service packages to be included for database updates. Custom service package is the name of the top most parent folder for the packaged service jar. The default is set to all, implying all custom services bundled in the image will be picked for database updates. It can be set to to a list of comma separated service package names when a new set of custom services are added to the image. It can also be set to none when there are other customization changes added to the image but no changes are made to the custom services.
customizationInit.image.repository: This configures the image repository for the customization init image.
customizationInit.image.tag: This configures the image tag for the customization init image.
customizationInit.image.digest: This configures the image digest for the customization init image.
customizationInit.image.pullPolicy: This configures the image pull policy for the customization init image.
customizationInit.command: This configures any entrypoint override command for the customization init image. This should only be configured if the default entrypoint script is customized else it should be left empty for most cases.

Note: The core implementation behavior of the default customization init image entrypoint script, which is to copy the customizations from default location (/ibm/b2bi/customization) in the init image to the customization mount directory (/ibm/customization) should be kept intact when customizing the entrypoint script or configuring additional custom commands using the customizationInit.command parameter. This should be the case even if you add any new custom logic to the default entrypoint script.