bfirsh/loom — pull request #35 by asimihsan (2014-06-12 08:20:13+00:00)
Title: hiera.yaml - remove non-compliant line

On both Fedora 18+ and Ubuntu 13.10+, whilst using Puppet 3.6.2, the
clientcert line in hiera.yaml prevents loom from working. Specifically
the error message that appears is:

```
[192.168.50.10] out: Error: Error from DataBinding 'hiera' while looking
up 'sudo::enable': (): found character that cannot start any
token while scanning for the next token at line 7 column 5 on node
ubuntu-14.04-amd64-vbox
[192.168.50.10] out: Wrapped exception:
[192.168.50.10] out: (): found character that cannot start any
token while scanning for the next token at line 7 column 5
[192.168.50.10] out: Wrapped exception:
[192.168.50.10] out: (): found character that cannot start any
token while scanning for the next token at line 7 column 5
[192.168.50.10] out: Error: Error from DataBinding 'hiera' while looking
up 'sudo::enable': (): found character that cannot start any
token while scanning for the next token at line 7 column 5 on node
ubuntu-14.04-amd64-vbox
[192.168.50.10] out:
```

It is possible that I have misconfigured my Puppet manifests and that is
causing this error. However removing the `%{::clientcert}` line from
`hiera.yaml` does not seem to have any negative consequences.

If you'd like a better, more minimal reproduction of this issue please let
me know; I have some Vagrant/Puppet scripts lying around.