chore: bump charts minor versions (#304)

Author: rm3l

charts/backstage/Chart.yaml

@@ -47,4 +47,4 @@ sources: []
 # Versions are expected to follow Semantic Versioning (https://semver.org/)
 # Note that when this chart is published to https://github.com/openshift-helm-charts/charts
 # it will follow the RHDH versioning 1.y.z
-version: 5.0.1
+version: 5.1.0

charts/backstage/README.md

@@ -1,7 +1,7 @@
 
 # RHDH Backstage Helm Chart for OpenShift
 
-![Version: 5.0.1](https://img.shields.io/badge/Version-5.0.1-informational?style=flat-square)
+![Version: 5.1.0](https://img.shields.io/badge/Version-5.1.0-informational?style=flat-square)
 ![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square)
 
 A Helm chart for deploying Red Hat Developer Hub, which is a Red Hat supported version of Backstage.
@@ -30,7 +30,7 @@ helm repo add bitnami https://charts.bitnami.com/bitnami
 helm repo add backstage https://backstage.github.io/charts
 helm repo add redhat-developer https://redhat-developer.github.io/rhdh-chart
 
-helm install my-backstage redhat-developer/backstage --version 5.0.1
+helm install my-backstage redhat-developer/backstage --version 5.1.0
 ```
 
 ## Introduction

charts/backstage/values.yaml

@@ -1,5 +1,4 @@
 nameOverride: developer-hub
-
 global:
   dynamic:
     # -- Array of YAML files listing dynamic plugins to include with those listed in the `plugins` field.
@@ -8,13 +7,11 @@ global:
       # -- List of dynamic plugins included inside the `rhdh` container image, some of which are disabled by default.
       # This file ONLY works with the `rhdh` container image.
       - "dynamic-plugins.default.yaml"
-
     # -- List of dynamic plugins, possibly overriding the plugins listed in `includes` files.
     # Every item defines the plugin `package` as a [NPM package spec](https://docs.npmjs.com/cli/v10/using-npm/package-spec),
     # an optional `pluginConfig` with plugin-specific backstage configuration, and an optional `disabled` flag to disable/enable a plugin
     # listed in `includes` files. It also includes an `integrity` field that is used to verify the plugin package [integrity](https://w3c.github.io/webappsec-subresource-integrity/#integrity-metadata-description).
     plugins: []
-
   # -- Shorthand for users who do not want to specify a custom HOSTNAME. Used ONLY with the DEFAULT upstream.backstage.appConfig value and with OCP Route enabled.
   clusterRouterBase: "apps.example.com"
   # -- Custom hostname shorthand, overrides `global.clusterRouterBase`, `upstream.ingress.host`, `route.host`, and url values in `upstream.backstage.appConfig`.
@@ -30,7 +27,6 @@ global:
       existingSecret: ""
       # -- Instead of generating a secret value, use the following value
       value: ""
-
   # -- Catalog index configuration for automatic plugin discovery.
   # The `install-dynamic-plugins.py` script pulls this image if the `CATALOG_INDEX_IMAGE` environment variable is set.
   # The `dynamic-plugins.default.yaml` file will be extracted and written to `dynamic-plugins-root` volume mount.
@@ -39,7 +35,6 @@ global:
       registry: quay.io
       repository: rhdh/plugin-catalog-index
       tag: "1.9"
-
 # -- Upstream Backstage [chart configuration](https://github.com/backstage/charts/blob/main/charts/backstage/values.yaml)
 # @default -- Use Openshift compatible settings
 upstream:
@@ -258,8 +253,7 @@ upstream:
     installDir: /opt/app-root/src
     podAnnotations:
       checksum/dynamic-plugins: >-
-        {{- include "common.tplvalues.render" ( dict "value"
-        .Values.global.dynamic "context" $) | sha256sum }}
+        {{- include "common.tplvalues.render" ( dict "value" .Values.global.dynamic "context" $) | sha256sum }}
   ingress:
     host: "{{ .Values.global.host }}"
   metrics:
@@ -313,71 +307,53 @@ upstream:
       - name: http-metrics
         port: 9464
         targetPort: 9464
-
 # -- OpenShift Route parameters
 route:
   # -- Route specific annotations
   annotations: {}
-
   # -- Enable the creation of the route resource
   enabled: true
-
   # -- Set the host attribute to a custom value. If not set, OpenShift will generate it, please make sure to match your baseUrl
   host: "{{ .Values.global.host }}"
-
   # -- Path that the router watches for, to route traffic for to the service.
   path: "/"
-
   # -- Wildcard policy if any for the route. Currently only 'Subdomain' or 'None' is allowed.
   wildcardPolicy: None
-
   # -- Route TLS parameters
   # <br /> Ref: https://docs.openshift.com/container-platform/4.9/networking/routes/secured-routes.html
   tls:
     # -- Enable TLS configuration for the host defined at `route.host` parameter
     enabled: true
-
     # -- Specify TLS termination.
     termination: "edge"
-
     # -- Certificate contents
     certificate: ""
-
     # -- Key file contents
     key: ""
-
     # -- Cert authority certificate contents. Optional
     caCertificate: ""
-
     # -- Contents of the ca certificate of the final destination.
     # <br /> When using reencrypt termination this file should be provided in order to have routers use it for health checks on the secure connection. If this field is not specified, the router may provide its own destination CA and perform hostname validation using the short service name (service.namespace.svc), which allows infrastructure generated certificates to automatically verify.
     destinationCACertificate: ""
-
     # --  Indicates the desired behavior for insecure connections to a route.
     # <br /> While each router may make its own decisions on which ports to expose, this is normally port 80. The only valid values are None, Redirect, or empty for disabled.
     insecureEdgeTerminationPolicy: "Redirect"
-
 # -- Test pod parameters
 test:
   # -- Whether to enable the test-connection pod used for testing the Release using `helm test`.
   enabled: true
-
   image:
     # -- Test connection pod image registry
     registry: quay.io
-
     # -- Test connection pod image repository. Note that the image needs to have both the `sh` and `curl` binaries in it.
     repository: curl/curl
-
     # -- Test connection pod image tag. Note that the image needs to have both the `sh` and `curl` binaries in it.
     tag: latest
-
   # -- Whether to inject a fake dynamic plugins npmrc secret.
   # <br />See RHDHBUGS-1893 and RHDHBUGS-1464 for the motivation behind this.
   # <br />This is only used for testing purposes and should not be used in production.
   # <br />Only relevant when `test.enabled` field is set to `true`.
   injectTestNpmrcSecret: false
-
 orchestrator:
   enabled: false
   #  Disable Serverless Logic Operator if it already exists on the cluster
@@ -402,28 +378,20 @@ orchestrator:
         cpu: "500m"
     # -- Secret name for the user-created secret to connect an external DB
     externalDBsecretRef: ""
-
     # -- Name for the user-configured external Database
     externalDBName: ""
-
     # -- Host for the user-configured external Database
     externalDBHost: ""
-
     # -- Port for the user-configured external Database
     externalDBPort: ""
-
     # -- Image for the init container used by the create-db job
     initContainerImage: "{{ .Values.upstream.postgresql.image.registry }}/{{ .Values.upstream.postgresql.image.repository }}:{{ .Values.upstream.postgresql.image.tag }}"
-
     # -- Image for the container used by the create-db job
     createDBJobImage: "{{ .Values.upstream.postgresql.image.registry }}/{{ .Values.upstream.postgresql.image.repository }}:{{ .Values.upstream.postgresql.image.tag }}"
-
     # -- Image for the container used by the sonataflow jobs service, optional and used for disconnected environments
     jobServiceImage: ""
-
     # -- Image for the container used by the sonataflow data index, optional and used for disconnected environments
     dataIndexImage: ""
-
   # -- Orchestrator plugins and their configuration
   plugins:
     # RHDHBUGS-1464: Note that the plugins here fetch the packages from their direct HTTP download URLs from the (official) Red Hat NPM Registry.

charts/orchestrator-infra/Chart.yaml

@@ -14,4 +14,4 @@ maintainers:
 type: application
 sources:
   - https://github.com/redhat-developer/rhdh-chart
-version: 0.4.0
+version: 0.5.0

charts/orchestrator-infra/README.md

@@ -1,7 +1,7 @@
 
 # Orchestrator Infra Chart for OpenShift
 
-![Version: 0.4.0](https://img.shields.io/badge/Version-0.4.0-informational?style=flat-square)
+![Version: 0.5.0](https://img.shields.io/badge/Version-0.5.0-informational?style=flat-square)
 ![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square)
 
 Helm chart to deploy the Orchestrator solution's required infrastructure suite on OpenShift, including OpenShift Serverless Operator and OpenShift Serverless Logic Operator, both required to configure Red Hat Developer Hub to use the Orchestrator.
@@ -25,7 +25,7 @@ Kubernetes: `>= 1.25.0-0`
 ```console
 helm repo add redhat-developer https://redhat-developer.github.io/rhdh-chart
 
-helm install my-orchestrator-infra redhat-developer/redhat-developer-hub-orchestrator-infra --version 0.4.0
+helm install my-orchestrator-infra redhat-developer/redhat-developer-hub-orchestrator-infra --version 0.5.0
 ```
 
 > **Tip**: List all releases using `helm list`

charts/orchestrator-software-templates-infra/Chart.yaml

@@ -10,7 +10,7 @@ kubeVersion: ">= 1.25.0-0"
 type: application
 sources:
   - https://github.com/redhat-developer/rhdh-software-templates-infrastructure
-version: 0.3.1
+version: 0.4.0
 maintainers:
   - name: Red Hat Developer Hub Team
     url: https://github.com/redhat-developer/rhdh-chart

charts/orchestrator-software-templates-infra/README.md

@@ -1,7 +1,7 @@
 
 # Orchestrator Software Templates Infra Chart for OpenShift (Community Version)
 
-![Version: 0.3.1](https://img.shields.io/badge/Version-0.3.1-informational?style=flat-square)
+![Version: 0.4.0](https://img.shields.io/badge/Version-0.4.0-informational?style=flat-square)
 ![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square)
 
 A Helm chart to install Openshift GitOps and Openshift Pipelines, which are required operators for installing the Orchestrator Software Templates to be available on RHDH.
@@ -25,7 +25,7 @@ Kubernetes: `>= 1.25.0-0`
 ```console
 helm repo add redhat-developer https://redhat-developer.github.io/rhdh-chart
 
-helm install my-orchestrator-software-templates-infra redhat-developer/orchestrator-software-templates-infra --version 0.3.1
+helm install my-orchestrator-software-templates-infra redhat-developer/orchestrator-software-templates-infra --version 0.4.0
 ```
 
 > **Tip**: List all releases using `helm list`

charts/orchestrator-software-templates/Chart.yaml

@@ -11,7 +11,7 @@ kubeVersion: ">= 1.25.0-0"
 type: application
 sources:
   - https://github.com/redhat-developer/rhdh-chart
-version: 0.2.1
+version: 0.3.0
 maintainers:
   - name: Red Hat Developer Hub Team
     url: https://github.com/redhat-developer/rhdh-chart

charts/orchestrator-software-templates/README.md

@@ -1,7 +1,7 @@
 
 # Orchestrator Software Templates Chart for Red Hat Developer Hub
 
-![Version: 0.2.1](https://img.shields.io/badge/Version-0.2.1-informational?style=flat-square)
+![Version: 0.3.0](https://img.shields.io/badge/Version-0.3.0-informational?style=flat-square)
 ![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square)
 
 This Helm chart deploys the Orchestrator Software Templates for Red Hat Developer Hub (RHDH) and other necessary GitOps configurations.
@@ -78,7 +78,7 @@ After configuring all prerequisites, you can install the chart with the followin
 ```console
 helm repo add redhat-developer https://redhat-developer.github.io/rhdh-chart
 
-helm install my-orchestrator-templates redhat-developer/orchestrator-software-templates --version 0.2.1
+helm install my-orchestrator-templates redhat-developer/orchestrator-software-templates --version 0.3.0
 ```
 
 Now, follow the instruction on the post-installation Notes. They will include the steps to create a custom values.yaml file to allow you to update the backstage chart