From b75d0f3603fef2c76c546bde6e0060411b4c19c9 Mon Sep 17 00:00:00 2001
From: Silvio Rhatto <rhatto@riseup.net>
Date: Tue, 22 Mar 2016 13:46:16 -0300
Subject: Rename 'hiera' to 'config'

---
 hiera/hiera.yaml | 33 ---------------------------------
 1 file changed, 33 deletions(-)
 delete mode 100644 hiera/hiera.yaml

(limited to 'hiera/hiera.yaml')

diff --git a/hiera/hiera.yaml b/hiera/hiera.yaml
deleted file mode 100644
index a8ae792..0000000
--- a/hiera/hiera.yaml
+++ /dev/null
@@ -1,33 +0,0 @@
----
-:backends:
-  - yaml
-:yaml:
-  # Right now vagrant and puppet are not fully supporting
-  # a relative datadir. For it to work, we were forced to
-  # create a manifests/hiera symlink. This should be
-  # reconsidered in the future.
-  #
-  # See http://docs.vagrantup.com/v2/provisioning/puppet_apply.html
-  :datadir: '%{settings::confdir}/hiera'
-:hierarchy:
-  #
-  # Put in the secrets folder all sensitive information that
-  # wont be spread into every system if you're using the Hydra Suite.
-  #
-  # We also recommend to leave only encrypted data in your hiera config.
-  #
-  - 'secrets/node/%{::clientcert}'
-  - 'secrets/role/%{::nodo::role}'
-  - 'secrets/location/%{::nodo::location}'
-  - 'secrets/domain/%{::domain}'
-
-  #
-  # All other stuff goes in regular YAML files.
-  #
-  - 'node/%{::clientcert}'
-  - 'role/%{::nodo::role}'
-  - 'virtual/%{::virtual}'
-  - 'location/%{::nodo::location}'
-  - 'domain/%{::domain}'
-  - bootstrap
-  - common
-- 
cgit v1.2.3