Jira (PUP-9473) Systemd daemon-reload doesn't get triggered for removal of unit file
Title: Message Title
Andreas Papst commented on PUP-9473
Re: Systemd daemon-reload doesn't get triggered for removal of unit file
Hello, To find changed unit-files use:
$ systemctl --all status *.service 2>&1 | grep --color 'changed on disk. Run' Warning: The unit file, source configuration file or drop-ins of example.service changed on disk. Run 'systemctl daemon-reload' to reload units.
For a distinct service, it would be
$ systemctl --all status example.service 2>&1 | grep --color 'changed on disk. Run' && echo changed
BTW: `systemctl daemon-reload´ mends all deltas. Therefore I suggest, you use a trigger to a global Exec['/bin/systemctl daemon-reload'] for all changes and a `ensure => Exec['/bin/systemctl daemon-reload']´ within the Service statement. The statement {{exec['/bin/systemctl daemon-reload'] {refreshonly => true,} }} should be part of modules/systemd/manifest/init.pp. Example:
file { '/usr/lib/systemd/system/foo.service': ensure => file, owner => 'root', group => 'root', mode => '0644', source => "puppet:///modules/${module_name}/foo.service", notify => Exec['/bin/systemctl daemon-reload'], } ~> service
Unknown macro: {'foo'}
Just have a look at https://github.com/justin8/justin8-systemd Regards Andreas
Add Comment
This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d)
Jira (PDB-5364) Enabling log-queries in 7.7.1 causes JSON serialization failures
Title: Message Title
Andreas Papst commented on PDB-5364
Re: Enabling log-queries in 7.7.1 causes JSON serialization failures
Hello, same issue here with puppetdb 7.8.0-1buster : $ curl -X GET http://localhost:8080/pdb/query/v4 --data-urlencode 'query= facts[certname, name]{ name in ["fact1", "fact2"] }' Cannot JSON encode object of class: class org.postgresql.jdbc.PgArray: {"fact1","fact2"} I've got a hint: https://stackoverflow.com/questions/29819540/org-postgresql-util-pgobject-cannot-be-cast-to-org-postgresql-util-pgobject This can only really happen when you have multiple versions of the Postgresql JDBC driver on your classpath. Maybe one in your webapp and another one in the servlet container itself. Make sure to only have one such jar file. Maybe a fix should be easy now. Regards Andreas
Add Comment
This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d)
--
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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.423245.163664995.1620.1642509240043%40Atlassian.JIRA.
Jira (PUP-8058) filebucket has a lack of authorization on puppet server side (extern)
Title: Message Title Andreas Papst created an issue Puppet / PUP-8058 filebucket has a lack of authorization on puppet server side (extern) Issue Type: Bug Affects Versions: PUP 4.10.8 Assignee: Unassigned Components: filebucket Created: 2017/10/16 8:23 AM Environment: all Priority: Minor Reporter: Andreas Papst Hello, I'd asked you for providing `puppet filebucket list` of external data (on puppet-server) too and digged into this issue to provide some ideas or maybe a draft. But for very good reasons it is not allowed to query an external filebucket list at the moment and more basic work is needed to accomplish this task. The crucial point is no limitation exists on accessing filebucket data. It has only "security through obscurity" and if a root user guesses the MD5 hash reading all files from all servers using filebucket is possible. An iteration attack is simple thus credentials and other confidential information could
Jira (PUP-6082) ignore-disabled option for puppet agent runs by hand
Title: Message Title Andreas Papst commented on PUP-6082 Re: ignore-disabled option for puppet agent runs by hand (Your guess is right And this feature is deployed on my servers already. I'm fine with this, no change is required. Thank you! 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-6082) ignore-disabled option for puppet agent runs by hand
Title: Message Title Andreas Papst commented on PUP-6082 Re: ignore-disabled option for puppet agent runs by hand Thank you for this hint! I don't care for names of options. The command puppet agent -t --noop --agent_disabled_lockfile=/nonexisting works perfectly for my purpose. I was wandering and then have proofed, it keeps support of locking execution of a second puppet instance. Then my only wish is this option should have some kind of "being supported" state, i.e. units-tests and/or regression-tests should be available. 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-6082) ignore-disabled option for puppet agent runs by hand
Title: Message Title Andreas Papst commented on PUP-6082 Re: ignore-disabled option for puppet agent runs by hand Hello, would it also represent a wrong technical direction if a --force option would only work in combination with --noop option? Background: IMHO this tool should enable admins to do a centralized ops. For instance that is to have consolidated information of pending changes due to disabled puppet runs. In my case this is stored then in puppetdb and summaries are displayed out of puppetdb. Therefor it would be phenomenal, not to have fault-prone workarounds running in cronjobs to collect these data and just do a `puppet agent -t --noop --force´ for fetching infos regardless if puppet is disabled. Cheers Andreas 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-7199) Update to puppet-agent 1.9.0-1jessie breaks puppet master
Title: Message Title Andreas Papst commented on PUP-7199 Re: Update to puppet-agent 1.9.0-1jessie breaks puppet master Hey, as you can see from node.yaml: hiera_hash is used implicitly. And deeper merge is defined in hiera.conf: :merge_behavior: deeper :deep_merge_options: :knock_out_prefix: '--' :sort_merge_arrays: true :merge_hash_arrays: true I guess too that hiera is the prime suspect. Maybe deeper merge is broken even when there is no second hash to merge. Cheers Andreas Add Comment This message was sent by Atlassian JIRA
Jira (PUP-7199) Update to puppet-agent 1.9.0-1jessie breaks puppet master
Title: Message Title Andreas Papst commented on PUP-7199 Re: Update to puppet-agent 1.9.0-1jessie breaks puppet master No, this all work fine with 1.8.3 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-7199) Update to puppet-agent 1.9.0-1jessie breaks puppet master
Title: Message Title Andreas Papst commented on PUP-7199 Re: Update to puppet-agent 1.9.0-1jessie breaks puppet master Sorry, that I have been to harsh, servers are fixed now and regular operation is verified. Now I have time to elaborate. - These is the message (retrieved from puppedb): some_module::Chroot[name_a] is already declared in file modules/some_module/manifests/conf.pp:103 cannot redeclare at modules/some_module/manifests/conf.pp:103 at modules/some_module/manifests/conf.pp:103:7 at modules/some_module/manifests/virtual.pp:5 on node some_node Which is: modules/some_module/manifests/conf.pp:103:7
Jira (PUP-7199) Update to puppet-agent 1.9.0-1jessie breaks puppet master
Title: Message Title Andreas Papst commented on PUP-7199 Re: Update to puppet-agent 1.9.0-1jessie breaks puppet master OK, I didn't expected that a Debian package isn't configured to apt-get install does all required steps. So I terminated puppetserver process and started it again. (but when stepping back, puppetserver is restarted by apt-get, why this?) But I cannot tell if this is the solution (I'm pretty sure it is not) due to a new syntax error regarding function create_resources which has been used to ensure deep in a packet that a resource is defined. It changed behavior and now it gives an error: Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Evaluation Error: Error while evaluating a Resource Statement, Evaluation Error: Error while evaluating a Resource Statement, Duplicate declaration: and more serious, it breaks now some more important services. Thus I cannot check anything any further but have to switch back immediately! To me puppet agent 1.9 is completely broken and I will not use it any more. I strongly recommend to tag puppet-agent to version 1.8.3-1 on puppet master. BTW: Consulting the doku: https://docs.puppet.com/hiera/3.2/configuring.html :deep_merge_options
Jira (PUP-7199) Update to puppet-agent 1.9.0-1jessie breaks puppet master
Title: Message Title Andreas Papst commented on PUP-7199 Re: Update to puppet-agent 1.9.0-1jessie breaks puppet master Hello, thank you for this update, but installing puppet-agent=1.9.1-1jessie doesn't solve my problem, puppet master is still broken to me. Also is still an issue! Thus I switch back to 1.8.3-1 again. Cheers Andreas 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 (FACT-1406) Big values become negativ
Title: Message Title Andreas Papst created an issue Facter / FACT-1406 Big values become negativ Issue Type: Bug Affects Versions: FACT 3.1.6 Assignee: Unassigned Created: 2016/04/29 6:02 AM Environment: Debian 8.4 ii puppet-agent1.4.2-1jessie i386 The Puppet Agent package contains all of the elements needed to run puppet, including ruby, facter, hiera and mcollective. ii puppetlabs-release-pc1 1.0.0-2jessie all Release packages for the Puppet Labs PC1 repository ii postgresql-9.5 9.5.2-1.pgdg80+1amd64object-relational SQL database, version 9.5 server
Jira (FACT-1403) timestamp as a default fact
Title: Message Title
Andreas Papst created an issue
Facter / FACT-1403
timestamp as a default fact
Issue Type:
New Feature
Assignee:
Unassigned
Created:
2016/04/28 4:59 AM
Priority:
Trivial
Reporter:
Andreas Papst
Hello,
to me it is important to know, when data (facts) were generated. In particular it is crucial if these facts are stored for example in puppetDB.
Thus I wrote a tiny extension I'd like to share with you. Maybe it is useful for somebody else too.
Facter.add(:facts_timestamp) do
setcode do
report = {}
dt = Time.now
Jira (HI-507) Puppet lookup (doing a Hiera lookup) in yaml files do not find keys with a dot
Title: Message Title Andreas Papst commented on HI-507 Re: Puppet lookup (doing a Hiera lookup) in yaml files do not find keys with a dot Hello, Are you telling me, that this works as being designed? At least it is very confusing when somebody like me did an upgrad from puppet3 to puppet4. With puppet3 this YAML-key with a dot inside was valid and could be used with any tool reporting the respective value. After upgrading to puppet4 it took me half a day to find out this dot is not valid any more even using hiera command itself. And I'm aware of friends running into the same problem. May I suggest, that you update your upgrade-documentation including this issue. Thank you Andreas Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 (HI-507) Puppet lookup (doing a Hiera lookup) in yaml files do not find keys with a dot
Title: Message Title Andreas Papst commented on HI-507 Re: Puppet lookup (doing a Hiera lookup) in yaml files do not find keys with a dot Yes, my example above is failing even with Hiera 3.1.1 For my output of your HI-504 checks look at https://tickets.puppetlabs.com/browse/HI-504 Thank you Andreas Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 (HI-504) Allow interpolated keys to be quoted and contain dot characters
Title: Message Title Andreas Papst commented on HI-504 Re: Allow interpolated keys to be quoted and contain dot characters /etc/puppetlabs/code/test.yaml : --- :backends: - yaml :yaml: :datadir: /etc/puppetlabs/code/hieradata :hierarchy: - "test" /etc/puppetlabs/code/hieradata/test.yaml : --- foo: bar foo_dot_bar:
Jira (HI-506) When working in userspace `puppet lookup´ does not respect the `--node´ option nor use userspace hiera.yaml
Title: Message Title Andreas Papst commented on HI-506 Re: When working in userspace `puppet lookup´ does not respect the `--node´ option nor use userspace hiera.yaml Hello, I'm sorry, but I'm totally confused about your version system. I'm using the latest Debian package provided be your Debian repository, just upgraded today: puppet-agent 1.4.1-1jessie $ puppet -V 4.4.1 which I suppose is the latest version. I must use a --facts option pointing to ./test.yaml --- fqdn : mynode.univie.ac.at environment : my_env in puppet lookup --node mynode.univie.ac.at foo::bar_1 --environment my_env --facts ./test.yaml --explain --debug
Jira (HI-507) Puppet lookup (doing a Hiera lookup) in yaml files do not find keys with a dot
Title: Message Title Andreas Papst commented on HI-507 Re: Puppet lookup (doing a Hiera lookup) in yaml files do not find keys with a dot Sorry, but I cannot confirm, that with Hiera 3.1.1 this issue is resolved. In contrary, with puppetserver 2.3.1-1puppetlabs1 puppet-agent 1.4.1-1jessie $ /opt/puppetlabs/bin/hiera -V 3.1.1 neither hiera command itself nor puppet lookup show up true for foo.bar I still get nil! Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (PDB-1304) Trouble starting PuppetDB service
Title: Message Title Andreas Papst commented on PDB-1304 Re: Trouble starting PuppetDB service With installing Debian package puppetdb 2.3.3-1puppetlabs1 this problem is not experienced any more. thanks Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1304) KahaDB: Could not retrieve facts
Title: Message Title Andreas Papst commented on PDB-1304 Re: KahaDB: Could not retrieve facts Hi Kenneth, there is no more log content to obtain. As we further investigate this problem you are right. The start up of the init.d script failed in some parts. Finally we managed to start up puppetdb by executing each single step of this script on a shell prompt. That worked and we haven't try to restart it again. And due to the fact we have increased the memory size in the virtual server instance puppetdb isn't dying any more. Recently a new Debian package for puppetdb is made available which we will try to install next days and look for some improvements. Regards Andreas Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1304) Trouble starting PuppetDB service
Title: Message Title Andreas Papst commented on PDB-1304 Re: Trouble starting PuppetDB service As I mentioned, we have increased memory on the server. Maybe the problem was related to a shortage of memory. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1303) puppetdb with postgres backend shows up password in process list to all users
Title: Message Title Andreas Papst created an issue PuppetDB / PDB-1303 puppetdb with postgres backend shows up password in process list to all users Issue Type: Improvement Assignee: Unassigned Created: 2015/03/19 10:23 AM Environment: puppetdb 2.2.2-1puppetlabs1 Debian GNU/Linux 7.8 (wheezy) Priority: Minor Reporter: Andreas Papst According to your configuration document https://docs.puppetlabs.com/puppetdb/2.2/postgres_ssl.html I setup /etc/default/puppetdb with password to connect to postgresDB Modify this if you'd like to change the memory allocation, enable JMX, etc JAVA_ARGS=-Xmx192m -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/var/log/puppetdb/puppetdb-oom.hprof -Djavax.net.ssl.trustStore=/etc/puppetdb/ssl/truststore.jks -Djavax.net.ssl.trustStorePassword=PASSWORD Starting puppetdb and entering the command `ps -ef` the password is visible than to all users, what is imho very ugly. Please provide a different approach to hand over trustStore password to java.
Jira (PDB-1304) KahaDB: Could not retrieve facts
Title: Message Title
Andreas Papst created an issue
PuppetDB / PDB-1304
KahaDB: Could not retrieve facts
Issue Type:
Improvement
Assignee:
Unassigned
Created:
2015/03/19 10:39 AM
Environment:
Debian GNU/Linux 7.8 (wheezy) puppet 3.7.4-1puppetlabs1 puppet-dashboard 1.2.23-1puppetlabs1 puppet-lint 0.1.13-2 puppetdb 2.2.2-1puppetlabs1 puppetdb-terminus 2.2.2-1puppetlabs1 puppetlabs-release 1.0-11 puppetmaster 3.7.4-1puppetlabs1 puppetmaster-common 3.7.4-1puppetlabs1 puppetmaster-passenger 3.7.3-1puppetlabs1 java-common 0.47 openjdk-7-jre-headless:amd64 7u65-2.5.1-5~deb7u1
Priority:
Normal
Reporter:
Andreas Papst
Each puppet agent cannot retrieve information according it's name from puppetdb.
Removing directory or deleting some file inside /var/lib/puppetdb/mq/localhost/KahaDB does not help.
/var/log/puppetdb/puppetdb.log: 2015-03-19 18:30:33,140 WARN [o.e.j.h.HttpParser] badMessage: java.lang.IllegalStateException: too much data after closed for HttpChannelOverHttp@139ca786 {r=1,a=IDLE,uri=-}
puppet agent error: Warning: Unable to fetch my node definition, but the agent run will continue: Warning: Error 400 on SERVER: Could not retrieve facts for agent.test.com: Failed to find facts from PuppetDB at puppetmaster.test.com:8081: [404 Not Found] htmlheadmeta http-equiv=Content-Type content=text/html;charset=ISO-8859-1/titleError 404 /title/headbodyh2HTTP ERROR: 404/h2pProblem accessing /v3/nodes/agent.test.com/facts. Reason:pre Not Found/pre/phr /ismallPowered by Jetty:///small/i/body/html
Even
Jira (HI-296) hiera merging: remove values when :merge_behavior is set to deeper
Title: Message Title Andreas Papst updated an issue Hiera / HI-296 hiera merging: remove values when :merge_behavior is set to deeper Change By: Andreas Papst Attachment: backend.rb.patch Attachment: backend.rb.example Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-296) hiera merging: remove values when :merge_behavior is set to deeper
Title: Message Title
Andreas Papst updated an issue
Hiera / HI-296
hiera merging: remove values when :merge_behavior is set to deeper
Change By:
Andreas Papst
Aim:WithdeepermergingofHieradefinedhashesitshouldbepossibletoremovepreviouslydefinedhash-values.Thistinypatchfulfillsthisimposition:Patch/usr/lib/ruby/vendor_ruby/hiera/backend.rbwith--- {noformat} ---orig/backend.rb+++improvement/backend.rb@@-173,6+173,16@@#:deeper=UseHash.deep_merge!#defmerge_answer(left,right)+ifConfig[:merge_exclude_string]+caseConfig[:merge_behavior]+when:deeper,'deeper'+left.deep_merge!(right,{:knockout_prefix=Config[:merge_exclude_string]})+when:deep,'deep'+left.deep_merge(right,{:knockout_prefix=Config[:merge_exclude_string]})+else#Nativeandundefined+left.merge(right)+end+elsecaseConfig[:merge_behavior]when:deeper,'deeper'left.deep_merge!(right)@@-181,6+191,7@@else#Nativeandundefinedleft.merge(right)end+endend#Callsouttoallconfiguredbackendsintheorderthey {noformat} ---(Pleasebegenerous,thesearemyfirstlinesrubycode)Thusanewhiera.yamlkeyisintroduced::merge_exclude_stringIt'svalueisusedasforoption:knockout_prefixintheunderlyingrubymoduledeep_merge(https://github.com/danielsdeleo/deep_merge)toremovearrayentriesandhashvalues.Usageof:merge_exclude_stringinthehashtobemerged:./Ahashvalueprefixedwith:merge_exclude_stringwillbecomeanemptystring./The:merge_exclude_stringusedaloneresultsinanemptystringashashvalue,allvaluesdefinedpreviouslywillbecomedeleted../Anarraymemberprefixedwith:merge_exclude_stringwillberemovedfromthearray../The:merge_exclude_stringusedaloneasanarraymemberwillgiveanemptyarray../Anyvalueorarray-memberprefixedwith:merge_exclude_stringwillnotbeincludedevenifitwasnotdefinedpreviously../Mergingdifferenttypesofvalueswillcausethedeletionofthepreviouslydefinedvalueasitwasbefore.Example:/tmp/hieradata/hiera.yaml:-- {noformat} ---:backends:-yaml:yaml::datadir:/tmp/hieradata:hierarchy:-replace-common:merge_behavior:deeper:merge_exclude_string:'--' {noformat} --/tmp/hieradata/common.yaml:-- {noformat} ---K:KA:KA1:valA1KA2:valA2KA3:valA3KA4:valA4KB:KB1:valB1KB2:to_be_removed_valB2KB3:valB3KB4:valB4KC:KC1:valC1KC2:valC2KC3:valC3KC4:valC4KD:KD1:-array_member_D1-array_member_D2-array_member_D3-array_member_D4KE:KE1:-array_member_E1-to_be_removed_array_member_E2-array_member_E3-array_member_E4KF:KF1:-all_to_be_removed_array_member_F1-all_to_be_removed_array_member_F2-all_to_be_removed_array_member_F3-all_to_be_removed_array_member_F4KG:KG1:-all_to_be_removed_array_member_G1-all_to_be_removed_array_member_G2-all_to_be_removed_array_member_G3-all_to_be_removed_array_member_G4KH:KH1:-all_to_be_removed_array_member_H1-all_to_be_removed_array_member_H2-all_to_be_removed_array_member_H3-all_to_be_removed_array_member_H4 {noformat} --/tmp/hieradata/replace.yaml:-- {noformat}
Jira (HI-296) hiera merging: remove values when :merge_behavior is set to deeper
Title: Message Title Andreas Papst commented on HI-296 Re: hiera merging: remove values when :merge_behavior is set to deeper Hi Rob, I hope this meets your requirements now. best wishes Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-296) hiera merging: remove values when :merge_behavior is set to deeper
Title: Message Title
Andreas Papst created an issue
Hiera / HI-296
hiera merging: remove values when :merge_behavior is set to deeper
Issue Type:
Improvement
Affects Versions:
HI 1.3.4
Assignee:
Unassigned
Created:
08/Oct/14 5:58 AM
Environment:
could solve Feature-Request #18793 ruby 1.9
Fix Versions:
HI 1.3.4
Priority:
Normal
Reporter:
Andreas Papst
Aim: With deeper merging of Hiera defined hashes it should be possible to remove previously defined hash-values.
This tiny patch fulfills this imposition: Patch /usr/lib/ruby/vendor_ruby/hiera/backend.rb with --- — orig/backend.rb +++ improvement/backend.rb @@ -173,6 +173,16 @@
:deeper = Use Hash.deep_merge! # def merge_answer(left,right) + if Config[:merge_exclude_string] + case Config[:merge_behavior] + when :deeper,'deeper' + left.deep_merge!(right, {:knockout_prefix =
Jira (PUP-2735) unexpected different behaviour of 0 (integer vs. string) as a value in Hiera and as a default value for class parameters
Title: Message Title Andreas Papst commented on an issue Re: unexpected different behaviour of 0 (integer vs. string) as a value in Hiera and as a default value for class parameters Hi Henrik, adding the option you mentioned (puppet agent -t --parser future) doesn't change anything. But this seems not to be a big surprise, due to template command is extrapolated at the puppet master but not at the agent side. Recall: Default for parameter $foobar = 0 node.yaml: — classes: test = /tmp/test: foobar foobar == '0' node.yaml: — classes: test test::foobar: = /tmp/test: foobar foobar == '0' node.yaml: — classes: test test::foobar: 0 = /tmp/test: foobar foobar == 0 node.yaml: — classes: test test::foobar: '0' = /tmp/test: foobar foobar == '0' node.yaml: — classes: test test::foobar: true = /tmp/test: foobar foobar == true node.yaml: — classes: test test::foobar: false = /tmp/test: empty node.yaml: — classes: test test::foobar: 1 = /tmp/test: foobar Hope this is something useful to you Andreas puppet -V 3.6.2 cat /etc/debian_version 7.3 dpkg -l | grep puppet ii facter 2.0.2-1puppetlabs1 amd64 Ruby module for collecting simple facts about a host operating system ii hiera 1.3.4-1puppetlabs1 all A simple pluggable Hierarchical Database. ii puppet 3.6.2-1puppetlabs1 all Centralized configuration management - agent startup and compatibility scripts ii
Jira (PUP-2735) unexpected different behaviour of 0 (integer vs. string) as a value in Hiera and as a default value for class parameters
Title: Message Title Andreas Papst created an issue Puppet / PUP-2735 unexpected different behaviour of 0 (integer vs. string) as a value in Hiera and as a default value for class parameters Issue Type: Bug Affects Versions: 3.6.1 Assignee: Unassigned Created: 06/Jun/14 4:34 AM Environment: $ facter | grep oper operatingsystem = Debian operatingsystemmajrelease = 7 operatingsystemrelease = 7.5 $ puppet -V 3.6.1 $ dpkg -l | grep puppet ii facter 2.0.1-1puppetlabs1 amd64 Ruby module for collecting simple facts about a host operating system ii hiera 1.3.3-1puppetlabs1 all A simple pluggable Hierarchical Database. ii puppet 3.6.1-1puppetlabs1 all Centralized configuration management - agent startup and compatibility scripts ii puppet-common 3.6.1-1puppetlabs1 all Centralized configuration management ii puppet-lint 0.1.13-2 all check puppet manifests for style guide conformity ii puppetdb 2.0.0-1puppetlabs1 all PuppetDB Centralized Storage. ii puppetdb-terminus 2.0.0-1puppetlabs1 all Connect Puppet to PuppetDB by setting up a terminus for PuppetDB. ii puppetlabs-release 1.0-7 all Package to install Puppet Labs gpg key and apt repo ii puppetmaster 3.6.1-1puppetlabs1 all Centralized configuration management - master startup and compatibility scripts ii puppetmaster-common 3.6.1-1puppetlabs1 all Puppet master common scripts ii puppetmaster-passenger 3.6.1-1puppetlabs1 all Centralised configuration management - master setup to run under mod passenger ii ruby-rgen 0.6.5-1puppetlabs1 all A framework supporting Model Driven Software Development (MDSD) ii vim-puppet 3.6.1-1puppetlabs1 all syntax highlighting for puppet manifests in vim Priority: Normal Reporter: Andreas Papst
