feat: forward landing page app image overrides

charts/theia-cloud/Chart.yaml

@@ -15,7 +15,7 @@ type: application
 # This is the chart version. This version number should be incremented each time you make changes
 # to the chart and its templates, including the app version.
 # Versions are expected to follow Semantic Versioning (https://semver.org/)
-version: 1.4.0-next.2
+version: 1.4.0-next.3
 
 # This is the version number of the application being deployed. This version number should be
 # incremented each time you make changes to the application. Versions are not expected to

charts/theia-cloud/README.md

@@ -56,7 +56,7 @@ A Helm chart for Theia Cloud
 | keycloak.enable | bool | `false` | Whether keycloak authentication shall be used |
 | keycloak.realm | string | `"TheiaCloud"` | The Keycloak Realm. Only has to be specified when enable: true |
 | landingPage | object | (see details below) | Values related to the landing page |
-| landingPage.additionalApps | string | `nil` | The page may show these additional apps in a drop down. This is a map. The key maps to the app definition name The value is the label that is supposed to be shown in the UI  Example: different-app-definition:   label: "Different App Definition" further-app-definition:   label: "Further App Definition" |
+| landingPage.additionalApps | string | `nil` | The page may show these additional apps in a drop down. This is a map. The key maps to the app definition name. The value contains the label shown in the UI and may optionally include `image` or `Image` to override the logo name/path forwarded to the landing page config. Example: different-app-definition: label: "Different App Definition" image: "different-app-definition" |
 | landingPage.appDefinition | string | `"theia-cloud-demo"` | the app id to launch |
 | landingPage.disableInfo | bool | `false` | Should showing info title and text below the launch button be disabled true hides the info title and text false shows the info title and text |
 | landingPage.enabled | bool | `true` | Whether the landing page shall be enabled |

charts/theia-cloud/templates/landing-page-config-map.yaml

@@ -1,4 +1,5 @@
 {{- if .Values.landingPage.enabled }}
+{{- $root := . }}
 apiVersion: v1
 kind: ConfigMap
 metadata:
@@ -22,9 +23,13 @@ data:
       appDefinition: "{{ tpl (.Values.landingPage.appDefinition | toString) . }}",
       additionalApps: [
         {{- range $key, $val := .Values.landingPage.additionalApps }}
+        {{- $image := (get $val "image" | default (get $val "Image")) }}
         {
           serviceAuthToken: {{ $key | quote}},
           appName: {{ $val.label | quote }},
+          {{- if $image }}
+          image: {{ tpl ($image | toString) $root | quote }},
+          {{- end }}
         },
         {{- end }}
       ],

charts/theia-cloud/values.yaml

@@ -113,16 +113,19 @@ landingPage:
 
   # -- The page may show these additional apps in a drop down. This is a map.
   # The key maps to the app definition name
-  # The value is the label that is supposed to be shown in the UI
+  # The value contains the label shown in the UI and may optionally contain
+  # an image override that is forwarded to the landing page config.
   #
   # Example:
   # different-app-definition:
   #   label: "Different App Definition"
+  #   image: "different-app-definition"
   # further-app-definition:
   #   label: "Further App Definition"
   additionalApps:
     # different-app-definition:
     #   label: "Different App Definition"
+    #   image: "different-app-definition"
     # further-app-definition:
     #   label: "Further App Definition"