Eric Sirianni

> @sirianni can you please confirm whether you reviewed the PR or whether you validated the code (did you run the entire example)? I did not run the example. I...

Any updates? Same problem here.

> Since the connection client/driver functions already have access to connection and query, would passing the user object as is work? This way drivers would have access to other user...

Has this gone cold? Our main reason for using YAML configs is that it integrates nicely with Helm and Kubernetes.

@lorendias What is that color picker app in the upper right of your screenshot?

+1 for adding first-class support for enumerated values (or a String-valued gauge). I have some internal customers trying to model this in their applications. Currently they are setting the enumerated...

You're right, the `tpl` function can just be used directly. I'm not sure why `helm` defines both `tpl` and `include` then.... :thinking: ```yaml {{ define "my-template" }} some-yaml: foo: {{...

> Do you have any idea on how we should differentiate per-helmfile values that can be accessed by {{ .Values }} vs the release-specific values? Should they be differentiated? Or...

> Merging release-specific values into {{ .Values }} can be a breaking change for people who have been using it to render release-specific values. Good point. > Would adding `{{...

Ah, I see. To preserve compatibility, there are two basic approaches: 1. _Reference_ the release-specific values with a new name. For example: ``` {{ .Release.Values }} ``` 2. _Declare_ the...