Add "Config" to list of possible generators

[foot]

So we can enable it and avoid this error:

failed to generate template for set monitoring-example: generator Config not enabled

[foot]

You can test by setting up the gitopssets controller.. one of the easier ways is to

• tilt up in weave-gitops-enterprise

Configure gs-sets to use this tag and add a config generator:

diff --git a/charts/mccp/values.yaml b/charts/mccp/values.yaml
index 276c49387..6d3c21148 100644
--- a/charts/mccp/values.yaml
+++ b/charts/mccp/values.yaml
@@ -195,6 +195,8 @@ gitopssets-controller:
   enabled: true
   controllerManager:
     manager:
+      image:
+        tag: pr-126
       args:
         - --health-probe-bind-address=:8081
         - --metrics-bind-address=127.0.0.1:8080
diff --git a/tools/dev-resources/gitopssets/gitopsset-config.yaml b/tools/dev-resources/gitopssets/gitopsset-config.yaml
new file mode 100644
index 000000000..36362eade
--- /dev/null
+++ b/tools/dev-resources/gitopssets/gitopsset-config.yaml
@@ -0,0 +1,36 @@
+apiVersion: v1
+kind: ConfigMap
+metadata:
+  name: test-cm
+data:
+  name: test-config
+  demo: test-value
+---
+apiVersion: templates.weave.works/v1alpha1
+kind: GitOpsSet
+metadata:
+  name: imagepolicy-matrix-example
+  namespace: default
+spec:
+  generators:
+    - matrix:
+        generators:
+          - config:
+              kind: ConfigMap
+              name: test-cm
+          - list:
+              elements:
+                - cluster: dev-cluster
+                  version: 1.0.0
+                - cluster: prod-cluster
+                  version: 1.0.0
+  templates:
+    - content:
+        kind: ConfigMap
+        apiVersion: v1
+        metadata:
+          name: "demo-configmap-{{ .Element.cluster }}"
+        data:
+          generatedValue: "{{ .Element.demo }}"
+          cluster: "{{ .Element.cluster }}"
+          version: "{{ .Element.version }}"

[foot]

[enekofb]

@paulcarlton-ww suggesting if we could release this version once merge to help with https://github.com/weaveworks/weave-gitops-interlock/issues/563