24eb60b34d
We are already organizing our hiera content basically the same way as ansible needs for variables to be provided. If we reorganize the directories slightly (to be coordinated with dirs on puppetmaster) then we can have a single directory do double-duty. Change-Id: I6ac90a7439ed8a5d9433d9526f37e44668b360ff
23 lines
1021 B
Django/Jinja
23 lines
1021 B
Django/Jinja
---
|
|
:hierarchy:
|
|
# Use private hieradata first. Align naming with ansible so that the private
|
|
# data can exist in a single copy for both ansible and puppet
|
|
# Puppet3 paths
|
|
- "hieradata/%{::environment}/host_vars/%{::fqdn}"
|
|
- "hieradata/%{::environment}/group_vars/%{group}" # no :: because group is set at nodescope
|
|
- "hieradata/%{::environment}/group_vars/all"
|
|
# Puppet4 paths
|
|
- "%{::environment}/hieradata/host_vars/%{::fqdn}"
|
|
- "%{::environment}/hieradata/group_vars/%{group}" # no :: because group is set at nodescope
|
|
- "%{::environment}/hieradata/group_vars/all"
|
|
# Use public hieradata second, also be environmentally aware. Keep this
|
|
# in the old structure so that we don't have to do a dance. There isn't much
|
|
# here, and it can be transferred piecemeal.
|
|
- "%{::environment}/hiera/fqdn/%{::fqdn}"
|
|
- "%{::environment}/hiera/group/%{group}" # no :: because group is set at nodescope
|
|
- "%{::environment}/hiera/common"
|
|
:backends:
|
|
- yaml
|
|
:yaml:
|
|
:datadir: "{{ puppet_hiera_datadir }}"
|