You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've got a spec/hiera.yaml file with spec.yaml as an additional entry so that onceover can get all the data that would otherwise come from a Hashicorp Vault instance. I also have a spec/hieradata directory, and my spec/hiera.yaml looks like:
---
version: 5
defaults:
datadir: hieradata
data_hash: yaml_data
hierarchy:
- name: Common data
paths:
- common.yaml
It appears that the hieradata isn't being read at all, as I then get errors like:
profile::traefik::host: failed
errors:
error during compilation: Evaluation Error: Error while evaluating a Function Call, Class[Profile::Traefik::Host]:
expects a value for parameter 'letsencrypt_email'
expects a value for parameter 'docker_network'
parameter 'auth_password' expects a String value, got Undef (line: 13, column: 1) on node 08713ae32bdc
I did try to move the spec common.yaml file into my main hieradata directory as hieradata/spec.yaml and just clone the root hiera.yaml, adding spec.yaml to the paths, but this doesn't seem to get read either.
Possibly related: I've always had manifest = site.pp in my environment.conf. If I keep that in, I get the following error:
profile::traefik::host: failed
errors:
Function lookup() did not find a value for the name 'classes'
Suggesting that the site.pp is indeed being read, and not ignore, as per the README.
I've got a
spec/hiera.yaml
file withspec.yaml
as an additional entry so that onceover can get all the data that would otherwise come from a Hashicorp Vault instance. I also have aspec/hieradata
directory, and myspec/hiera.yaml
looks like:I've got some data in
spec/hieradata/common.yaml
:It appears that the hieradata isn't being read at all, as I then get errors like:
I did try to move the spec
common.yaml
file into my main hieradata directory ashieradata/spec.yaml
and just clone the roothiera.yaml
, addingspec.yaml
to the paths, but this doesn't seem to get read either.Possibly related: I've always had
manifest = site.pp
in myenvironment.conf
. If I keep that in, I get the following error:Suggesting that the site.pp is indeed being read, and not ignore, as per the README.
My site.pp is simply:
The text was updated successfully, but these errors were encountered: