On 2020-03-03 11:17, Dirk Heinrichs wrote:
Hi,

while reading through the documentation about migrating to Hiera v5, the following questions came to my mind:

  * Can <Environment>/hiera.yaml be a symlink? Our setup is as such that
    each subdirectory (modules, manifests, hiera) of each environment is
    a clone of a Git repository, with different branches checked out.
    That means that in order to be able to enable per-environment
    hierarchies, I'd need to put hiera.yaml into the hiera repository.

I think it should work with a symlink. Report as an issue if it doesn't.

  * Does the eyaml backend NEED to have the path(s) specified? In our
    current (v3) setup, we configure eyaml globally and then simply mix
    encrypted and uncencrypted values in the files given in the
    hierarchy. As I understand the documentation, the eyaml backend now
    has its own hierarchy. Is this correct?


It does not have its own hierarchy. You can set up a default data provider and that can be the eyaml one as it supports both clear text and encrypted yaml content. You will need to repeat the default in each of the hiera.yaml files as I don't think the defaults carry over from global to env to module hiera.yaml configurations.

Hope that helps.
- henrik


Thanks...

Dirk
--
*Dirk Heinrichs*
Senior Systems Engineer, Delivery Pipeline
OpenText ™ Discovery | Recommind
*Phone*: +49 2226 15966 18
*Email*: dhein...@opentext.com <mailto:dhein...@opentext.com>
*Website*: www.recommind.de
Recommind GmbH, Von-Liebig-Straße 1, 53359 Rheinbach
Vertretungsberechtigte Geschäftsführer Gordon Davies, Madhu Ranganathan, Christian Waida, Registergericht Amtsgericht Bonn, Registernummer HRB 10646 This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail sind nicht gestattet.

--
You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com <mailto:puppet-users+unsubscr...@googlegroups.com>. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/637cf3f1b30ef085cbf67a27c07150adb2de3889.camel%40opentext.com <https://groups.google.com/d/msgid/puppet-users/637cf3f1b30ef085cbf67a27c07150adb2de3889.camel%40opentext.com?utm_medium=email&utm_source=footer>.


--

Visit my Blog "Puppet on the Edge"
http://puppet-on-the-edge.blogspot.se/

--
You received this message because you are subscribed to the Google Groups "Puppet 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/r3lol8%241914%241%40ciao.gmane.io.

Reply via email to