Difference between revisions of "Hiera Example"

From stoney cloud
Jump to: navigation, search
[unchecked revision][unchecked revision]
(Created page with " <pre> --- :backends: - ldap - yaml - json :ldap: :url:ldaps://ldap.stoney-cloud.org:636/ :binddn:cn=Manager,dc=stoney-cloud,dc=org :bindpw:secret :basedn:dc=sto...")
 
(explain a bit what this is)
Line 21: Line 21:
 
   - "%{::custom_location}"
 
   - "%{::custom_location}"
 
   - common
 
   - common
 
 
</pre>
 
</pre>
  
 
Notes:
 
Notes:
 +
* This is an example of how a hiera config file might look with an mock ldap backend. The backend in question still needs to be found or written.
 
* mapping from a DN to directory structure would be nice, so we would rather have to write: ''ou=virtual machines/ou=services'' instead to be compatible with the already existing yaml/json backends or something different entirely
 
* mapping from a DN to directory structure would be nice, so we would rather have to write: ''ou=virtual machines/ou=services'' instead to be compatible with the already existing yaml/json backends or something different entirely
  
 
[[Category: Documentation]]
 
[[Category: Documentation]]

Revision as of 22:29, 5 January 2014

---
:backends:
  - ldap
  - yaml
  - json
:ldap:
  :url:ldaps://ldap.stoney-cloud.org:636/
  :binddn:cn=Manager,dc=stoney-cloud,dc=org
  :bindpw:secret
  :basedn:dc=stoney-cloud,dc=org
:yaml:
  :datadir: /etc/puppet/hieradata
:json:
  :datadir: /etc/puppet/hieradata
:hierarchy:
  - "ou=virtual machines,ou=services?sub?(&(sstNetworkHostName=%{::hostname})(sstNetworkDomainName=%{::domainname}))"
  - "ou=software stack,ou=configuration?sub?(uid=%{::rzUid})"
  - "%{::clientcert}"
  - "%{::custom_location}"
  - common

Notes:

  • This is an example of how a hiera config file might look with an mock ldap backend. The backend in question still needs to be found or written.
  • mapping from a DN to directory structure would be nice, so we would rather have to write: ou=virtual machines/ou=services instead to be compatible with the already existing yaml/json backends or something different entirely