Ah, I misunderstood Eric's response to Eli then. Well as long as the location is the same regardless of edition and only varies by version (I.e. $::puppetversion >= 4.5.0 or similar) it shouldn't muck things up too much.
On Tuesday, March 15, 2016, R.I.Pienaar <[email protected]> wrote: > > > On 15 Mar 2016, at 02:13, Rob Nelson <[email protected] > <javascript:_e(%7B%7D,'cvml','[email protected]');>> wrote: > > I've not seen a conflict with r10k, can you elaborate on that? Curious if > I'm hitting it and not knowing it! > > However, I have seen it cause great confusion with modules like > hunner/hiera or jlambert121/puppet that want to manage it, because there's > an ugly set of possible locations depending on oss vs enterprise and then > various versions. There have been a LOT of changes in the location and > adding another possible location to everyone's module matrix seems like it > may make the problem worse. So when it comes to timing, where it's at now > seems like a reasonable location until such time as per environment hiera > configs are available, IMHO. > > > Per environment configs have been around for a bit in 4. Some bug fixes > should land in next and then they should be totally usable I think > > > > On Monday, March 14, 2016, Eric Sorenson <[email protected] > <javascript:_e(%7B%7D,'cvml','[email protected]');>> wrote: > >> As a result of some introspection around r10k workflows, I came to agree >> with the statement in the title of HI-490: "the location of hiera.yaml in >> puppet-agent is a mistake." The root of the problem is that the current >> hiera.yaml is a mixture of global configuration (datadir location, merge >> behaviour, the backend configuration) and "code" like settings, namely the >> hierarchy itself. We chose to put it in $codedir but this has caused >> problems when people try to manage the file with puppet modules because it >> then conflicts with the control repo/r10k deploy workflow. (The PE-13367 >> ticket I mention in the description there is about the file sync service, >> but more generally r10k+webook management runs into the same problem.) >> >> There was some conversation that spun off into a google doc and seemed to >> coalesce around the following proposal: >> >> 1. puppet-agent packaging would be updated to install a default >> hiera.yaml at $confdir/hiera.yaml >> 2. both puppet and hiera would check in the old location, >> $codedir/hiera.yaml, and fall back to the new location >> $confdir/hiera.yaml >> 3. we would document the new location and encourage users to move their >> hiera.yaml >> >> This then raises the question of when we yank support for the old >> location, $codedir/hiera.yaml. Here the suggestion is: >> 1. for puppet-agent this happens in a major release of >> puppet/hiera/puppet-agent >> 2. for Puppet Enterprise additionally, we check if there is a >> $codedir/hiera.yaml and block the upgrade if it exists >> >> I wanted to raise visibility on this and see what the wider puppet-dev >> audience thought. Please feel free to chime in here or on the ticket and >> I'll summarize before taking any action. >> >> >> --eric0 >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Puppet Developers" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/puppet-dev/55526912-dd49-4fca-8ec6-2f59da7eca84%40googlegroups.com >> <https://groups.google.com/d/msgid/puppet-dev/55526912-dd49-4fca-8ec6-2f59da7eca84%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > > > -- > > Rob Nelson > [email protected] <javascript:_e(%7B%7D,'cvml','[email protected]');> > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] > <javascript:_e(%7B%7D,'cvml','puppet-dev%[email protected]');> > . > To view this discussion on the web visit > https://groups.google.com/d/msgid/puppet-dev/CAC76iT9vRzLe9NyXusmxcXXRE7ZVyE181rnrers8K9qjVoLCjQ%40mail.gmail.com > <https://groups.google.com/d/msgid/puppet-dev/CAC76iT9vRzLe9NyXusmxcXXRE7ZVyE181rnrers8K9qjVoLCjQ%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] > <javascript:_e(%7B%7D,'cvml','puppet-dev%[email protected]');> > . > To view this discussion on the web visit > https://groups.google.com/d/msgid/puppet-dev/5C2ED28A-B0F0-4D55-886E-BE22B128FDF5%40devco.net > <https://groups.google.com/d/msgid/puppet-dev/5C2ED28A-B0F0-4D55-886E-BE22B128FDF5%40devco.net?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- Rob Nelson [email protected] -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-dev/CAC76iT-xFrUV9tWCzHwuEtBvvcVqTY8pxN8fyEqu1ux0SJ3OZg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
