# ConfigMap Configs
Any file containing the extension `.yaml` will be turned into a ConfigMap. The name specified within the template utilizes the filename without extension: `config.<file name>` or `config.foobar` with the example displayed here.

### Example Config File `foobar.yaml`
```yaml
## foobar.yaml provides a default set of configuration options

## service author
author: "Pluto TV"

## name of the running application
name: "foobar"
## Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor. 
## Incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco.
## Laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate.

## log: logger configuration
log:
  ## log level used to filter logs of lesser severity (from highest to lowest):
  ## panic, fatal, error, warn, info, debug
  level: warn
  ## enable pretty colorized console logging. setting to false will output
  ## structured JSON logs. Recommended false in production.
  pretty: false
```
### Volume Mounts & Volumes
The ConfigMap's generated are **NOT** automatically mounted, and must be specified within the `values.yaml` within `deployment.volumeMounts` & `deployment.volumes` for this functionality.