Descriptor templates

All descriptors do use golang tempaltes which apply before the descriptors are parsed.
The context is build from the YAML object in the optional values.yaml file.
For each simple value there is a corresponding environment variable to alter the value.

IMPORTANT: All keys in the YAML are converted to lower case.

e.g.: If you have a key in your values.yaml someKeyWithCamelCase this will become:
somekeywithcamelcase - in the template context. So someKeyWithCamelCase will not be found

You can access all values from the context in the template.
The full key path is build by joining all key parts down the yaml structure with dots.
You can address a value from the values.yaml with {{ .<full-key-path> }}

project_name: a-simple-project
storage_class:
  azure:
    provisioner: kubernetes.io/azure-disk
    volume_binding_mode: Immediate

This can be accessed by:

name	description	exsample
read	read the content of a file	`{{ read some-content.txt }}`
indent	indent each line with X YAML indents	`{{ read .tls_cert_key_file
base64	encodes the content as base 64	`{{ read .license_file
toYaml	inserts the complete yaml branch or array of the specified value	`{{ toYaml .my_value }}`

Each key which has a simple value (string, int, bool) can be changed by a corresponding environment variable.
The name of the environment variable is build from the full key path.
- All dots are replaced by _
- The environment variable is all upper case

project_name: a-simple-project
storage_class:
  azure:
    provisioner: kubernetes.io/azure-disk
    volume_binding_mode: Immediate

This can be changed by the environment variables: