Erik Osterman (CEO @ Cloud Posse)

Actually, I think [in your example](https://github.com/mumoshu/aws-secret-operator#usage), you already show how this is possible: ``` $ aws secretsmanager put-secret-value\ --secret-id prod/mysecret \ --secret-string '{"foo":"bar"}'` ``` So maybe it already works? =)...

Would still love to see this! =)

In this particular use-case, I don't even have access to kubernetes or helm. I just want to validate the `helmfile.yaml` template results is valid yaml and that the `--set` arguments...

Just to be extra clear, with the upcoming `0.13.0` release, the entire `helmfile.yaml` is a template. We're using the current `master`. No mechanism exists to validate the output from the...

Here's an example of the complex `helmfile.yaml`: https://github.com/cloudposse/geodesic/pull/124/files

Yes, that sounds like a great idea. The `lint` would satisfy the helmfile validation. That said, I still want to know what the command looks like before executing it as...

I think that sounds good. For clarification, are you saying that `helmfile sync --dry-run` would also call `helm upgrade --install --dry-run`? Basically, in my use-case, I don't even have `helm`...

> you'd occasionally need to encrypt/decrypt secrets referenced via secrets: section, which results in helm secret dec calls. Aha, yes, we use `chamber` instead, which is why this didn't occur...

Is this the same as #19? (which was unfortunately rejected)

Also, #304 could solve this pain point by making it easier to run a series of set up commands that do not get recorded.