Jira (PUP-7089) Allow "hiera3_backend" to be specified in a Hiera version 5 configuration.
Title: Message Title Craig Gomes updated an issue Puppet / PUP-7089 Allow "hiera3_backend" to be specified in a Hiera version 5 configuration. Change By: Craig Gomes Sprint: PDE 2017-01-11, PDE 2017-01-25, PDE 2017-02-08 , PDE 2017-02-22 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7089) Allow "hiera3_backend" to be specified in a Hiera version 5 configuration.
Title: Message Title Eric Thompson commented on PUP-7089 Re: Allow "hiera3_backend" to be specified in a Hiera version 5 configuration. that'd work except out planning meeting is at 1pm pacific. how about 12:30 pacific? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7089) Allow "hiera3_backend" to be specified in a Hiera version 5 configuration.
Title: Message Title Thomas Hallgren commented on PUP-7089 Re: Allow "hiera3_backend" to be specified in a Hiera version 5 configuration. Eric Thompson, I suggest that we set up a BJ meeting with some screen sharing. I'm out of ideas on why this works for me and not for you. I can do it today at 1pm if that's ok? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7089) Allow "hiera3_backend" to be specified in a Hiera version 5 configuration.
Title: Message Title Eric Thompson commented on PUP-7089 Re: Allow "hiera3_backend" to be specified in a Hiera version 5 configuration. i've tried both my own path, and adding it to servers ruby-load-path and installing via gem. i also tried just putting it here: [root@njthb2xx78szqu1 ~]# cat /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/hiera/backend/custom_backend.rb class Hiera module Backend class Custom_backend def lookup(key, scope, order_override, resolution_type, context) return 'custom value' unless (key == 'lookup_options') end end end end
Jira (PUP-7089) Allow "hiera3_backend" to be specified in a Hiera version 5 configuration.
Title: Message Title Thomas Hallgren commented on PUP-7089 Re: Allow "hiera3_backend" to be specified in a Hiera version 5 configuration. That's surprising. The last approach really should work. For puppetserver, that is. It will not work for `puppet master` or `puppet lookup` unless you add it to the LOAD_PATH manually before issuing the command. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7089) Allow "hiera3_backend" to be specified in a Hiera version 5 configuration.
Title: Message Title Eric Thompson commented on PUP-7089 Re: Allow "hiera3_backend" to be specified in a Hiera version 5 configuration. Thomas Hallgren this doesn't work for me either. i'll try building a gem from my custom backend and install it. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7089) Allow "hiera3_backend" to be specified in a Hiera version 5 configuration.
Title: Message Title Eric Thompson commented on PUP-7089 Re: Allow "hiera3_backend" to be specified in a Hiera version 5 configuration. excellent Thomas Hallgren, thank you! i had tried some other hackish attempts. like putting a ruby file that solely adds my custom backend to $LOAD_PATH in the existing LOAD_PATH, but it didn't work. possibly because it was being overwritten, like you said. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7089) Allow "hiera3_backend" to be specified in a Hiera version 5 configuration.
Title: Message Title
Thomas Hallgren commented on PUP-7089
Re: Allow "hiera3_backend" to be specified in a Hiera version 5 configuration.
I see that using the servers libdir won't work. It is created dynamically on each run and whatever is placed there is overwritten.
Instead, you will need to create your own addition to the puppetserver's $LOAD_PATH. This can be done by adding a path to the ruby_load_path in /etc/puppetlabs/puppetserver/conf.d/puppetserver.conf. I did this on the nt0ovjx4zrt6lsz.delivery.puppetlabs.net server mentioned above:
cat /etc/puppetlabs/puppetserver/conf.d/puppetserver.conf
{
"jruby-puppet": {
"ruby-load-path": [
"/opt/puppetlabs/puppet/lib/ruby/vendor_ruby"
"/opt/puppetlabs/puppet/lib/ruby/testing"
],
...
and then I added the custom_backend.rb file under /opt/puppetlabs/puppet/lib/ruby/testing/hiera/backend and it works!
Jira (PUP-7089) Allow "hiera3_backend" to be specified in a Hiera version 5 configuration.
Title: Message Title Eric Thompson commented on PUP-7089 Re: Allow "hiera3_backend" to be specified in a Hiera version 5 configuration. here are the VMs if you want to reproduce/debug: 2017-02-06 22:49:59 [+] vmpooler el-7-x86_64 nt0ovjx4zrt6lsz.delivery.puppetlabs.net (redhat7-64-1) 2017-02-06 22:49:59 [+] vmpooler ubuntu-14.04-amd64 hi1tjodyg2vc3j7.delivery.puppetlabs.net (ubuntu1404-64-1) el-7 is the master Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7089) Allow "hiera3_backend" to be specified in a Hiera version 5 configuration.
Title: Message Title Eric Thompson commented on PUP-7089 Re: Allow "hiera3_backend" to be specified in a Hiera version 5 configuration. it doesn't seem to work, Thomas Hallgren [root@sm1pie8jo3xj19d lib]# cat /opt/puppetlabs/server/data/puppetserver/lib/hiera/backend/custom_backend.rb class Hiera module Backend class Custom_backend def lookup(key, scope, order_override, resolution_type, context) return 'custom value' unless (key == 'lookup_options') end end end end
Jira (PUP-7089) Allow "hiera3_backend" to be specified in a Hiera version 5 configuration.
Title: Message Title Thomas Hallgren commented on PUP-7089 Re: Allow "hiera3_backend" to be specified in a Hiera version 5 configuration. It should work to put the backend in /hiera/backend. It will be found since is included in the the LOAD_PATH. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7089) Allow "hiera3_backend" to be specified in a Hiera version 5 configuration.
Title: Message Title Eric Thompson commented on PUP-7089 Re: Allow "hiera3_backend" to be specified in a Hiera version 5 configuration. hmmm, putting this in the master's libdir doesn't work. i believe because it needs to be in hiera/backend/ subdir which is not in the LOAD_PATH Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7089) Allow "hiera3_backend" to be specified in a Hiera version 5 configuration.
Title: Message Title Eric Thompson commented on PUP-7089 Re: Allow "hiera3_backend" to be specified in a Hiera version 5 configuration. for this test, then i'll just stick the custom backend in the global libdir. thanks for the thorough debugging and analysis Thomas Hallgren! Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7089) Allow "hiera3_backend" to be specified in a Hiera version 5 configuration.
Title: Message Title Thomas Hallgren commented on PUP-7089 Re: Allow "hiera3_backend" to be specified in a Hiera version 5 configuration. I added DOC-3092 to track the documentation error. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7089) Allow "hiera3_backend" to be specified in a Hiera version 5 configuration.
Title: Message Title Henrik Lindberg commented on PUP-7089 Re: Allow "hiera3_backend" to be specified in a Hiera version 5 configuration. This is the pain that people seem to solve by plugin syncing to master (if not installing gems in server as well) - it is a mess, and have been so for a long time. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7089) Allow "hiera3_backend" to be specified in a Hiera version 5 configuration.
Title: Message Title
Thomas Hallgren commented on PUP-7089
Re: Allow "hiera3_backend" to be specified in a Hiera version 5 configuration.
After a longer session of trial and error, the cause of this finally dawned on me. Short story, the test is wrong, this isn't supposed to work.
Longer story: Code that resides under a modules lib directory is not automatically executed as part of a catalog compilation. It is however, made available to an agent as a "plugin". So, the agent uses a File resource to install the files. This can be seen in the agent log output:
Info: Retrieving plugin
Notice: /File[/opt/puppetlabs/puppet/cache/lib/hiera]/ensure: created
Notice: /File[/opt/puppetlabs/puppet/cache/lib/hiera/backend]/ensure: created
Notice: /File[/opt/puppetlabs/puppet/cache/lib/hiera/backend/custom_backend.rb]/ensure: defined content as '{md5}b8dd18e4a61e059706fd4c02c5f8'
This plugin is only installed on the agent side though. The files are not available to the master unless the master and the agent runs on the same server and they have the same setting for $libdir (or $vardir as it's derived from that). If they do, the agent install of the plugins actually makes the files available to both the master and the agent. This is because $libdir is part of the Ruby $LOAD_PATH.
The tests that Eric Thompson was running had a master $vardir configured for a puppetserver. That setting differs from the default and therefore, the tests failed, even if the agent and the master was running on the same machine. If the setting is commented out in puppet.conf, the test actually succeeds.
So why does this work when running a lookup from the command line? Well, unless the command is "master" or "agent", puppet actually adds whatever is listed under 'lib' in the configured environment to the ruby $LOAD_PATH. I assume that it does this so that the "plugins" listed there are made available to commands like "apply".
This means that this statement from the documentation:
Jira (PUP-7089) Allow "hiera3_backend" to be specified in a Hiera version 5 configuration.
Title: Message Title Eric Thompson commented on PUP-7089 Re: Allow "hiera3_backend" to be specified in a Hiera version 5 configuration. yes. sorry i should have thought about that last night! el7 master here: eqayuwweiqgs5yx.delivery.puppetlabs.net running master puppet agent 6f6ae4a2b84ee9e50a1103852f66a5e2fce326a0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7089) Allow "hiera3_backend" to be specified in a Hiera version 5 configuration.
Title: Message Title Thomas Hallgren commented on PUP-7089 Re: Allow "hiera3_backend" to be specified in a Hiera version 5 configuration. Eric Thompson, I've tested this backwards and forwards but I'm not able to reproduce the problem. Would it be possible for you to make a server accessible to me where this problem is apparent? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7089) Allow "hiera3_backend" to be specified in a Hiera version 5 configuration.
Title: Message Title Eric Thompson commented on PUP-7089 Re: Allow "hiera3_backend" to be specified in a Hiera version 5 configuration. same issue: Debug: importing '/etc/puppetlabs/code/environments/hiera3_custom_backend_tq3nh067/modules/some_mod/manifests/init.pp' in environment hiera3_custom_backend_tq3nh067 Debug: Automatically imported some_mod from some_mod into hiera3_custom_backend_tq3nh067 Debug: ModuleLoader: module 'some_mod' has unknown dependencies - it will have all other modules visible Debug: Lookup of 'anykey' Searching for "lookup_options" Global Data Provider (hiera configuration version 5) Using configuration "/etc/puppetlabs/puppet/hiera.yaml" Hierarchy entry "Test" Unable to load backend 'custom': cannot load such file -- hiera/backend/custom_backend
Jira (PUP-7089) Allow "hiera3_backend" to be specified in a Hiera version 5 configuration.
Title: Message Title Thomas Hallgren commented on PUP-7089 Re: Allow "hiera3_backend" to be specified in a Hiera version 5 configuration. I assume that you're using a puppetserver? If so, is there any difference if you just run a plain puppet master instead (that's what I did)? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7089) Allow "hiera3_backend" to be specified in a Hiera version 5 configuration.
Title: Message Title Eric Thompson commented on PUP-7089 Re: Allow "hiera3_backend" to be specified in a Hiera version 5 configuration. supposedly loaded, but: 2017-01-31 17:42:11,435 DEBUG [qtp666317422-24] [puppetserver] Puppet importing '/etc/puppetlabs/code/environments/hiera3_custom_backend_tq3nh067/modules/some_mod/manifests/init.pp' in environment hiera3_custom_backend_tq3nh067 2017-01-31 17:42:11,444 DEBUG [qtp666317422-24] [puppetserver] Puppet Automatically imported some_mod from some_mod into hiera3_custom_backend_tq3nh067 2017-01-31 17:42:11,447 DEBUG [qtp666317422-24] [puppetserver] Puppet ModuleLoader: module 'some_mod' has unknown dependencies - it will have all other modules visible 2017-01-31 17:42:11,544 DEBUG [qtp666317422-24] [puppetserver] Puppet Lookup of 'anykey' Searching for "lookup_options" Global Data Provider (hiera configuration version 5) Using configuration "/etc/puppetlabs/puppet/hiera.yaml" Hierarchy entry "Test" Unable to load backend 'custom': no such file to load --
Jira (PUP-7089) Allow "hiera3_backend" to be specified in a Hiera version 5 configuration.
Title: Message Title Thomas Hallgren commented on PUP-7089 Re: Allow "hiera3_backend" to be specified in a Hiera version 5 configuration. Eric Thompson, never mind. I misread that quote. Puppet really do load things beneath lib. I tried your example. It works OK for me, both using the command line and with puppet agent -t. Can you run the master with --debug enabled? It would be helpful because it will output a full lookup explanation in the master log. When I do that, I get this output: Debug: Lookup of 'anykey' Searching for "lookup_options" Global Data Provider (hiera configuration version 5) Using configuration "/home/thhal/puppet_fixture/etc/puppet/hiera.yaml" Hierarchy entry "Custom" Found key: "lookup_options" value: nil Searching for "anykey" Global Data Provider (hiera configuration version 5) Using configuration "/home/thhal/puppet_fixture/etc/puppet/hiera.yaml"
Jira (PUP-7089) Allow "hiera3_backend" to be specified in a Hiera version 5 configuration.
Title: Message Title Thomas Hallgren commented on PUP-7089 Re: Allow "hiera3_backend" to be specified in a Hiera version 5 configuration. To answer my own question. I found this in the docs (last link in Eric's comment above): When using Hiera with Puppet, you can load backends from the lib directory of a Puppet module; however, these backends won’t be loaded when you run Hiera from the command line unless you specify that directory in your RUBYLIB environment variable. @erict, is the RUBYLIB environment variable set on the master when you execute the agent run? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7089) Allow "hiera3_backend" to be specified in a Hiera version 5 configuration.
Title: Message Title Thomas Hallgren commented on PUP-7089 Re: Allow "hiera3_backend" to be specified in a Hiera version 5 configuration. @erict, any Hiera backend can provide lookup_options. It gives the user the ability to declare lookup_options close to data and works with Puppet lookup using a classic Hiera 3 too. Regarding the failure, is everything present under modules/some_mod/lib added to the Ruby load path? I wouldn't expect that to happen. Do we have some example of a backend for classic Hiera that is made accessible this way? My expectation would be that such backends must to be installed as gems to be available to Hiera but I might be wrong. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7089) Allow "hiera3_backend" to be specified in a Hiera version 5 configuration.
Title: Message Title Eric Thompson commented on PUP-7089 Re: Allow "hiera3_backend" to be specified in a Hiera version 5 configuration. also, it was a bit surprising to me, as the user that i had to screen on lookup_options in my custom_backend. this makes perfect sense based on my own knowledge of data in modules and hiera5. my custom_backend is exceedingly dumb as well, compared to one that would be used in production, checking for actual keys and returning nil for non-existent keys. Lindsey Smith, others: thoughts? documentation additions? existing docs: https://docs.puppet.com/puppet/latest/lookup_quick.html#setting-lookupoptions-in-data https://docs.puppet.com/hiera/3.2/custom_backends.html Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7089) Allow "hiera3_backend" to be specified in a Hiera version 5 configuration.
Title: Message Title Eric Thompson commented on PUP-7089 Re: Allow "hiera3_backend" to be specified in a Hiera version 5 configuration. now i can get this to work with puppet lookup but not in an agent run: [root@uqxwu2rlejmodoo hiera3_custom_backend_7pe0glhq]# find . . ./manifests ./manifests/site.pp ./modules ./modules/some_mod ./modules/some_mod/lib ./modules/some_mod/lib/hiera ./modules/some_mod/lib/hiera/backend ./modules/some_mod/lib/hiera/backend/custom_backend.rb
Jira (PUP-7089) Allow "hiera3_backend" to be specified in a Hiera version 5 configuration.
Title: Message Title Craig Gomes updated an issue Puppet / PUP-7089 Allow "hiera3_backend" to be specified in a Hiera version 5 configuration. Change By: Craig Gomes Sprint: PDE 2017-01-11, PDE 2017-01-25 , PDE 2017-02-08 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7089) Allow "hiera3_backend" to be specified in a Hiera version 5 configuration.
Title: Message Title Thomas Hallgren assigned an issue to qa Puppet / PUP-7089 Allow "hiera3_backend" to be specified in a Hiera version 5 configuration. Change By: Thomas Hallgren Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7089) Allow "hiera3_backend" to be specified in a Hiera version 5 configuration.
Title: Message Title Henrik Lindberg commented on PUP-7089 Re: Allow "hiera3_backend" to be specified in a Hiera version 5 configuration. second PR merged to master at: 76ea81d Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7089) Allow "hiera3_backend" to be specified in a Hiera version 5 configuration.
Title: Message Title Thomas Hallgren assigned an issue to Thomas Hallgren Puppet / PUP-7089 Allow "hiera3_backend" to be specified in a Hiera version 5 configuration. Change By: Thomas Hallgren Assignee: qa Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7089) Allow "hiera3_backend" to be specified in a Hiera version 5 configuration.
Title: Message Title Thomas Hallgren assigned an issue to Unassigned Puppet / PUP-7089 Allow "hiera3_backend" to be specified in a Hiera version 5 configuration. Change By: Thomas Hallgren Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7089) Allow "hiera3_backend" to be specified in a Hiera version 5 configuration.
Title: Message Title Thomas Hallgren commented on PUP-7089 Re: Allow "hiera3_backend" to be specified in a Hiera version 5 configuration. Henrik Lindberg, Eric Thompson, I created an additional PR that addresses the above problem and moved this back to "ready for merge". Please review. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7089) Allow "hiera3_backend" to be specified in a Hiera version 5 configuration.
Title: Message Title Thomas Hallgren commented on PUP-7089 Re: Allow "hiera3_backend" to be specified in a Hiera version 5 configuration. Thanks @erict, I'll look into that. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7089) Allow "hiera3_backend" to be specified in a Hiera version 5 configuration.
Title: Message Title Thomas Hallgren assigned an issue to qa Puppet / PUP-7089 Allow "hiera3_backend" to be specified in a Hiera version 5 configuration. Change By: Thomas Hallgren Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7089) Allow "hiera3_backend" to be specified in a Hiera version 5 configuration.
Title: Message Title Eric Thompson commented on PUP-7089 Re: Allow "hiera3_backend" to be specified in a Hiera version 5 configuration. Thomas Hallgren i haven't dug in too far yet, here is the server foreground that seems applicable: /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/parser/compiler.rb:395:in `evaluate_classes' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/pops/loader/../../../puppet/functions/include.rb:16:in `include' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/pops/functions/dispatch.rb:47:in `invoke' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/pops/functions/dispatcher.rb:36:in `dispatch' org/jruby/RubyKernel.java:1242:in `catch' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/pops/functions/dispatcher.rb:35:in `dispatch' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/pops/functions/function.rb:46:in `call' org/jruby/RubyKernel.java:1242:in `catch' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/pops/functions/function.rb:45:in `call'
Jira (PUP-7089) Allow "hiera3_backend" to be specified in a Hiera version 5 configuration.
Title: Message Title Henrik Lindberg commented on PUP-7089 Re: Allow "hiera3_backend" to be specified in a Hiera version 5 configuration. Eric Thompson You can only use hiera3_backend in the global layer's version 3 and 5 hiera.yaml - the v3 hiera backends are typically not designed to handle different sets of data (we don't know how they are implemented) and they are therefore not safe to use per environment (or in a module). You should not get the error you are showing though... Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7089) Allow "hiera3_backend" to be specified in a Hiera version 5 configuration.
Title: Message Title Thomas Hallgren commented on PUP-7089 Re: Allow "hiera3_backend" to be specified in a Hiera version 5 configuration. @erict, the stacktrace is from the agent and doesn't help much. Is it possible to provide a trace from the master? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7089) Allow "hiera3_backend" to be specified in a Hiera version 5 configuration.
Title: Message Title
Eric Thompson commented on PUP-7089
Re: Allow "hiera3_backend" to be specified in a Hiera version 5 configuration.
if i move the config to $confdir in above, i get an {{undefined method `empty? ' for nil
[root@bax9lksuojkgdtc hiera3_custom_backend_msb3g5p9]# puppet agent -t --server $(hostname -f) --environment hiera3_custom_backend_msb3g5p9 --trace
Info: Using configured environment 'hiera3_custom_backend_msb3g5p9'
Info: Retrieving pluginfacts
Info: Retrieving plugin
Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Evaluation Error: Error while evaluating a Function Call, undefined method `empty?' for nil:NilClass at /etc/puppetlabs/code/environments/hiera3_custom_backend_msb3g5p9/modules/some_mod/manifests/init.pp:2:19 on node bax9lksuojkgdtc.delivery.puppetlabs.net
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/rest.rb:269:in `is_http_200?'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/rest.rb:167:in `find'
Jira (PUP-7089) Allow "hiera3_backend" to be specified in a Hiera version 5 configuration.
Title: Message Title Eric Thompson commented on PUP-7089 Re: Allow "hiera3_backend" to be specified in a Hiera version 5 configuration. this is only allowed at global level? is that intended? bax9lksuojkgdtc.delivery.puppetlabs.net (bax9lksuojkgdtc.delivery.puppetlabs.net) 22:41:44$ puppet lookup --environment hiera3_custom_backend_0v8kha9i --explain anykey Searching for "lookup_options" Global Data Provider (hiera configuration version 5) No such key: "lookup_options" Environment Data Provider (hiera configuration version 5) Using configuration "/etc/puppetlabs/code/environments/hiera3_custom_backend_0v8kha9i/hiera.yaml" /etc/puppetlabs/code/environments/hiera3_custom_backend_0v8kha9i/hiera.yaml: 'hiera3_backend' is only allowed in the global layer
Jira (PUP-7089) Allow "hiera3_backend" to be specified in a Hiera version 5 configuration.
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-7089 Allow "hiera3_backend" to be specified in a Hiera version 5 configuration. Change By: Henrik Lindberg Release Notes Summary: Part of the new hiera 5 feature. Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7089) Allow "hiera3_backend" to be specified in a Hiera version 5 configuration.
Title: Message Title Kenn Hussey commented on PUP-7089 Re: Allow "hiera3_backend" to be specified in a Hiera version 5 configuration. Henrik Lindberg please add release notes for this issue. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7089) Allow "hiera3_backend" to be specified in a Hiera version 5 configuration.
Title: Message Title Craig Gomes updated an issue Puppet / PUP-7089 Allow "hiera3_backend" to be specified in a Hiera version 5 configuration. Change By: Craig Gomes Sprint: PDE 2017-01-11 , PDE 2017-01-25 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7089) Allow "hiera3_backend" to be specified in a Hiera version 5 configuration.
Title: Message Title Eric Thompson updated an issue Puppet / PUP-7089 Allow "hiera3_backend" to be specified in a Hiera version 5 configuration. Change By: Eric Thompson QA Risk Assessment Reason: partially covered by unit tests, needs acceptance. high risk for migrations Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7089) Allow "hiera3_backend" to be specified in a Hiera version 5 configuration.
Title: Message Title Eric Thompson updated an issue Puppet / PUP-7089 Allow "hiera3_backend" to be specified in a Hiera version 5 configuration. Change By: Eric Thompson QA Risk Assessment: Needs Assessment Automate Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7089) Allow "hiera3_backend" to be specified in a Hiera version 5 configuration.
Title: Message Title Henrik Lindberg commented on PUP-7089 Re: Allow "hiera3_backend" to be specified in a Hiera version 5 configuration. merged to master at: e4866ac Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7089) Allow "hiera3_backend" to be specified in a Hiera version 5 configuration.
Title: Message Title Henrik Lindberg commented on PUP-7089 Re: Allow "hiera3_backend" to be specified in a Hiera version 5 configuration. since it is delegating to a hiera3 backend, should the path be with or without prefix in the hiera5 hiera.yaml for such an entry? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7089) Allow "hiera3_backend" to be specified in a Hiera version 5 configuration.
Title: Message Title Thomas Hallgren assigned an issue to Unassigned Puppet / PUP-7089 Allow "hiera3_backend" to be specified in a Hiera version 5 configuration. Change By: Thomas Hallgren Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7089) Allow "hiera3_backend" to be specified in a Hiera version 5 configuration.
Title: Message Title Thomas Hallgren assigned an issue to Thomas Hallgren Puppet / PUP-7089 Allow "hiera3_backend" to be specified in a Hiera version 5 configuration. Change By: Thomas Hallgren Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7089) Allow "hiera3_backend" to be specified in a Hiera version 5 configuration.
Title: Message Title
Thomas Hallgren updated an issue
Puppet / PUP-7089
Allow "hiera3_backend" to be specified in a Hiera version 5 configuration.
Change By:
Thomas Hallgren
It is currently only possible to migrate to using a global Hiera version 5 configuration when the current Hiera version 3 configuration declares backends that are supported in Hiera version 5 (currently yaml, json, and hocon). There is no way to add a custom hiera3 hiera version 3 backend.In order to always enable a migration of the configuration (and hence , get rid of deprecation warnings), it should be possible for a Hiera 5 config configuration to also declare a reference to a custom Hiera 3 backend. A new entry {{hiera3_backend}} should be added that is mutually exclusive to the currently known function types {{data_hash}}, {{lookup_key}}, and {{data_dig}}.The ability to declare a hiera 3 backend in a named Hiera version 5 {{hierarchy}} entry will also make it possible to identify and override entries declared in a {{bottom_hierarchy}} (a planned future addition) . It also and removes the need to introduce the {{bottom_hierarchy}} in a Hiera version 3 configuration .
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at
Jira (PUP-7089) Allow "hiera3_backend" to be specified in a Hiera version 5 configuration.
Title: Message Title Thomas Hallgren created an issue Puppet / PUP-7089 Allow "hiera3_backend" to be specified in a Hiera version 5 configuration. Issue Type: Improvement Assignee: Unassigned Created: 2017/01/11 7:45 AM Fix Versions: PUP 4.9.0 Priority: Normal Reporter: Thomas Hallgren It is currently only possible to migrate to using a global Hiera 5 configuration when the current Hiera 3 declares backends that are supported in Hiera 5 (currently yaml, json, and hocon). There is no way to add a custom hiera3 backend. In order to always enable a migration of the configuration (and hence, get rid of deprecation warnings), it should be possible for a Hiera 5 config to also declare a reference to a custom Hiera 3 backend. A new entry hiera3_backend should be added that is mutually exclusive to the currently known function types data_hash, lookup_key, and data_dig. The ability to declare a hiera 3 backend in a named Hiera 5 hierarchy entry will also make it possible to identify and override entries declared in a bottom_hierarchy (a planned future addition). It also removes the need to introduce the bottom_hierarchy in a Hiera 3 configuration.
