Jira (PUP-6125) verbose agent runs result data being sent console and syslog
Title: Message Title Matthew Gyurgyik commented on PUP-6125 Re: verbose agent runs result data being sent console and syslog Henrik Lindberg Did you see my closed pull request PR#4837? I think this is similar to what your are suggesting. This PR would cause --verbose and --debug to only log to the console unless --logdest is set. In PR#4982 PR#4982, the idea is that --verbose and --debug
Jira (PUP-6328) Parsing of strings changes with puppet 4.5.0
Title: Message Title
Henrik Lindberg commented on PUP-6328
Re: Parsing of strings changes with puppet 4.5.0
In 4.5.0 all references to types are validated and you get an error if it does not exists. Since there is no type named Ubuntu you get an error. An upper case bare word is a type (has been since 3.x with future parser, and in all 4.x versions). Before 4.5.0 they were not validated - and thus, the type Ubuntu presented itself as the string 'Ubuntu' when given to something like notify which transform everything to string before logging.
Since you are probably not dealing with a type Ubuntu you should quote the text.
puppet apply -e 'notice("Ubuntu")'
If you have a type named Ubuntu it is missing from the module path.
Compare the error you are getting to something like
puppet apply -e 'notice(Integger)'
which is also a reference to a type that does not exists. Before Puppet 4.5.0, such errors (typos) went unnoticed in many places.
Hope that explains what is going on, and why there is a difference. This is by design. (Always quote what you expect to be a string).
Add Comment
Jira (PUP-6338) Allow arrow syntax on the contain keyword
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6338 Allow arrow syntax on the contain keyword If doing this also consider moving the function to 4.x API. Change By: Henrik Lindberg Story Points: 1 Sprint: Language Triage Scrum Team: Language 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
Jira (PUP-6338) Allow arrow syntax on the contain keyword
Title: Message Title
Henrik Lindberg commented on PUP-6338
Re: Allow arrow syntax on the contain keyword
Jesús M. Navarro Which version of Puppet are you using? (3.x, if so, with future parser on, or 4.x)?
Do you get the error:
Illegal relationship operand, can not form a relationship with an Undef Value. A Catalog type is required.
The wanted behaviour could be achieved by lettering the contain function return an Array[Class[name]] (i.e. the input given to the function resolved to types). Thus, in the example, the returned value would be [Class\['someclass'], and the arrow operator would then work. This can only be changed for 4.x.
Alternatively, it may be possible to do this with a call to with, like this:
with('someclass') |$name| { contain($name); Class[$name] } -> Notify[x]
Or:
with(Class['someclass']) |$classes| { contain($classes); classes } -> Notify[x]
With this example, the input to with can be a single reference, or an array of references. (This is what a modified contain would do in principle).
Currently the contain (as well as the include function) always return undef.
Jira (PUP-6125) verbose agent runs result data being sent console and syslog
Title: Message Title Henrik Lindberg commented on PUP-6125 Re: verbose agent runs result data being sent console and syslog This seems to be backwards incompatible. Suggest instead changing behaviour so those that want can turn off logging to console when it is not wanted. That way there is no surprise. 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-6339) Hiera Data in Module give bad results when environment_timeout is unlimited
Title: Message Title Henrik Lindberg commented on PUP-6339 Re: Hiera Data in Module give bad results when environment_timeout is unlimited Looks like caching that should be associated with the compiler instance is associated with the environment. 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-6339) Hiera Data in Module give bad results when environment_timeout is unlimited
Title: Message Title Henrik Lindberg commented on PUP-6339 Re: Hiera Data in Module give bad results when environment_timeout is unlimited Ping Thomas Hallgren 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-6339) Hiera Data in Module give bad results when environment_timeout is unlimited
Title: Message Title Henrik Lindberg assigned an issue to Thomas Hallgren Puppet / PUP-6339 Hiera Data in Module give bad results when environment_timeout is unlimited Change By: Henrik Lindberg Assignee: Thomas Hallgren 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-6339) Hiera Data in Module give bad results when environment_timeout is unlimited
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6339 Hiera Data in Module give bad results when environment_timeout is unlimited Change By: Henrik Lindberg Priority: Normal Major 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-6339) Hiera Data in Module give bad results when environment_timeout is unlimited
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6339 Hiera Data in Module give bad results when environment_timeout is unlimited Change By: Henrik Lindberg Fix Version/s: PUP 4.5.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 (FACT-1405) Facter does not like next hop flags in ip route output
Title: Message Title Daniele Sluijters commented on FACT-1405 Re: Facter does not like next hop flags in ip route output Yup, it's the same problem, just a different attribute that it manifests on. It basically goes wrong on the assumption in Facter's code that you'll always get relatable pairs in the output dev eth0, proto kernel, scope link and so forth but that's not necessarily the case. 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.
