👐 Allow for multiline string and yaml objects

Author: thomascizeron

charts/nextcloud/README.md

@@ -228,7 +228,7 @@ The following table lists the configurable parameters of the nextcloud chart and
 | `podLabels`                                                 | Labels to be added at 'pod' level                                                                   | not set                    |
 | `podAnnotations`                                            | Annotations to be added at 'pod' level                                                              | not set                    |
 | `dnsConfig`                                                 | Custom dnsConfig for nextcloud containers                                                           | `{}`                       |
-| `extraManifests`                                            | List of additional Kubernetes manifests (YAML strings) to render with the release. Useful for custom resources like Traefik IngressRoutes, Middlewares, etc. | `[]`                       |
+| `extraManifests`                                            | List of additional Kubernetes manifests to render with the release. Each item can be either a YAML string (multi-line block) or a YAML object. Useful for custom resources like Traefik IngressRoutes, Middlewares, etc. | `[]`                       |
 
 ### Ingress
 #### Ingress Sticky-Sessions
@@ -777,7 +777,13 @@ kubectl exec $NEXTCLOUD_POD -- su -s /bin/sh www-data -c "php occ recognize:down
 
 ## Injecting Additional Manifests (`extraManifests`)
 
-You can inject additional Kubernetes manifests (such as Traefik IngressRoutes, Middlewares, or any custom resources) directly via `values.yaml` using the `extraManifests` value. This allows you to deploy custom resources alongside Nextcloud in a single Helm release.
+You can inject additional Kubernetes manifests (such as Traefik IngressRoutes, Middlewares, or any custom resources) directly via `values.yaml` using the `extraManifests` value.
+
+Each item in the list can be either:
+- a string containing valid YAML (multi-line block, e.g. with `|`), or
+- a YAML object (inline YAML structure).
+
+These manifests will be rendered as part of the Helm release.
 
 **Example usage in `values.yaml`:**
 
@@ -790,17 +796,14 @@ extraManifests:
       name: my-middleware
     spec:
       ...
-  - |
-    apiVersion: traefik.containo.us/v1alpha1
+  - apiVersion: traefik.containo.us/v1alpha1
     kind: IngressRoute
     metadata:
       name: my-ingressroute
     spec:
       ...
 ```
 
-Each item in the list should be a string containing valid YAML. These manifests will be rendered as part of the Helm release.
-
 # Backups
 Check out the [official Nextcloud backup docs](https://docs.nextcloud.com/server/latest/admin_manual/maintenance/backup.html). For your files, if you're using persistent volumes, and you'd like to back up to s3 backed storage (such as minio), consider using [k8up](https://github.com/k8up-io/k8up) or [velero](https://github.com/vmware-tanzu/velero).
 

charts/nextcloud/templates/extra-manifests.yaml

@@ -1,10 +1,14 @@
 {{- /*
   Renders extra manifests provided by the user in values.yaml under extraManifests.
-  Each item should be a string containing valid YAML (can be multi-document).
+  Each item can be a string (YAML block) or a YAML object.
 */ -}}
 {{- if .Values.extraManifests }}
 {{- range $manifest := .Values.extraManifests }}
 ---
+{{- if kindIs "string" $manifest }}
 {{ tpl $manifest $ }}
+{{- else }}
+{{ toYaml $manifest | nindent 0 }}
+{{- end }}
 {{- end }}
 {{- end }}

charts/nextcloud/test-values/extra-manifests.yml

@@ -0,0 +1,14 @@
+extraManifests:
+  - |
+    apiVersion: v1
+    kind: ConfigMap
+    metadata:
+      name: custom-config
+    data:
+      customKey: customValue
+  - apiVersion: v1
+    kind: Secret
+    metadata:
+      name: custom-secret
+    data:
+      secretKey: secretValue