Extend configMapGenerator to work with application.yml files

[mcdolding]

The configMapGenerator will manage a configmap using properties of the form myproperty=myvalue.
However I have springboot and quarkus applications which are configured using application.yml files (in place of application.properties files). At runtime we provide configmaps of the form:

  - kind: ConfigMap
    apiVersion: v1
    data:
      application.yml: |-
        my:
	  nested:
	    property1: myvalue1
	    property2: myvalue2

Would it be possible to extend configMapGenerator to handle yml properties?

[stormqueen1990]

Hello there, @mcdolding! 👋🏻

Currently, it's possible to add YAML file contents to a Kustomization using the configMapGenerator through the files field, or the --from-file CLI option if you're using kustomize edit add. For example, in a directory structure such as:

.
|____kustomization.yaml
|____application.yaml

where your application.yaml has a content such as:

server:
  port: 8080

you could use kustomize edit add configmap test-cm --namespace test-ns --from-file=application.yaml to generate the following kustomization.yaml:

apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization
configMapGenerator:
- files:
  - application.yaml
  name: test-cm
  namespace: test-ns

which would then generate the following structure on kustomize build:

apiVersion: v1
data:
  application.yaml: |
    server:
      port: 8080
kind: ConfigMap
metadata:
  name: test-cm-bd9fg9hb5h
  namespace: test-ns

It's also possible to override the YAML key when using --from-file by specifying it before the file name. For instance, running kustomize edit add configmap test-cm --namespace test-ns --from-file=test.yaml=application.yaml would yield:

apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization
configMapGenerator:
- files:
  - test.yaml=application.yaml
  name: test-cm
  namespace: test-ns

which then results in:

apiVersion: v1
data:
  test.yaml: |
    server:
      port: 8080
kind: ConfigMap
metadata:
  name: test-cm-d76c2hh757
  namespace: test-ns

Does that address your use case?

[mcdolding]

Thanks for your detailed response. This is exactly what I need.