Jira (PUP-10627) write public information to puppet_dir/public
Title: Message Title R.I.Pienaar commented on PUP-10627 Re: write public information to puppet_dir/public The product is secure, the information in this file is not a security risk for the vast number of users. Those who function in repressive security environments can carry the cost associated with learning every minute detail and tweaking it all to their exact needs - as they already do for everything they use. Leaving sane defaults for the majority of users. Thats why this directory was made to specifically make it easy and obvious where and what puppet is providing as public - the problem is a) a file in there is not public b) it's not public because 1 user decided its a risk while 10s felt its good use to make that data public. When picking defaults its common for those to be picked in a way to serve the majority and then allow the minorities who do need things at a much more restrictive level to adjust things. Catering to new users with sane defaults the promote a safe use of the product is not their "ignorance", it's just how new users are and how people who do not make a product their entire life exist. It's a careful balance in product design. Another tenet of product design is that of consistency and obviousness and now we have a non public file in a public directory which is not consistent or obvious. And yes, every response by you so far has been that of a Jerk Scott Cyprus I'd appreciate if you can town it down a bit to a more civil level. It would also help if you didnt edit out entire comments so that when people respond to you others can see what the responses are about. Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97)
Jira (PUP-10627) write public information to puppet_dir/public
Title: Message Title R.I.Pienaar commented on PUP-10627 Re: write public information to puppet_dir/public Yeah, sorry I copied down from Trevor incorrectly, indeed reports should be not be accessible as they hold vast troves of information The whole reason this public directory was even made was due to the request - by many people over the years - to restore last run summary to world readable as it was in the distant past. It was great to see that was done as it solved a security issue for many enabling monitoring as non root. The ability to control file modes in config files is known by very few people ime based on chat history etc now we are back where we started - hard to use defaults for the majority average users. And more confusingly a public directory that holds a non public file Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.369665.1597829487000.33703.1621054500030%40Atlassian.JIRA.
Jira (PUP-10627) write public information to puppet_dir/public
Title: Message Title R.I.Pienaar commented on PUP-10627 Re: write public information to puppet_dir/public The file was not executable. It doesn’t indicate what the load of the system is and there are far simpler ways to determine what version of puppet is being run. It holds SIGNIFICANTLY less information than a report - as a response to “by default even reports should be accessible”. You are right which is why they are not. This summary file is not nearly as big a deal as suggested here. And those who are in highly controlled environments are used to tightening things down. This file has a very useful utility - and that is so that monitoring tools monitoring the health of puppet does not need to be run as root. Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.369665.1597829487000.33589.1621025700029%40Atlassian.JIRA.
Jira (PUP-10627) write public information to puppet_dir/public
Title: Message Title R.I.Pienaar commented on PUP-10627 Re: write public information to puppet_dir/public Came across this since the initial request that put the file here was PA-3253 and that created the "public" directory, now we have 0640 files in a public directory, which doesnt seem like the right thing to do and again makes it so that monitoring the puppet system can only be done as root? Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.369665.1597829487000.32411.1620901320028%40Atlassian.JIRA.
Jira (PDB-5002) Array match queries stopped working in version 7
Title: Message Title R.I.Pienaar commented on PDB-5002 Re: Array match queries stopped working in version 7 Rob Browning arg, my bad I should have noted that. But was latest on the date and I know I tried it a few times since all ones in 7 prior to latest had it, sorry about the bad bug report. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.384540.1611348921000.177490.1617119640034%40Atlassian.JIRA.
Jira (PDB-5002) Array match queries stopped working in version 7
Title: Message Title R.I.Pienaar commented on PDB-5002 Re: Array match queries stopped working in version 7 Yes, confirm, 7.2.0 fixes this. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.384540.1611348921000.170318.1616153940029%40Atlassian.JIRA.
Jira (PDB-5002) Array match queries stopped working in version 7
Title: Message Title
R.I.Pienaar commented on PDB-5002
Re: Array match queries stopped working in version 7
The mcollective.server.collectives fact has -["mcollective", "mt_collective"] - so the .match('\d') did a search over the array for the value on the right. I can't now find docs for this feature anymore, but its something for sure we supported when PQL shipped
Add Comment
This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
--
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.384540.1611348921000.122294.1611349500124%40Atlassian.JIRA.
Jira (PDB-5002) Array match queries stopped working in version 7
Title: Message Title
R.I.Pienaar created an issue
PuppetDB / PDB-5002
Array match queries stopped working in version 7
Issue Type:
New Feature
Assignee:
Unassigned
Created:
2021/01/22 12:55 PM
Priority:
Normal
Reporter:
R.I.Pienaar
In puppetdb-6.11.2-1.el7.noarch queries such as here will match within the fact facts.mcollective.server.collectives the value "mcollective": nodes[certname, deactivated] { (certname in inventory[certname] { facts.mcollective.server.collectives.match("\d+") = "mcollective" })} In puppetdb 7 this match is not supported anymore and now cause exceptions like: Caused by: org.postgresql.util.PSQLException: ERROR: syntax error at or near ")" Position: 1205 at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2532) at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2267) at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:312) at org.postgresql.jdbc.PgStatement.executeInternal(PgStatement.java:448) at org.postgresql.jdbc.PgStatement.execute(PgStatement.java:369) at org.postgresql.jdbc.PgPreparedStatement.executeWithFlags(PgPreparedStatement.java:153) at org.postgresql.jdbc.PgPreparedStatement.executeQuery(PgPreparedStatement.java:103) at com.zaxxer.hikari.pool.ProxyPreparedStatement.executeQuery(ProxyPreparedStatement.java:52) at com.zaxxer.hikari.pool.HikariProxyPreparedStatement.executeQuery(HikariProxyPreparedStatement.java) at puppetlabs.puppetdb.jdbc$call_with_array_converted_query_rows$fn__24748.invoke(jdbc.clj:320) at clojure.java.jdbc$db_transaction_STAR_.invokeStatic(jdbc.clj:814) at clojure.java.jdbc$db_transaction_STAR_.invoke(jdbc.clj:741) at puppetlabs.puppetdb.jdbc$call_with_array_converted_query_rows.invokeStatic(jdbc.clj:312) at puppetlabs.puppetdb.jdbc$call_with_array_converted_query_rows.invoke(jdbc.clj:295) at puppetlabs.puppetdb.jdbc$call_with_array_converted_query_rows.invokeStatic(jdbc.clj:308) at puppetlabs.puppetdb.jdbc$call_with_array_converted_query_rows.invoke(jdbc.clj:295) at puppetlabs.puppetdb.query_eng$body_stream$fn_31251$fn31254$fn_31255.invoke(query_eng.clj:339) at
Jira (FACT-1882) facter.rb:35: [BUG] Segmentation fault
Title: Message Title R.I.Pienaar commented on FACT-1882 Re: facter.rb:35: [BUG] Segmentation fault I had the same. Eventually ran a thorough memtest on the machine and one dimm was bad. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-1965) Clients are hung when server has intermittent service
Title: Message Title R.I.Pienaar commented on PUP-1965 Re: Clients are hung when server has intermittent service This can probably be closed after PUP-7517 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 (PDOC-243) should escape underscores outside of code blocks
Title: Message Title R.I.Pienaar updated an issue Puppet Strings / PDOC-243 should escape underscores outside of code blocks Change By: R.I.Pienaar Issue Type: New Feature Bug Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 (PDOC-243) should escape underscores outside of code blocks
Title: Message Title R.I.Pienaar created an issue Puppet Strings / PDOC-243 should escape underscores outside of code blocks Issue Type: New Feature Assignee: Unassigned Created: 2018/05/14 11:05 AM Priority: Normal Reporter: R.I.Pienaar When a class has a name like mcollective_agent_puppet, the resulting markdown from --format markdown looks like this: ## Plans * [`mcollective_agent_puppet::disable`](#mcollective_agent_puppetdisable): Disables Puppet on the provided nodes * [`mcollective_agent_puppet::disable_and_wait`](#mcollective_agent_puppetdisable_and_wait): Disables Puppet on the provided nodes and wait for them to idle By default 10 checks will be done 20 seconds apart, you can adjust these usi * [`mcollective_agent_puppet::enable`](#mcollective_agent_puppetenable): Enables Puppet on the provided nodes
Jira (PUP-8680) Puppet should supervise and kill its applying child if it gets stuck
Title: Message Title R.I.Pienaar commented on PUP-8680 Re: Puppet should supervise and kill its applying child if it gets stuck Ah that's handy, was not aware of this setting. Yeah setting it to something like a few hours by default in 6 would be great thanks! Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8680) Puppet should supervise and kill its applying child if it gets stuck
Title: Message Title R.I.Pienaar created an issue Puppet / PUP-8680 Puppet should supervise and kill its applying child if it gets stuck Issue Type: New Feature Affects Versions: PUP 5.4.0 Assignee: Unassigned Created: 2018/04/30 12:48 AM Priority: Normal Reporter: R.I.Pienaar The problem of stuck agents during periods of network instability comes up often see for example PUP-1570 which was marked wontfix. Network instability is a real problem, perhaps we cant fix the real problem but the symptoms and fall out can be better managed. There's no conceivable reason for a puppet catalog application to take hours or days: root 21490 2.6 1.2 281488 49480 ?Ssl Apr20 0:02 /opt/puppetlabs/puppet/bin/ruby /opt/puppetlabs/puppet/bin/puppet agent --no-daemonize root 3050 0.0 2.3 397320 90968 ?Sl Apr26 0:08 puppet agent: applying configuration Today is the 30th, surely the puppet agent that spawns the applier could detect this and kill the bad applier? Worse, restarting puppet agent service does not resolve this:
Jira (PUP-8566) "puppet config print" should only emit diagnostic info when run with verbose or higher
Title: Message Title R.I.Pienaar commented on PUP-8566 Re: "puppet config print" should only emit diagnostic info when run with verbose or higher Each command like master, agent, apply use different sections in the puppet.conf. Many other commands too and they can be quite confusing (which ones use user?) So never mind knowing this detail, puppet --configprint does the right thing and fetches it from the config file out of the appropriate section for that command. So the same CLI API to extracting the command appropriate information. I find this a lot nicer than puppet config print because you have to know a lot less to get at the information you want and have less scope for human error. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 (PDB-3852) PuppetDB query nodes based on fact broken
Title: Message Title R.I.Pienaar commented on PDB-3852 Re: PuppetDB query nodes based on fact broken Eric Sorenson rather than PDB-3856 being related I think this is the cause of the woes, no Choria user can upgrade PuppetDB at the moment. Would be fab to get this prioritised Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 (PDB-3856) PQL specifying both type and title for class makes pql not find existing class
Title: Message Title R.I.Pienaar commented on PDB-3856 Re: PQL specifying both type and title for class makes pql not find existing class David Hollinger your discovery is more likely failing due to https://tickets.puppetlabs.com/browse/PDB-3852 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 (PDB-3856) PQL specifying both type and title for class makes pql not find existing class
Title: Message Title
R.I.Pienaar commented on PDB-3856
Re: PQL specifying both type and title for class makes pql not find existing class
PuppetDB 5.1.1:
$ rpm -q puppetdb
puppetdb-5.1.1-1.el7.noarch
$ puppet query 'nodes[certname] { resources { type = "Class" and title = "Puppetdb" } }'
[
{
"certname": "puppet.choria.example.net"
}
]
Upgraded to 5.2.1 by setting puppetdb::globals::version to 5.2.1-1.el7:
$ rpm -q puppetdb
puppetdb-5.2.1-1.el7.noarch
Jira (PUP-8608) Plans should return undef without an explicit return
Title: Message Title R.I.Pienaar commented on PUP-8608 Re: Plans should return undef without an explicit return It’s incredible that over and over I have tried engage with you about boltlib. I have offered to work with you to design something generic that can be extended with what I wanted to achieve I did at first implement my results around your data types and I have explained AT LENGTH to you that using yours is the absolute best idea for everyone involved. I want to support 100% the same UX from a code basis as bolt. I have repeatedly asked for boltlib to be on the forge so others can use it Your response has in all cases been to refuse to talk about it. Say you have to make changes and when I offer to wait on releasing my code you refuse to say if 1.0.0 is weeks months or years away - even a ballpark that another engineer can place in the obvious context of it being thumb suck dates but something we can work together around. Instead your answer last time we spoke about this was that in fact boltlib is LESS likely to be released even due to changes you were instigating in it that day. All this made it abundantly clear you a: do not want to work towards a unified user experience with me b: will not be putting it on the forge When others on your team comment it’s very possible you personally reply and say it’s not. And here we are “I suggest you use our module, types and functions anyway.” Are you for real? In what world is that a possibility based on your own statements on the state of things? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the
Jira (PUP-8608) Plans should return undef without an explicit return
Title: Message Title R.I.Pienaar commented on PUP-8608 Re: Plans should return undef without an explicit return I'd suggest: Where you call "result = func.class.dispatcher.dispatchers[0].call_by_name_with_scope(scope, params, true)" next line, check the result, if its not one you like to expose to usersdont. This way nothing breaks and the system is not arbitrarily restricted for no reason limiting future work. I don't know if your boltlib will do what I need, it keeps changing weekly, I stopped looking as its a giant waste of time, I have result type of my own now which does what I need. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8608) Plans should return undef without an explicit return
Title: Message Title R.I.Pienaar commented on PUP-8608 Re: Plans should return undef without an explicit return The tasks I have are different from yours - and as discussed ad nauseum - I cannot use your types they are locked in bolt where no-one else can access them. So regardless of what, you are making it impossible to use. We do not need to revisit that again tbh. My return data is to_json compatible and for arbitrary stuff - say I want to make a plan that discovers some data, do a manipulation on it and return a hash - those are also serializable. As I have MANY TIMES said, I would love to use your module, why dont you make it so I can Alex Dreyer do we really need to keep going round in circles? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8608) Plans should return undef without an explicit return
Title: Message Title R.I.Pienaar commented on PUP-8608 Re: Plans should return undef without an explicit return I am ambivalent about the return behaviour, but I am very much against restricting the type of data plans can return unless thats something you can enable as a parameter to the function that invokes it. First I think there are many and good reasons for returning arbitrary stuff Second this would break choria plan integration since I cant use your return types Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-2997) Logdest cannot be set in the puppet.conf
Title: Message Title R.I.Pienaar commented on PUP-2997 Re: Logdest cannot be set in the puppet.conf And if someone goes to the trouble of setting up lets say splunk logging or whatever, and make Puppet log there, it's a safe assumption thats where they want to look for problems with puppet. Fall back default that is not where they look for critical errors is grossly irresponsible. I don't care either way, I am just pointing out why things are as they are for some context Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-2997) Logdest cannot be set in the puppet.conf
Title: Message Title R.I.Pienaar commented on PUP-2997 Re: Logdest cannot be set in the puppet.conf But it doesn't in so many cases puppet apply, puppet agent --test, etcetc. There's no right thing that handles all cases other than let people tell it what to do always. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-2997) Logdest cannot be set in the puppet.conf
Title: Message Title R.I.Pienaar commented on PUP-2997 Re: Logdest cannot be set in the puppet.conf The chicken and egg here is that, where do you log when you can't find the config file to tell you where to log? or cant read it? etc Logging it to a default fallback STDERR would be wrong - because then if someone monitors splunk they dont know about it. Specifying it on the CLI only ensures that in all cases the right thing can be done (or at least tried). Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8566) "puppet config print" needs --quiet option to disable new (default) verbosity
Title: Message Title R.I.Pienaar commented on PUP-8566 Re: "puppet config print" needs --quiet option to disable new (default) verbosity Master, apply etc all have —configprint and all does the right thing. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8566) "puppet config print" needs --quiet option to disable new (default) verbosity
Title: Message Title R.I.Pienaar commented on PUP-8566 Re: "puppet config print" needs --quiet option to disable new (default) verbosity James Ralston fwiw I tend to prefer puppet agent --configprint foo as then you know what your actual thing will use not whats in a particular section and luckily it seems that has not been affected by this Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8566) "puppet config print" needs --quiet option to disable new (default) verbosity
Title: Message Title R.I.Pienaar commented on PUP-8566 Re: "puppet config print" needs --quiet option to disable new (default) verbosity +1, this will break a lot of things Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 (PDOC-225) Data in Modules?
Title: Message Title R.I.Pienaar commented on PDOC-225 Re: Data in Modules? I have no ideas on how to do this with yard but details of the module supplied lookup options (merge strategies) would be amazing. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8491) Move essential functions from stdlib to puppet
Title: Message Title R.I.Pienaar commented on PUP-8491 Re: Move essential functions from stdlib to puppet I personally like them in the types but its also quite a change and a long tail before people stop needing stdlib stdlib is a tyre fire, moving these somewhere proper means a high % of people just wouldnt need to be exposed to stdlib mess, so the less code change required the most likely it is to go well Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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-8491) Move essential functions from stdlib to puppet
Title: Message Title R.I.Pienaar commented on PUP-8491 Re: Move essential functions from stdlib to puppet I'd love to see these move too they seem like the most basic things one would want in a modern language I think to_json and to_yaml would be great - perhaps with some changes so there's a optional flag to enable the pretty version of json. likewise loadjson and loadyaml (renamed for consistency I guess?) The things like downcase, upcase, capitalize, lstrip, rstrip, strip, chop, chomp and such basic string manipulation ones. Also min, max, flatten, sort and unique - these are unfortunately all v3 functions. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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-8493) The differences between the vendored semantic_puppet and the original make it impossible to swap in the original
Title: Message Title R.I.Pienaar commented on PUP-8493 Re: The differences between the vendored semantic_puppet and the original make it impossible to swap in the original /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/vendor/semantic_puppet is 1.0.1, I have no idea why the 0.1.2 one is there, its just a headache Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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-8493) The differences between the vendored semantic_puppet and the original make it impossible to swap in the original
Title: Message Title R.I.Pienaar commented on PUP-8493 Re: The differences between the vendored semantic_puppet and the original make it impossible to swap in the original Puppet Agent ships both, it would be better if there was just one /opt/puppetlabs/puppet/lib/ruby/gems/2.4.0/gems/semantic_puppet-0.1.2 /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/vendor/semantic_puppet Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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
Jira (PUP-8405) Knock-out-prefix fails with more than 3 merges
Title: Message Title R.I.Pienaar commented on PUP-8405 Re: Knock-out-prefix fails with more than 3 merges Personally to me that would be less surprising yes Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8405) Knock-out-prefix fails with more than 3 merges
Title: Message Title R.I.Pienaar commented on PUP-8405 Re: Knock-out-prefix fails with more than 3 merges Imo this makes this feature more or less useless. It works too differently and have very surprising restrictions orthogonal to the rest of hiera If it can’t be fixed it should be removed rather than just be super weird Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8070) cannot extract partial result from errors in plans
Title: Message Title
R.I.Pienaar updated an issue
Puppet / PUP-8070
cannot extract partial result from errors in plans
Change By:
R.I.Pienaar
Given a simple task:{code}#!/opt/puppetlabs/puppet/bin/rubyrequire 'json'puts Time.nowexit 1{code}And a plan:{code}plan mymod () { $r = run_task("mymod::sample", ["dev1"]) $r.error_nodes.each |$node, $error| {notice($node)notice($error)if $error =~ Error { notice($ node error .partial_result())} }}{code}I expect to get the data out of partial result, but:{code}bolt plan run mymod --modules .Warning: Support for ruby version 2.0.0 is deprecated and will be removed in a future release. See https://docs.puppet.com/puppet/latest/system_requirements.html#ruby for a list of supported ruby versions. (at /home/rip/.gem/ruby/gems/bolt-0.5.1/vendored/puppet/lib/puppet.rb:134:in `')Notice: Scope(/home/rip/temp/bolts/mymod/plans/init.pp, 4): dev1Notice: Scope(/home/rip/temp/bolts/mymod/plans/init.pp, 5): Error({'message' => 'The task failed with exit code 1', 'kind' => 'puppetlabs.tasks/task-error', 'issue_code' => 'TASK_ERROR', 'partial_result' => "2017-10-19 12:23:59 +0200\n", 'details' => {'exit_code' => 1}})Error: Evaluation Error: Unknown function: 'partial_result'. at /home/rip/temp/bolts/mymod/plans/init.pp:6:34 on node dev2.devco.netExiting because of an error in Puppet code{code}
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
Jira (PUP-8070) cannot extract partial result from errors in plans
Title: Message Title R.I.Pienaar created an issue Puppet / PUP-8070 cannot extract partial result from errors in plans Issue Type: Task Assignee: Unassigned Created: 2017/10/19 3:24 AM Priority: Normal Reporter: R.I.Pienaar Given a simple task: #!/opt/puppetlabs/puppet/bin/ruby require 'json' puts Time.now
Jira (PUP-8050) puppet agent -e environment
Title: Message Title R.I.Pienaar commented on PUP-8050 Re: puppet agent -e environment yes, puppet apply has -e, clash would be bad -E perhaps but seems like a pit of dsispair 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-8056) Error type docs wrong
Title: Message Title
R.I.Pienaar updated an issue
Puppet / PUP-8056
Error type docs wrong
Change By:
R.I.Pienaar
The plan error docs https://puppet.com/docs/bolt/0.5/writing_plans.html#returning-errors-in-plans suggest this would work:{code}plan mymodule::myplan { Error(message=> "Sorry, this plan does not work yet.",kind => 'mymodule/error',issue_code => 'NOT_IMPLEMENTED') }{code} This gives:{code}Error: Evaluation Error: Error while evaluating a Function Call, 'new_error' parameter 'message' expects a String value, got Struct at /home/rip/temp/bolts/mymod/plans/discover.pp:2:3 on node dev2.devco.net{code} Appears the code does not support that syntax it wants params of strings https://github.com/puppetlabs/puppet/blob/7fce55c2395df4c9547220169f82c97bb92b4574/lib/puppet/pops/types/p_error_type.rb#L59 Henrik points out and I seem to recall that there's something that should allow a hash to be passed in and mapped to param names - this might be the actual thing thats broken
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-8056) Error type docs wrong
Title: Message Title
R.I.Pienaar created an issue
Puppet / PUP-8056
Error type docs wrong
Issue Type:
Bug
Assignee:
Unassigned
Created:
2017/10/16 4:41 AM
Priority:
Normal
Reporter:
R.I.Pienaar
The plan error docs https://puppet.com/docs/bolt/0.5/writing_plans.html#returning-errors-in-plans suggest this would work:
plan mymodule::myplan {
Error(
message=> "Sorry, this plan does not work yet.",
kind => 'mymodule/error',
Jira (PDB-3699) allow PQL queries to be stored and executed by name
Title: Message Title
R.I.Pienaar created an issue
PuppetDB / PDB-3699
allow PQL queries to be stored and executed by name
Issue Type:
Bug
Assignee:
Unassigned
Created:
2017/10/10 1:48 PM
Priority:
Normal
Reporter:
R.I.Pienaar
PQL queries can be pretty awkward to type even though they are a LOT better than the old queries. A typo can wreak havok and they are hard to debug, it would be great if we could store queries by name which would facilitate reuse and sharing between team members - or just error reduction.
So if I could store
inventory[certname] { facts.osfamily = "RedHat" and
facts.datacentre = "PDX" and
resources { type = "Package" and
Jira (PUP-7822) Make the fact() function from stdlib part of core puppet so that the dot syntax is available in the DSL by default
Title: Message Title R.I.Pienaar commented on PUP-7822 Re: Make the fact() function from stdlib part of core puppet so that the dot syntax is available in the DSL by default I still think "dot syntax is nice" is a good answer and does not remove the utility for facts() but that fet() is absolutely needed. We now have dot syntax to access hashes on the cli, mcollective, puppetdb and probably elsewhere but not puppet. It's a commonality across fooling. It's nice. It's friendly and it creates cohesion. Whatever UX concerns exist for facts hash exist for normal hashes too it's a function of the puppet language not the facts hash. i think though fact() is not going to make it better. Already we have a crazy amount of ways to access facts - $foo $:foo $facts[foo] @foo etc we keep identifying bad ideas and adding new ideas and never removing old bad ideas and it is making it really really hard to explain to people what is going on and when to use what. Now there is an new confusing fact() thing that is close enough to the rest to make it worse. That's why $facts should be the way forward - hashes are well understood and behaves this way in many languages. It's just a hash and people need to learn how hashes work for their general life with puppet. Not only will they then understand facts but also all the other case they come across hashes in general. The name $facts then just communicate it clearly what is what and provide The Way to get at facts so there never exist any confusion what a variable is as there is just one obviously named way. That was my motivation for campaigning for years to get $facts in. Adding yet more ways to indirect people from what is going on and adding more confusingly named things to access facts will be a distraction. So along the lines of "it's a hash like any other" I suggest core gains just a get(). If another module wants say stdlib::facts() it's up to that module to create a tiny wrapper. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-7638) `puppet config print certname` only reads from [main], defaults to FQDN if no value is in [main]
Title: Message Title R.I.Pienaar commented on PUP-7638 Re: `puppet config print certname` only reads from [main], defaults to FQDN if no value is in [main] It pretty much does behave as you say. If you set in main it applies to all sections unless otherwise set specifically in a section. The non obvious thing is that config print is consulting only the main and user sections. Because it's a user utility it does that. It could perhaps print some hint but they would break a bunch of things as scripts will parse this output. You have to pick 1 section or run mode. Picking user seems correct but I can see how people might expect agent to be default - unless they happen to be on a master and then they expect master or something. Best to just specify what you want section/runmode wise 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-7638) `puppet config print certname` only reads from [main], defaults to FQDN if no value is in [main]
Title: Message Title R.I.Pienaar commented on PUP-7638 Re: `puppet config print certname` only reads from [main], defaults to FQDN if no value is in [main] Isn't this expected behaviour? Config print runs with the same config as apply would - so it does not consult agent. You can set which run mode you want on the CLI 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 R.I.Pienaar commented on PUP-6082 Re: ignore-disabled option for puppet agent runs by hand This option / approach is perfectly valid and supported All you are doing is telling your one specific puppet run to not look for the lock in the usual place and run anyway. You do it by changing the path to the lock. That's all, you don't change how the feature works or how other running instances interact with the existing lock and all the other locks like concurrent locks still work. So to me given that the basic feature exist and is (I guess!) tested then so is changing its config option and you are fine to use 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-6082) ignore-disabled option for puppet agent runs by hand
Title: Message Title R.I.Pienaar commented on PUP-6082 Re: ignore-disabled option for puppet agent runs by hand simple work around: puppet agent --test --agent_disabled_lockfile=/nonexisting 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-6165) it should not be possible to disable manifest ordering
Title: Message Title R.I.Pienaar commented on PUP-6165 Re: it should not be possible to disable manifest ordering Henrik Lindberg will that not recreate the issues with include/contain? class with resources_in_sequence includes other class they don't control, now the whole thing is unknown again? Generally I think MOAR is such a massive massive win on all levels for Puppet that introducing new hurdlers to it's use is a bad idea, you'd rather annotate which resources are parallel safe rather than which is not. In any way given that we (as a user) have never even considered parallel execution of resources that does seem to me the only viable option. 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-4716) Add option to pass transaction_uuid into agent
Title: Message Title R.I.Pienaar commented on PUP-4716 Re: Add option to pass transaction_uuid into agent Even if this goes into the last run summary and reports and do get stored - you still won't know what it was when triggering a run - you only find out at the end So async tools like mco will still not be able to know or find reports related to a run they triggered. Being able to pass a id explicitly means they can tell users to wait for a specific report Imagine the user request a splayed run via mco, is there another way to know in advance what this id will be when the run eventually starts? 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-2248) Provide a better way to connect and retrieve certificate without doing a client run.
Title: Message Title R.I.Pienaar commented on PUP-2248 Re: Provide a better way to connect and retrieve certificate without doing a client run. $ puppet certificate generate some.cert --ssldir /tmp/whatever --ca-location remote --ca_serve ca.example.net # someone signs it $ puppet certificate find some.cert --ssldir /tmp/whatever --ca-location remote --ca_server ca.example.net # get the ca too $ puppet certificate find ca --ssldir /tmp/whatever --ca-location remote --ca_server ca.example.net not sure this is 'better', but it worked last time I checked. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-7130) Fix problems with Puppet running on Ruby 2.4
Title: Message Title R.I.Pienaar commented on PUP-7130 Re: Fix problems with Puppet running on Ruby 2.4 File.expand_path I guess? 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-7213) support to_yaml in epp
Title: Message Title R.I.Pienaar commented on PUP-7213 Re: support to_yaml in epp Christoph Maser it really isn't as simple as just doing to_yaml since hashes are unordered you end up with files that changes every run. This is not really something Puppet should solve in core, especially as there are already modules on the forge that does this well. Not every problem is a core problem, not having this kind of thing in core has many advantages see for eg https://forge.puppet.com/fiddyspence/hash_file 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-7204) Add support for mapped paths in hiera.yaml version 5
Title: Message Title R.I.Pienaar commented on PUP-7204 Re: Add support for mapped paths in hiera.yaml version 5 Henrik Lindberg that looks pretty good to me 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-7202) excessive INFO logging when files arent found
Title: Message Title
R.I.Pienaar created an issue
Puppet / PUP-7202
excessive INFO logging when files arent found
Issue Type:
Bug
Affects Versions:
PUP 4.8.2
Assignee:
Unassigned
Created:
2017/02/10 11:09 AM
Priority:
Normal
Reporter:
R.I.Pienaar
When one use the common pattern like this:
file{"/foo":
source => ["puppet:///modules/x/foo.${fqdn}", "puppet:///modules/x/foo"]
}
Jira (HI-257) Dynamic hierarchy based on fact/variable
Title: Message Title R.I.Pienaar commented on HI-257 Re: Dynamic hierarchy based on fact/variable Henrik Lindberg this is the feature discussed at contributor summit, I suspect with the new code base we're in a better position to reconsider the feasibility of including this? Good history on the PR https://github.com/puppetlabs/hiera/pull/193 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-7050) Puppet apply is not reporting when fails to compile the catalog
Title: Message Title R.I.Pienaar commented on PUP-7050 Re: Puppet apply is not reporting when fails to compile the catalog Henrik Lindberg Puppet should report on failures so people can find out about it on their dashboards (foreman or otherwise), agent behaved like apply does in the distant past - did not report on serious errors - but that got added at some point, apply must be using a different code path that did not get this feature. So this should be to add that feature where it report on these kind of critical issues 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-7050) Puppet apply is not reporting when fails to compile the catalog
Title: Message Title R.I.Pienaar commented on PUP-7050 Re: Puppet apply is not reporting when fails to compile the catalog a good apply run reports: [rip@dev4]% puppet apply --report -e 'notice()' --debug|tail -5 <17:18:09 Debug: Finishing transaction 29848620 Debug: Received report to process from dev4.devco.net Debug: Evicting cache entry for environment 'production' Debug: Caching environment 'production' (ttl = 0 sec) Debug: Processing report from dev4.devco.net with processor Puppet::Reports::Store a bad one doesnt: % puppet apply --report -e 'foo foo foo' --debug 2>&1|tail -5 }.
Jira (PDB-3232) Open ports for PuppetDB based on assigned listen address
Title: Message Title R.I.Pienaar commented on PDB-3232 Re: Open ports for PuppetDB based on assigned listen address Valery Zabawski See the open*_ parameters to the class, this is already supported 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-6988) Variable Scope of defined Types in Puppet4 changed (undocumented)
Title: Message Title R.I.Pienaar commented on PUP-6988 Re: Variable Scope of defined Types in Puppet4 changed (undocumented) this is documented, its a change in templates not defined types https://docs.puppet.com/puppet/latest/lang_updating_manifests.html#dynamic-scoping-in-erb 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 (HI-546) Defining resource types by means of hiera
Title: Message Title
R.I.Pienaar commented on HI-546
Re: Defining resource types by means of hiera
I wouldn't suggest this should be a built in feature personally, just like hiera_include is not long for this world and lookup wont have a native version of it.
But you can easily build this yourself and stick it on the forge, untested code but you get the idea:
node default {
include classifier
}
class classifier (
String $resources_key = "resources",
String $classes_key = "classes"
) {
$resources = lookup({"name" => $resources_key, "default_value" => {}, "merge" => "deep"})
$classes = lookup({"name" => $classes_key, "default_value" => [], "merge" => "unique"})
Jira (PUP-6936) unable to read last_run_summary.yaml from user
Title: Message Title R.I.Pienaar commented on PUP-6936 Re: unable to read last_run_summary.yaml from user last_run_report should not be readable, last_run_summary should but as you say, on puppet-agent packages: drwxr-x--- 14 root root 4096 Oct 31 22:59 /opt/puppetlabs/puppet/cache is the real problem preventing 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-6899) puppet lookup ignores --hiera_config option
Title: Message Title
R.I.Pienaar commented on PUP-6899
Re: puppet lookup ignores --hiera_config option
Jesse Reynolds it looks under the environmentpath, so pass to your puppet lookup invocation the correct --environmentpath
% cd ~/temp/preso
% ls environments/production/hiera.yaml
environments/production/hiera.yaml
% puppet lookup --environmentpath /home/rip/temp/preso/environments users::local
{}
this is why you dont need to set hiera.yaml location, it's fixed relative to the env path
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-6903) user supplied identifier for a catalog application
Title: Message Title R.I.Pienaar commented on PUP-6903 Re: user supplied identifier for a catalog application Ah yes, PUP-4716 looks on the money, I had not seen that one - tough one to search for, we can merge these tickets or mark this one dupe. Essential for making reporting stuff resilient though for automation tools as it's inherently async. Thanks Josh Cooper 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-6903) user supplied identifier for a catalog application
Title: Message Title R.I.Pienaar created an issue Puppet / PUP-6903 user supplied identifier for a catalog application Issue Type: New Feature Assignee: Unassigned Created: 2016/11/08 8:48 AM Priority: Normal Reporter: R.I.Pienaar To facilitate correlating a specific puppet run with a specific report in a way thats more granular than the current time based approach it would be great to have an ID the user can supply, something like: puppet agent --one-time --runid b1318207843d44d5e94a6d709f61b972 This ID should be logged, stored in last_run_summary.yaml and included in the report both stored on disk and sent to the master. PuppetDB should let us find report events by this ID. This means when trying to correlate a run done via something like mcollective with the pool of reports in PuppetDB we can be 100% sure we're looking at the report for the run we started and not whatever is latest.
Jira (PUP-6862) Lookup doesn't interpolate values into hash keys
Title: Message Title R.I.Pienaar commented on PUP-6862 Re: Lookup doesn't interpolate values into hash keys Thanks Daniel Sung, this is much better done with a loop now over the data rather than hacks like what you describe 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-6862) Lookup doesn't interpolate values into hash keys
Title: Message Title R.I.Pienaar commented on PUP-6862 Re: Lookup doesn't interpolate values into hash keys As Henrik says yes. Though I am curious what problem this feature solves for 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-6834) lookup explain shows found data incorrectly
Title: Message Title R.I.Pienaar created an issue Puppet / PUP-6834 lookup explain shows found data incorrectly Issue Type: Bug Affects Versions: PUP 4.7.0 Assignee: Unassigned Created: 2016/10/19 3:25 PM Priority: Normal Reporter: R.I.Pienaar # data/nodes/dev3.devco.net.yaml users::local: rip: email: "arri.pien...@example.net"
Jira (PUP-6511) Add support for lookup.conf (version 5)
Title: Message Title R.I.Pienaar commented on PUP-6511 Re: Add support for lookup.conf (version 5) Agree with Henrik Lindberg the extension should ideally be less important - and optional for functions that interact with non file things 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-6717) (LoadError) no such file to load -- puppet_x/puppetlabs/std lib/deprecation_gen
Title: Message Title R.I.Pienaar commented on PUP-6717 Re: (LoadError) no such file to load -- puppet_x/puppetlabs/std lib/deprecation_gen you should not run master of stdlib, run a release. master has no guarantees about it working ever. 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-6712) Arrays in resource chaining
Title: Message Title R.I.Pienaar commented on PUP-6712 Re: Arrays in resource chaining Yes if we can make it so that syntax does not realise then that would be a massive win I was saying if without them would be a shortcut to the exact same behaviour it would be more confusing. 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-6712) Arrays in resource chaining
Title: Message Title R.I.Pienaar commented on PUP-6712 Re: Arrays in resource chaining I find the empty <||> is a nice reminder that this is in fact a find+realise and not a find. Of course the % of users who even know what virtual resources are must be single digit but might become even more surprising. 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-6683) Puppet agent 1.6.2 breaks defined()
Title: Message Title R.I.Pienaar commented on PUP-6683 Re: Puppet agent 1.6.2 breaks defined() yes exactly the same 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-6683) Puppet agent 1.6.2 breaks defined()
Title: Message Title R.I.Pienaar commented on PUP-6683 Re: Puppet agent 1.6.2 breaks defined() I had the same problem, restart fixed it. puppet-agent package should detect puppetserver and restart it or signal it somehow to kill its ruby workers and restart them I think 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-6682) $settings leaks symbols into manifests
Title: Message Title R.I.Pienaar commented on PUP-6682 Re: $settings leaks symbols into manifests Yes, I wouldn't suggest keeping it called $settings, some thing else that clearly indicate that it's the master settings etc, perhaps somewhere below trusted leaving the option open to deprecate $settings as horrible. 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-6682) $settings leaks symbols into manifests
Title: Message Title
R.I.Pienaar created an issue
Puppet / PUP-6682
$settings leaks symbols into manifests
Issue Type:
Bug
Affects Versions:
PUP 4.6.1
Assignee:
Unassigned
Created:
2016/09/06 6:49 AM
Priority:
Normal
Reporter:
R.I.Pienaar
% puppet apply -e '$be = $settings::storeconfigs_backend notice(inline_template("<%= @be.class %>"))'
Notice: Scope(Class[main]): Symbol
and therefore
Jira (PUP-5808) puppet via sudo from nfs home is not working
Title: Message Title R.I.Pienaar commented on PUP-5808 Re: puppet via sudo from nfs home is not working Adam Winberg ok, yeah that's what I wanted to determine, thanks. Well I've not seen anyone else complain about this but likewise I am not a Puppet dev so was just curious to see if we can get more info about the scenario maybe it rings bells to others 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-5808) puppet via sudo from nfs home is not working
Title: Message Title R.I.Pienaar commented on PUP-5808 Re: puppet via sudo from nfs home is not working /Stage[pre]/Core::Users::Update_root_pw/Exec[set_grub2_password]: Could not evaluate: Permission denied - /home/a001329 it's failing on Core::Users::Update_root_pw which is some kind of exec. Or are you saying every single resource type of every resource you have in your catalog fails in this manner? 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-5808) puppet via sudo from nfs home is not working
Title: Message Title R.I.Pienaar commented on PUP-5808 Re: puppet via sudo from nfs home is not working Adam Winberg always better to show the .pp code whenever puppet tells you its failing on some specific .pp code. 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-4643) Add continue/next/break for iteration control
Title: Message Title
R.I.Pienaar commented on PUP-4643
Re: Add continue/next/break for iteration control
a way to return early without failing out of a class would be good
class foo {
if $facts["condition"] {
# lots of code
}
}
this is a bit clunky to solve that problem when:
class foo {
unless $facts["condition"] { return() }
# lots of code now not in crazy indention and logic wrappers
Jira (HI-530) Hiera silently drops malformed hierarchy sources
Title: Message Title R.I.Pienaar commented on HI-530 Re: Hiera silently drops malformed hierarchy sources missing sources is normal yes - you might have 100 hosts and only 10 have certname specific files, this should not produce errors/warnings it will be very noisy. badly formed ones should produce errors, though the feedback cycle available to hiera is limited but yeah I think if there's actually a set documented known good thing it should error when a known not good thing is given to it. I suspect the rules arent defined though so ultimately this might just end up as design feedback for lookup rather than fixes to hiera given the place in hieras life cycle. 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 (PUP-6608) variable scoping change in Puppet 4.6.0
Title: Message Title R.I.Pienaar commented on PUP-6608 Re: variable scoping change in Puppet 4.6.0 This seems to be a critical bug to me, the priority doesn't seem right. We've had a few people on irc/slack bitten by this. Perhaps some mail must go out to announce list warning people off upgrading or something like that? 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 (PDB-2961) client tools man pages installed incorrectly
Title: Message Title R.I.Pienaar created an issue PuppetDB / PDB-2961 client tools man pages installed incorrectly Issue Type: Bug Assignee: Unassigned Created: 2016/08/13 4:48 AM Environment: puppet-client-tools-1.1.0-1.el7.x86_64 Priority: Normal Reporter: R.I.Pienaar Man pages are in /opt/puppetlabs/client-tools/share/man but should be in /opt/puppetlabs/client-tools/share/man/man8. Without it MANPATH set to /opt/puppetlabs/client-tools/share/man finds nothing, with a symlink to resolve this man pages are found additionally the install guide shows: $ export MANPATH=/opt/puppetlabs/client/tools/share/man:$MANPATH which is also wrong - client/tools instead of client-tools. CentOS 7 puppet-client-tools-1.1.0-1.el7.x86_64
Jira (PDB-2935) Duplicate declaration: Service[firewalld] is already declared
Title: Message Title R.I.Pienaar commented on PDB-2935 Re: Duplicate declaration: Service[firewalld] is already declared Tracy Phillips these are not really questions for the Jira but rather it's a issue in how the modules are used, so you'll be better off with one of the community resources like IRC, Slack or the mailing lists. Your errors do not indicate problems with the product 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 (PUP-6056) Specification of the new function API should include autoload information
Title: Message Title R.I.Pienaar commented on PUP-6056 Re: Specification of the new function API should include autoload information looks great Henrik Lindberg, left some small comments 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 (PUP-6576) What's the deal with data_binding_terminus? Deprecate?
Title: Message Title R.I.Pienaar commented on PUP-6576 Re: What's the deal with data_binding_terminus? Deprecate? https://github.com/domcleal/foreman_data_binding used by https://github.com/domcleal/foreman_param_lookup http://jerakia.io/tutorial/puppet/ 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 (PUP-3483) Systemd provider doesn't scan for changed units
Title: Message Title R.I.Pienaar commented on PUP-3483 Re: Systemd provider doesn't scan for changed units Tom Limoncelli It's an option and it seems sane to me, but I have no idea who will make such a module, an 'official' one would bubble to the top of ones being used I suppose 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 (PUP-3483) Systemd provider doesn't scan for changed units
Title: Message Title R.I.Pienaar commented on PUP-3483 Re: Systemd provider doesn't scan for changed units this same problem basically exist with all the various hassles around managing apt and apt-get update, and there the solution is that everyone uses puppetlabs-apt, I agree that to be a logical approach to handling this too 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 (PUP-6527) hiera_include() should be ignored when compiling an environment catalog
Title: Message Title R.I.Pienaar commented on PUP-6527 Re: hiera_include() should be ignored when compiling an environment catalog Nick Lewis and what is the intended behaviour of hiera there? There isn't really a node and facts right? I tried to get data lookups working in a sane way in the environment stuff and it didnt really work - though I have to recreate my tests to see how it failed as it's been a while. But I think having data access in those manifests is super important 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 (PUP-6537) unresolvable environment catalogs are compiled
Title: Message Title
R.I.Pienaar created an issue
Puppet / PUP-6537
unresolvable environment catalogs are compiled
Issue Type:
Bug
Affects Versions:
PUP 4.5.2
Assignee:
Unassigned
Components:
Puppet Server
Created:
2016/07/22 11:27 AM
Environment:
puppetserver 2.4.0
Priority:
Normal
Reporter:
R.I.Pienaar
The following site yields a unresolvable catalog:
site {
Jira (PUP-6527) hiera_include() should be ignored when compiling an environment catalog
Title: Message Title R.I.Pienaar commented on PUP-6527 Re: hiera_include() should be ignored when compiling an environment catalog hiera_include just shouldnt exist anymore, it was a thing while include didnt take arrays - years ago 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 (PUP-6400) lookup cli has no way to set arbitrary scope values
Title: Message Title
R.I.Pienaar commented on PUP-6400
Re: lookup cli has no way to set arbitrary scope values
Eric Sorenson no can't say I got this to work tbh
irb(main):002:0> JSON.parse(File.read("facts.json"))
=> {"trusted"=>{"certname"=>"foo.com"}}
:hierarchy:
- "%{trusted.certname}"
# puppet lookup --facts facts.json --debug some::data
Debug: hiera(): Looking up lookup_options in YAML backend
Debug: hiera(): Looking for data source dev3.devco.net
...
Jira (PUP-2018) `puppet certificate generate` Generates Two CSRs in One Run
Title: Message Title R.I.Pienaar commented on PUP-2018 Re: `puppet certificate generate` Generates Two CSRs in One Run side note, this breaks the mcollective install docs, be good to get this fixed 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 (PUP-6485) make it easier to require based on tag
Title: Message Title R.I.Pienaar commented on PUP-6485 Re: make it easier to require based on tag thanks Henrik Lindberg, as is often the case my manifests are much more complex than what I showed, so many loops of packages etc all in conditionals - but I think with your suggestion I can figure it out. Did anticipate your answer would be about the late processing of queries, but maybe this can be kept open for some other language addition if not done exactly with queries (though they would be nice) 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 (PUP-2018) `puppet certificate generate` Generates Two CSRs in One Run
Title: Message Title R.I.Pienaar commented on PUP-2018 Re: `puppet certificate generate` Generates Two CSRs in One Run Eric Sorenson repro steps..I dont think puppet cert can talk to remote CAs so not sure if it does the exact same thing Here I expect just one cert made but it makes the new one and then the fqdn one - which the master already have and so i get the wrong key error If I set --certname rip.mcollective (to match the requested cert) it attempts to make the same cert twice. % rm -rf .puppetlabs/etc/puppet/ssl % puppet --version 4.5.2 % ls /home/rip/.puppetlabs/etc/puppet/csr_attributes.yaml ls: cannot access /home/rip/.puppetlabs/etc/puppet/csr_attributes.yaml: No such file or directory % puppet certificate generate rip.mcollective --ca-location remote --ca_server dev5.devco.net --debug --verbose Info: Creating a new SSL key for rip.mcollective Info: csr_attributes file loading from /home/rip/.puppetlabs/etc/puppet/csr_attributes.yaml
Jira (PUP-6485) make it easier to require based on tag
Title: Message Title
R.I.Pienaar updated an issue
Puppet / PUP-6485
make it easier to require based on tag
Change By:
R.I.Pienaar
At present you can do like:{code} $packages.each |$ package | { "foo" package{$package : tag => bar , ensure => present } } file{"/foo": }Package<| tag == "bar" |> -> File["/foo"]{code}I am not aware though of a way to express this relationship inside the file resource, I tried a few things but this seems like it would be nice:{code}file{"/foo": require => Package <| tag == "bar" |>}{code}This strikes me as a more natural looking fit than above and involves less typing etc, of course you should ideally stick these packages in a class and require the class, but this is not really feasable when you are using defined types.This fails though with{code}Error: Could not parse for environment production: Invalid use of _expression_. A Virtual Query does not produce a value{code}
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 (PUP-6485) make it easier to require based on tag
Title: Message Title
R.I.Pienaar created an issue
Puppet / PUP-6485
make it easier to require based on tag
Issue Type:
Bug
Assignee:
Unassigned
Created:
2016/07/09 12:07 AM
Priority:
Normal
Reporter:
R.I.Pienaar
At present you can do like:
package{"foo": tag => bar}
file{"/foo": }
Package<| tag == "bar" |> -> File["/foo"]
I am not aware though of a way to
Jira (HI-341) Hiera should support native HOCON to match Puppet Server
Title: Message Title R.I.Pienaar commented on HI-341 Re: Hiera should support native HOCON to match Puppet Server Chris Price +1 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-341) Hiera should support native HOCON to match Puppet Server
Title: Message Title R.I.Pienaar commented on HI-341 Re: Hiera should support native HOCON to match Puppet Server As mentioned there are now many formats of file involved. And even multiple sub formats of file (eyaml being yaml with strict internal structure ideas for example) HOCON even looks a lot like JSON and if you don't know better or the file in question has no HOCON features in use like comments and such you would have to refer to docs or something So I like just calling things what they are as long as there are actual standards for what it is. When a config file is some made up thing well then a generic .conf communicates on its own that you're probably in for a bad time involving spelunking to figure out syntax rules. 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-341) Hiera should support native HOCON to match Puppet Server
Title: Message Title R.I.Pienaar commented on HI-341 Re: Hiera should support native HOCON to match Puppet Server +1 to what Henrik Lindberg said, data should not be `.conf` 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-46) Hiera should support alternate environments
Title: Message Title R.I.Pienaar commented on HI-46 Re: Hiera should support alternate environments Frank Ederveen there is now a environment level hiera with a per environment hiera.yaml with their own settings and so forth. This is unfortunately not older hiera but rather the new lookup system so you more or less only have 2 backends to choose from today, but that appears to be the way forward and whatever backends people like needs porting. 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 (PUP-6472) Puppet Lookup does only went through the module hieradata once
Title: Message Title R.I.Pienaar commented on PUP-6472 Re: Puppet Lookup does only went through the module hieradata once indeed, doubt this ever worked for module data too, you're right 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.
