Tricia

Thanks for the advice; unfortunately it doesn't seem to help. Even with an `{{else}}` block in the template, consul-template still reports: ``` 2017/05/30 10:38:55 [ERR] (view) "secret(www-bbs-dev/static/db_demo2)" no secret exists...

Hello. I agree that this is similar to #776 (I read that one before I contemplated open a ticket), but I disagree that the answer should be the same, or...

Hello, @sethvargo. Can we reopen this ticket please? As I indicate in my message from May (and as I continue to believe), this request is substantially different from the request...

I think a reasonable implementation might be to accept an even-numbered list of key-value pairs that are populated into sub-fields of `.Data`, i.e., ``` {{ with secretOrDefault "/secret" "key" "NOT...

Yep, that's a great point. It doesn't seem like `secretOrDefault` would be reasonable with write semantics, so maybe `secretOrDefault` should not worry about the subsequent data arguments. A slightly more...

(which I see now is largely what you had previously suggested! so yeah, I think if we want to keep write semantics, that _would_ be the best option.) As for...

to expand more on merging, etc; msising keys in `.Data` can be handled already within consul-template, but a missing or inaccessible vault path entirely _can't_, it just causes rendering to...

@eikenb no worries, and thanks for taking a look at this after so long. In our environment, we don't use mounts that have side effects. So for us, it's a...

whoops, sorry about that! the latest commit fixes this issue. master: ``` $ rm -rf empty_1.0_amd64.deb; bin/fpm --deb-compression xz -s empty -t deb -n empty; dpkg-deb -I empty_1.0_amd64.deb Debian packaging...

hi, @zoni; could you take another look?