Jira (PUP-5648) Add Iterable type and runtime object
Title: Message Title Thomas Hallgren commented on PUP-5648 Re: Add Iterable type and runtime object I updated the PR to only cover the Iterable type and created PUP-5729 and PUP-5730 to cover the new reverse_each and step functions. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5648) Add Iterable type and runtime object
Title: Message Title Thomas Hallgren assigned an issue to Henrik Lindberg Puppet / PUP-5648 Add Iterable type and runtime object Change By: Thomas Hallgren Assignee: Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5729) Add a reverse_each function
Title: Message Title
Thomas Hallgren updated an issue
Puppet / PUP-5729
Add a reverse_each function
Change By:
Thomas Hallgren
Add a reverse_each function that takes one argument and an optional block. The argument must be of type `Iterable`.If the function is called without a block, it must return a new iterable that will yield each element of the given argument in reverse order.When a block is given, it must be called with each element of the given argument in reverse order. The argument is then returned.Example:{code:puppet}[1,3,5,7].reverse_each |$x| { notice($x) }{code}will result in the notices '7', '5', '3', '1'{code:puppet}$c = [1,3,5,7].reverse_each.map |$x| { $x * 10 }{code}Will result in:{code:puppet}$c == [70, 50, 30, 10].{code}
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
--
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 (NPUP-14) Parameter default value evaluation should have its own match scope
Title: Message Title Henrik Lindberg commented on NPUP-14 Re: Parameter default value evaluation should have its own match scope Merged to master at: b1c62ff Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-2186) PQL: Add experimental function for querying against PDB using AST
Title: Message Title Kenneth Barber commented on PDB-2186 Re: PQL: Add experimental function for querying against PDB using AST Do we need another ticket to create the actual function and its tests, or should we re-use this ticket? Just saying for tracking purposes etc. since the patch at the moment only covers a function. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5729) Add a reverse_each function
Title: Message Title Thomas Hallgren created an issue Puppet / PUP-5729 Add a reverse_each function Issue Type: Bug Assignee: Thomas Hallgren Created: 2016/01/21 3:31 AM Fix Versions: PUP 4.4.0 Priority: Normal Reporter: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs"
Jira (PUP-5730) Add a step() function
Title: Message Title Thomas Hallgren assigned an issue to Thomas Hallgren Puppet / PUP-5730 Add a step() function Change By: Thomas Hallgren Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5730) Add a step() function
Title: Message Title
Thomas Hallgren created an issue
Puppet / PUP-5730
Add a step() function
Issue Type:
Bug
Assignee:
Unassigned
Created:
2016/01/21 3:44 AM
Fix Versions:
PUP 4.4.0
Priority:
Normal
Reporter:
Thomas Hallgren
Add a step(iterable, n) function that takes two arguments and an optional block. The declared parameter types must be `Iterable` and `Integer[1]` (a positive integer).
If the function is called without a block, it must return a new iterable that will yield each nth element of the given argument When a block is given, it must be called with each nth element of the given argument. The argument is then returned.
Example:
[1,2,3,4,5,6,7,8].step(3) |$x| { notice($x) }
will result in the notices '1', '4', '7'
Jira (PUP-5729) Add a reverse_each function
Title: Message Title Thomas Hallgren assigned an issue to Henrik Lindberg Puppet / PUP-5729 Add a reverse_each function Change By: Thomas Hallgren Assignee: Thomas Hallgren Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5729) Add a reverse_each function
Title: Message Title
Thomas Hallgren updated an issue
Puppet / PUP-5729
Add a reverse_each function
Change By:
Thomas Hallgren
Add a reverse_each (iterable) function that takes one argument and an optional block. The argument declared parameter type must be of type `Iterable`.If the function is called without a block, it must return a new iterable that will yield each element of the given argument in reverse order.When a block is given, it must be called with each element of the given argument in reverse order. The argument is then returned.Example:{code:puppet}[1,3,5,7].reverse_each |$x| { notice($x) }{code}will result in the notices '7', '5', '3', '1'{code:puppet}$c = [1,3,5,7].reverse_each.map |$x| { $x * 10 }{code}Will result in:{code:puppet}$c == [70, 50, 30, 10].{code}
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
--
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-5730) Add a step() function
Title: Message Title Thomas Hallgren assigned an issue to Henrik Lindberg Puppet / PUP-5730 Add a step() function Change By: Thomas Hallgren Assignee: Thomas Hallgren Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-2316) (maint) Fix pretty-printing for PGObjects which are lists
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-2316 (maint) Fix pretty-printing for PGObjects which are lists Change By: Kenneth Barber Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-2316) (maint) Fix pretty-printing for PGObjects which are lists
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-2316 (maint) Fix pretty-printing for PGObjects which are lists Change By: Kenneth Barber Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-917) Identify why a cached catalog was used
Title: Message Title Nicholas Fagerlund commented on PUP-917 Re: Identify why a cached catalog was used Kylo Ginsberg Bump the report format. No way should we consider leaving this as version 4. If you receive a report object, you need some way to know what features are safe to use. If a given "version" is actually like three or four versions throughout its lifespan, the number becomes useless, and you'll have to do a bunch of defensive coding anyway. Sure, if the changes are all non-breaking, it's safe to rely on the lowest common denominator, but any new features are unsafe to use until the version bumps. So if you want to add a feature and have it actually be usable, bump it. FYI, that's also our existing precedent: I just checked the docs, and report format 4 is supposed to be backwards-compatible with format 3. (If we ignore PUP-5341.) Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-2564) Specify UTF-8 as a default encoding for puppet
Title: Message Title Henrik Lindberg commented on PUP-2564 Re: Specify UTF-8 as a default encoding for puppet We must have a ticket to add the "all pp language source must be in UTF-8" requirement to the language specification. (Will follow up on PUP-1301 , if one is linked there and otherwise create it. For Language, we must also deal with Puppet::Filesystem.read method as it does not accept encoding. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5670) Tag the release and create packages (PUP 3.8.5)
Title: Message Title Sean McDonald commented on PUP-5670 Re: Tag the release and create packages (PUP 3.8.5) The new SHA with updated msi ref to facter: 3d3962b971b38b962252e26d43687e445b2f67ed Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-1313) fqdn acceptance test failing on Solaris 11
Title: Message Title John Duarte assigned an issue to John Duarte Facter / FACT-1313 fqdn acceptance test failing on Solaris 11 Change By: John Duarte Assignee: qa John Duarte Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5670) Tag the release and create packages (PUP 3.8.5)
Title: Message Title Sean McDonald commented on PUP-5670 Re: Tag the release and create packages (PUP 3.8.5) builds for fixed SHA available at: http://builds.puppetlabs.lan/puppet/3.8.5/ Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5648) Add Iterable type and runtime object
Title: Message Title Henrik Lindberg commented on PUP-5648 Re: Add Iterable type and runtime object Thanks for splitting up the work into several tickets. Helps focusing on one thing at the time. Agree on your suggestion that a cap function is best as coming after the unbound (it pulls at most n times). Regarding the difference in opinion about Iterator - I like to think that objects of type T for which an Iterable[T] can be created are different than an instance of Iterable[?] even if asking for an Iterable for an Iterable. The only thing I want is to be able to tell an actual Iterable apart from the others. I cannot do that with: $x =~ Iterable Since that would be true for both an Array (and a bunch of others), as well as Iterable. I think I would need the type_of function, and then check if the type == Iterable. So, how do you tell them apart? Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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
Jira (PUP-5731) Specify that Puppet Language Source must be in UTF-8
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-5731 Specify that Puppet Language Source must be in UTF-8 Issue Type: Task Assignee: Unassigned Created: 2016/01/21 6:42 AM Priority: Normal Reporter: Henrik Lindberg The language specification should state that all Puppet Language Source text must be in UTF-8. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
Jira (PUP-5732) Puppet::Filesystem.read should handle encoding
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-5732 Puppet::Filesystem.read should handle encoding Issue Type: Task Assignee: Unassigned Created: 2016/01/21 6:45 AM Fix Versions: PUP 4.4.0 Priority: Normal Reporter: Henrik Lindberg The Puppet::Filesystem.read method does not handle an encoding argument which creates problems due to then reading in the platform's native encoding. Add Comment
Jira (PUP-5733) The Puppet Parser should ensure files are read with UTF-8
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-5733 The Puppet Parser should ensure files are read with UTF-8 Issue Type: Bug Assignee: Unassigned Created: 2016/01/21 6:54 AM Fix Versions: PUP 4.4.0 Priority: Normal Reporter: Henrik Lindberg The Puppet Parser should ensure that source files are read with UTF-8 encoding. One such place is in the Lexer where it uses Puppet::Filesystem.read ( which currently dos not accept an encoding argument - see PUP-5732). Another place is the Puppet Function Instantiator. In this ticket, it is important to track down the paths that leads to lexing of puppet source. It is possible to give the lexer a string - and that string may come from many different sources (mainly testing). There may be some places other than the two mentioned above where a file is read and the string the given to the lexer. Add Comment
Jira (PUP-5648) Add Iterable type and runtime object
Title: Message Title Thomas Hallgren commented on PUP-5648 Re: Add Iterable type and runtime object That's pretty much the same question as $x =~ Data, isn't it? You'll need to check if it's an Array, as well as Data. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-1313) fqdn acceptance test failing on Solaris 11
Title: Message Title John Duarte updated an issue Facter / FACT-1313 fqdn acceptance test failing on Solaris 11 Change By: John Duarte Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-2564) Specify UTF-8 as a default encoding for puppet
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-2564 Specify UTF-8 as a default encoding for puppet Change By: Henrik Lindberg Fix Version/s: PUP 4.0.0 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5713) ClassInformationService.classes_per_environment errantly evaluates parameter default expression
Title: Message Title Steve Barlow updated an issue Puppet / PUP-5713 ClassInformationService.classes_per_environment errantly evaluates parameter default _expression_ Change By: Steve Barlow Sprint: Int Language 2016-01-27 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5684) Windows ADSI User and Group exists? checks are invalid
Title: Message Title Ethan Brown updated an issue Puppet / PUP-5684 Windows ADSI User and Group exists? checks are invalid Change By: Ethan Brown Release Notes Summary: Puppet may have internally considered a Windows User or Group to exist when it does not, preventing the User / Group from being created. Based on how this code was used however, this likely had no user facing impact. Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5734) Value of the key dependencies in the metadata.json of modules isn't checked
Title: Message Title Reinhard Vicinus assigned an issue to Reinhard Vicinus Puppet / PUP-5734 Value of the key dependencies in the metadata.json of modules isn't checked Change By: Reinhard Vicinus Assignee: Reinhard Vicinus Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-917) Identify why a cached catalog was used
Title: Message Title Josh Cooper commented on PUP-917 Re: Identify why a cached catalog was used Nicholas Fagerlund Makes sense. Unfortunately, we haven't always been consistent (ignoring the PUP-5341 bug). Report [format 3 added environment|github.com/puppetlabs/puppet/commit/605e34d463ba837983cabcff8bb1232751ebab40], format 4 added the containment path, but in between we added transaction_uuid, but didn't bump the report format. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5640) Windows package provider can crash with "Memory access is out of bounds" when registry values are corrupt
Title: Message Title Ethan Brown updated an issue Puppet / PUP-5640 Windows package provider can crash with "Memory access is out of bounds" when registry values are corrupt Change By: Ethan Brown Release Notes Summary: Corrupt registry data could previously cause the Windows Puppet package provider to crash. Registry handling has been improved in Puppet so that invalid data no longer causes a crash. Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5646) fqdn_rand in real world - only 336 of possible 1440 daily cron slots ever used.
Title: Message Title Henrik Lindberg commented on PUP-5646 Re: fqdn_rand in real world - only 336 of possible 1440 daily cron slots ever used. The reason for the increased (better spread) is that the entropy in the hexdigest increases when the length of the string (and its entropy) increases. Entropy is important for a pseudo random number generator. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5426) config set ignores --section and can insert duplicate settings if they are in [main]
Title: Message Title Joshua Partlow commented on PUP-5426 Re: config set ignores --section and can insert duplicate settings if they are in [main] Ok, this is a truly bizarre bug. It seems to be the presence of the duplicate server setting, and also it's position that's involved. On 4.2.3: [main] server = exl7i0vi62ouagu.delivery.puppetlabs.net environment = production [agent] server = exl7i0vi62ouagu.delivery.puppetlabs.net certname = qcpd7c0tnvnp4kd.delivery.puppetlabs.net [main] server = exl7i0vi62ouagu.delivery.puppetlabs.net environment = production
Jira (NPUP-14) Parameter default value evaluation should have its own match scope
Title: Message Title Steve Barlow commented on NPUP-14 Re: Parameter default value evaluation should have its own match scope This ticket was dropped into the integration sprint by mistake. Moving it back to Language where it belongs. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 (NPUP-14) Parameter default value evaluation should have its own match scope
Title: Message Title Steve Barlow updated an issue Native Puppet / NPUP-14 Parameter default value evaluation should have its own match scope Change By: Steve Barlow Sprint: Int Language 2016-01-27 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5713) ClassInformationService.classes_per_environment errantly evaluates parameter default expression
Title: Message Title Steve Barlow commented on PUP-5713 Re: ClassInformationService.classes_per_environment errantly evaluates parameter default _expression_ This ticket was dropped into the integration sprint by mistake. Moving it back to Language where it belongs. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5734) Value of the key dependencies in the metadata.json of modules isn't checked
Title: Message Title
Reinhard Vicinus created an issue
Puppet / PUP-5734
Value of the key dependencies in the metadata.json of modules isn't checked
Issue Type:
Bug
Affects Versions:
PUP 4.3.1
Assignee:
Unassigned
Components:
Language
Created:
2016/01/21 8:29 AM
Priority:
Normal
Reporter:
Reinhard Vicinus
With the following metadata.json in a module:
{
"name": "",
Jira (PUP-474) Make Puppet Data types immutable in a safe way
Title: Message Title Thomas Hallgren commented on PUP-474 Re: Make Puppet Data types immutable in a safe way I think this can be closed. Immutability was added as part of PUP-4702 . Henrik Lindberg, what do you think? Are there more aspects to cover? Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-2260) PuppetDB Terminus doesn't use dns name, uses hostname
Title: Message Title David commented on PDB-2260 Re: PuppetDB Terminus doesn't use dns name, uses hostname Thank you! Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5735) Remove usage of win32-security gem
Title: Message Title Ethan Brown created an issue Puppet / PUP-5735 Remove usage of win32-security gem Issue Type: Task Assignee: Unassigned Created: 2016/01/21 10:02 AM Fix Versions: PUP 4.3.3 Priority: Normal Reporter: Ethan Brown With PUP-5538 , we reduced our dependency on the win32-security gem. We should fully deprecate its usage. This includes: Moving all the well-known SID constants that are being used into Puppet::Util::Windows::SID Audit the modules on the forge, and notify authors up front that there might be breaking changes going forward - look for strings like win32/security, Win32::Security, etc Remove the inclusion of win32/security anywhere that it occurs - for instance - https://github.com/puppetlabs/puppet/blob/ba5cfc392d597d22fa98e6d62b48f730845b6f22/lib/puppet/util/windows/security.rb#L68 Removal of the actual gem from the puppet-win32-ruby repository branches so that it's not included in the MSI any longer. The
Jira (PUP-5646) fqdn_rand in real world - only 336 of possible 1440 daily cron slots ever used.
Title: Message Title Kylo Ginsberg commented on PUP-5646 Re: fqdn_rand in real world - only 336 of possible 1440 daily cron slots ever used. Steve Traylen ah, gotcha. Yes, the seeds today would be identical for all single-parameter invocations of fqdn_rand for a particular host. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-917) Identify why a cached catalog was used
Title: Message Title Kylo Ginsberg commented on PUP-917 Re: Identify why a cached catalog was used I'm +1 on bumping the report version for all changes going forward. In docs, we should add a statement that it is doesn't adhere to semver, so a version bump doesn't imply (but may include) breaking changes. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-2985) Win32-Security does not work with fully qualified ALL APPLICATION PACKAGES group
Title: Message Title
Ethan Brown commented on PUP-2985
Re: Win32-Security does not work with fully qualified ALL APPLICATION PACKAGES group
Now that
PUP-5538
is merged and some of the underlying code has been rewritten... I revisited this on Windows 2012R2.
The SID S-1-15-2-1 is the well-known SID for ALL APPLICATION PACKAGES, so we can perform a lookup that way:
Puppet::Util::Windows::SID.name_to_sid_object('S-1-15-2-1')
The results are correct as:
irb(main):003:0> Puppet::Util::Windows::SID.name_to_sid_object('S-1-15-2-1')
=> #
@account="ALL APPLICATION PACKAGES",
@sid_bytes=[1, 2, 0, 0, 0, 0, 0, 15, 2, 0, 0, 0, 1, 0, 0, 0],
@sid="S-1-15-2-1",
@domain="APPLICATION PACKAGE AUTHORITY",
@domain_account="APPLICATION PACKAGE AUTHORITY\\ALL
Jira (PUP-5591) undefined local variable or method `data' for Puppet::Provider::Package::Windows::Package:Class
Title: Message Title Fabio Vimercati commented on PUP-5591 Re: undefined local variable or method `data' for Puppet::Provider::Package::Windows::Package:Class Ryan Anderson is 2015.3.1 (Gold) a version for paid PE customers? I'm not seeing the changes in my 2015.3.1 install. How do I get this? Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5560) Look at Improving Unicode for all Windows gems
Title: Message Title
Ethan Brown updated an issue
Puppet / PUP-5560
Look at Improving Unicode for all Windows gems
Change By:
Ethan Brown
* {{win32-security}} has problems - https://github.com/puppetlabs/puppet-win32-ruby/blob/2.1.x-x64/ruby/lib/ruby/gems/2.1.0/gems/win32-security-0.2.5/lib/win32/security/windows/functions.rb - see {{ConvertSidToStringSidA}}, {{ConvertStringSidToSidA}}, {{LookupAccountNameA}}, {{LookupAccountSidA}} - this has mostly been addressed in PUP-5538, and an additional ticket for some minor cleanup has opened as PUP-5735 * {{win32-service}} has problems - https://github.com/puppetlabs/puppet-win32-ruby/blob/2.1.x-x64/ruby/lib/ruby/gems/2.1.0/gems/win32-service-0.8.6/lib/win32/windows/functions.rb#L24-L75 - see {{CreateEventA}}, {{FormatMessageA}}, {{ChangeServiceConfigA}}, {{ChangeServiceConfig2A}}, {{CreateServiceA}}, {{EnumServicesStatusExA}}, {{GetServiceDisplayNameA}}, {{GetServiceKeyNameA}}, {{LookupPrivilegeValueA}}, {{OpenSCManagerA}}, {{OpenServiceA}}, {{QueryServiceConfigA}}, {{QueryServiceConfig2A}}, {{RegisterServiceCtrlHandlerExA}}, {{StartServiceA}}, {{StartServiceCtrlDispatcherA}}* {{win32-process}} has problems - https://github.com/puppetlabs/puppet-win32-ruby/blob/2.1.x-x64/ruby/lib/ruby/gems/2.1.0/gems/win32-process-0.7.4/lib/win32/process/functions.rb - see {{GetModuleHandleA}}, {{GetVersionExA}}, {{GetVolumeInformationA}}, {{CreateJobObjectA}}, {{OpenJobObjectA}}, {{ConvertSidToStringSidA}}* {{win32-eventlog}} has problems - https://github.com/puppetlabs/puppet-win32-ruby/blob/2.1.x-x64/ruby/lib/ruby/gems/2.1.0/gems/win32-eventlog-0.6.2/lib/win32/windows/functions.rb - see {{ClearEventLogA}}, {{LookupAccountSidA}}, {{OpenEventLogA}}, {{OpenBackupEventLogA}}, {{ReadEventLogA}}, {{RegConnectRegistryA}}, {{RegCreateKeyExA}}, {{RegisterEventSourceA}}, {{RegOpenKeyExA}}, {{RegQueryValueExA}}, {{RegSetValueExA}}, {{ReportEventA}}, {{CreateEventA}}, {{ExpandEnvironmentStringsA}}, {{FormatMessageA}}, {{LoadLibraryExA}}I have filed upstream tickets* https://github.com/djberg96/win32-security/issues/8* https://github.com/djberg96/win32-service/issues/32* https://github.com/djberg96/win32-process/issues/21* https://github.com/djberg96/win32-eventlog/issues/19
Add Comment
Jira (PUP-5591) undefined local variable or method `data' for Puppet::Provider::Package::Windows::Package:Class
Title: Message Title Ethan Brown updated an issue Puppet / PUP-5591 undefined local variable or method `data' for Puppet::Provider::Package::Windows::Package:Class Change By: Ethan Brown Release Notes Summary: Attempting to read REG_BINARY registry data would previously cause Puppet to crash on Windows. This no longer occurs. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-1316) [Facter 2.4.5] On Virtuozzo containers "ipaddress" becomes 127.0.0.1
Title: Message Title Adi Pircalabu commented on FACT-1316 Re: [Facter 2.4.5] On Virtuozzo containers "ipaddress" becomes 127.0.0.1 Looks like the test for ^127 has been removed from 2.4.5 and this is obviously affecting openvz: ifconfig | grep "inet addr|Link" lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 venet0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 inet addr:127.0.0.1 P-t-P:127.0.0.1 Bcast:0.0.0.0 Mask:255.255.255.255 venet0:0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 inet addr:192.168.1.171 P-t-P:1192.168.1.171 Bcast:192.168.1.171 Mask:255.255.255.255 venet0:1 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 inet addr:192.168.1.172 P-t-P:1192.168.1.172 Bcast:192.168.1.172 Mask:255.255.255.255 [...] — /tmp/ipaddress.rb.2.4.4 2015-05-20 02:41:16.0 +1000 +++ /tmp/ipaddress.rb.2.4.5 2016-01-21 09:31:53.0 +1100 @@ -3,7 +3,9 @@ Purpose: Return the main IP address for a host. # Resolution: On the Unixes does an ifconfig, and returns the first non 127.0.0.0/8 +# On Linux and AIX, it examines the routing table and uses the IP address +# of the default interface. +# On other Unixes does an ifconfig, and returns the first non 127.0.0.0/8 subnetted IP it finds. On Windows, it attempts to use the socket library and resolve the machine's hostname via DNS. @@ -27,19 +29,8 @@ Facter.add(:ipaddress) do confine :kernel => :linux setcode do ip = nil output = Facter::Util::IP.exec_ifconfig(["2>/dev/null"]) if output regexp = /inet (?:addr?([0-9] \.[0-9] \.[0-9] \.[0-9] )/
Jira (PUP-5120) Send checksum_type and static_catalog query params in catalog request
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet / PUP-5120 Send checksum_type and static_catalog query params in catalog request Change By: Michael Smith Assignee: Michael Smith Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5591) undefined local variable or method `data' for Puppet::Provider::Package::Windows::Package:Class
Title: Message Title Ethan Brown commented on PUP-5591 Re: undefined local variable or method `data' for Puppet::Provider::Package::Windows::Package:Class Fabio Vimercati this is part of the soon-to-be-released puppet-agent 1.3.3, which will be announced soon. Please keep an eye on https://groups.google.com/forum/#!forum/puppet-announce for the announcement. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5729) Add a reverse_each function
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5729 Add a reverse_each function Moving this to Language Triage sprint. Not sure if this will be ready for 4.4.0 and other things may have higher priority. Also need to finish the Iterable type first, and how to deal with the new kind of runtime object. Change By: Henrik Lindberg Scope Change Category: Found Sprint: Language 2016-01-27 Triage Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5648) Add Iterable type and runtime object
Title: Message Title Thomas Hallgren commented on PUP-5648 Re: Add Iterable type and runtime object Why don't you consider Iterable to be completely abstract? I really want to do that because I can see no gain in exposing the internal workings of the iterative functions. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-1963) Generated resources never receive dependency edges
Title: Message Title Branan Riley commented on PUP-1963 Re: Generated resources never receive dependency edges Given that our previous behavior was to allow dependencies and silently ignore notifies, I'm kind of inclined to just do PUP-4647. Even though option 2 is more "correct" to our current documented behavior, it might still cause brekages for other users who have managed to accidentally order a resource purge while the check was unenforced. Since we want to eventually get rid of the check anyway, I think going from "ordering allowed but notifies don't work" to "all ordering metaparameters work as expected" is a way better move than "fixing" the documented purges-can't-be-ordered behavior. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5648) Add Iterable type and runtime object
Title: Message Title Henrik Lindberg commented on PUP-5648 Re: Add Iterable type and runtime object If I do this: $a = [1,2,3].reverse_each then, $a is bound to a instance of Iterable, and it is no longer a pure implementation concern as the instance of Iterable that wraps the Array knows it is in "reverse". It is not abstract, there is an actual instance, and it is not the same as an Array. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-488) Add support for Arista EOS to Hiera acceptance tests
Title: Message Title Steve Barlow updated an issue Hiera / HI-488 Add support for Arista EOS to Hiera acceptance tests Change By: Steve Barlow Fix Version/s: HI 3.0.6 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5738) systemd provider doesn't seem to respect the hasstatus param
Title: Message Title Ben Ford created an issue Puppet / PUP-5738 systemd provider doesn't seem to respect the hasstatus param Issue Type: Improvement Assignee: Kylo Ginsberg Components: Types and Providers Created: 2016/01/21 3:27 PM Priority: Normal Reporter: Ben Ford Documentation explains that setting hasstatus => false and then setting a custom status command would use your custom status command. This does not seem to work properly on the systemd provider. systemctl is used regardless. Overriding to provider => base makes the parameter have effect. https://docs.puppetlabs.com/references/latest/type.html#service Add Comment
Jira (PUP-5648) Add Iterable type and runtime object
Title: Message Title Henrik Lindberg commented on PUP-5648 Re: Add Iterable type and runtime object I think it is important to have a defined way in Ruby to check for the type of Iterable in such a way that it does not have to have a priory knowledge of all possible kinds of iterables. This, if you are writing functions for communication, if you are in JRuby/Java land etc. Using the Puppet type system would be nice , i.e. having an Iterator type), but checking against a ruby "marker module" would also be fine. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-146) Install multiple packages with one call to the underlying package manager
Title: Message Title Bill Niestempski updated an issue Puppet / PUP-146 Install multiple packages with one call to the underlying package manager Change By: Bill Niestempski CS Priority: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5591) undefined local variable or method `data' for Puppet::Provider::Package::Windows::Package:Class
Title: Message Title Ryan Anderson commented on PUP-5591 Re: undefined local variable or method `data' for Puppet::Provider::Package::Windows::Package:Class I think you meant to tag a different Ryan Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-489) Add support for Cumulus to Hiera acceptance tests
Title: Message Title Steve Barlow updated an issue Hiera / HI-489 Add support for Cumulus to Hiera acceptance tests Change By: Steve Barlow Fix Version/s: HI 3.0.6 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5739) Tag puppet specifications repo to indicate where it was at release of puppet 4.3.2
Title: Message Title Henrik Lindberg commented on PUP-5739 Re: Tag puppet specifications repo to indicate where it was at release of puppet 4.3.2 When done, pull straight through to closed. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5739) Tag puppet specifications repo to indicate where it was at release of puppet 4.3.2
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-5739 Tag puppet specifications repo to indicate where it was at release of puppet 4.3.2 Issue Type: Task Assignee: Unassigned Created: 2016/01/21 3:41 PM Priority: Normal Reporter: Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5120) Send checksum_type and static_catalog query params in catalog request
Title: Message Title Josh Cooper commented on PUP-5120 Re: Send checksum_type and static_catalog query params in catalog request Christopher Price and I talked about a single digest algorithm previously, but sending a list of supported algorithms is nice from a future proof perspective. Thoughts Kylo Ginsberg? As far as the master using the checksum_type, that should be handled via PUP-5117 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5730) Add a step() function
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5730 Add a step() function Change By: Henrik Lindberg Sprint: Language 2016-01-27 Triage Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5120) Send checksum_type and static_catalog query params in catalog request
Title: Message Title Kylo Ginsberg commented on PUP-5120 Re: Send checksum_type and static_catalog query params in catalog request I'm +1 on the idea of sending a list of supported algorithms. If that runs into some snag though, we could revisit that in the name of expedience. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5730) Add a step() function
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5730 Add a step() function Moving this to triage, we need to finish Iterable type first, and the consequences of returning new runtime types into the puppet language. Lets decide then when this goes in. Change By: Henrik Lindberg Scope Change Category: Found Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5736) Remove usage of win32-process gem
Title: Message Title Ethan Brown updated an issue Puppet / PUP-5736 Remove usage of win32-process gem Change By: Ethan Brown For starters, the affected parts appear to be:* [lib/puppet/feature/base.rb|https://github.com/puppetlabs/puppet/blob/d2199af906fa5ca19ec0c37c82794934ea4fb4b5/lib/puppet/feature/base.rb#L23]* [lib/puppet/util/windows/process.rb|https://github.com/puppetlabs/puppet/blob/1a557254012447a4f0a2e01eeebaf52c75ab6f80/lib/puppet/util/windows/process.rb#L2]* [lib/puppet/util/pidlock.rb|https://github.com/puppetlabs/puppet/blob/d2199af906fa5ca19ec0c37c82794934ea4fb4b5/lib/puppet/util/pidlock.rb#L50-L52]* [puppet/ext/windows/service/daemon.rb|https://github.com/puppetlabs/puppet/blob/d2199af906fa5ca19ec0c37c82794934ea4fb4b5/ext/windows/service/daemon.rb#L6]* [puppet/install.rb|https://github.com/puppetlabs/puppet/blob/d2199af906fa5ca19ec0c37c82794934ea4fb4b5/install.rb#L247]However, note that Win32::Process actually monkey patches the process object - https://github.com/djberg96/win32-process/blob/ffi/lib/win32/process.rbSo we'll also want to look for calls to these functions as well:* - get_affinity - * - getpriority - * setpriority - https://github.com/puppetlabs/puppet/blob/d2199af906fa5ca19ec0c37c82794934ea4fb4b5/lib/puppet/util/limits.rb#L8 * uid - requires a more in-depth search * - getrlimit - * - setrlimit - * create - requires a more in-depth search * kill - https://github.com/puppetlabs/puppet/blob/d2199af906fa5ca19ec0c37c82794934ea4fb4b5/lib/puppet/util/pidlock.rb#L55 / https://github.com/puppetlabs/puppet/blob/d2199af906fa5ca19ec0c37c82794934ea4fb4b5/lib/puppet/util/execution.rb#L206 * - get_exitcode - * - snapshot - Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
Jira (PUP-5648) Add Iterable type and runtime object
Title: Message Title Henrik Lindberg commented on PUP-5648 Re: Add Iterable type and runtime object There is never anything that is an instance of Data floating around in the system - that type is completely abstract. That is not the case for Iterable, and that is precisely why I want to be able to tell them a part. I am fine if it is encoded in Iterable actually, but it is kind of ugly. I.e. Iterable[T, true] could mean what I called Iterator such that all of these are true: [1,2,3] =~ Iterable [1,2,3] =~ Iterable[Any, false] [1,2,3] !~ Iterable[Any, true] We currently have the type_of in stdlib. I would like that function in puppet (or that we had an operator that means type_of. If we have that, then it would be perfectly ok to do this: $x.type_of == Type[Iterable] Add Comment
Jira (FACT-1293) Add support for Arista EOS to Facter acceptance tests
Title: Message Title Steve Barlow updated an issue Facter / FACT-1293 Add support for Arista EOS to Facter acceptance tests Change By: Steve Barlow Fix Version/s: FACT 3.1.4 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-1312) Update Facter Acceptance tests for cumulus
Title: Message Title Steve Barlow updated an issue Facter / FACT-1312 Update Facter Acceptance tests for cumulus Change By: Steve Barlow Fix Version/s: FACT 3.1.4 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5120) Send checksum_type and static_catalog query params in catalog request
Title: Message Title Michael Smith commented on PUP-5120 Re: Send checksum_type and static_catalog query params in catalog request Any thoughts on whether we send Puppet[:digest_algorithm] vs a list of supported algorithms? I think I'll start down the route of using a list of supported algorithms, and the master can pick the first one that it supports. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5591) undefined local variable or method `data' for Puppet::Provider::Package::Windows::Package:Class
Title: Message Title Ryan Gard commented on PUP-5591 Re: undefined local variable or method `data' for Puppet::Provider::Package::Windows::Package:Class Fabio Vimercati No, the (Gold) indication is just to inform people that I'm using the shipped PE bits and not a development build. Don't worry, there is only one 2015.3.1. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-1963) Generated resources never receive dependency edges
Title: Message Title
Branan Riley commented on PUP-1963
Re: Generated resources never receive dependency edges
I'm going to start with a simple example, and work up to what happens with stages. Previously, the following catalog:
resources{ 'host':
purge => true
} ->
exec { 'reboot':
path => '/sbin'
}
Would create the following graph, with the evaluation order below it. Note that the graph doesn't actually contain the edges for the Exec dependency, even though they are guaranteed to evaluate immediately after the Resources resource, and thus the edge can be said to be implied.
Whit[Admissible_stage[main]] --> Resources[host] > Whit[Completed_stage[main]]
Jira (PUP-5648) Add Iterable type and runtime object
Title: Message Title Thomas Hallgren commented on PUP-5648 Re: Add Iterable type and runtime object I don't agree at all. Depending on implementation, this might well be true (it won't be with the current implementation, but that's beside the point): [3.2.1] == [1,2,3].reverse_each [1,2,3].reverse_each =~ Array My point is, you shouldn't make no other assumption about what the result of an iterative function is other than: [1,2,3].reverse_each ~= Iterable If you do, the you lock your code into one specific implementation and we don't want to add implementation specifics into the Puppet spec. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
Jira (PUP-5648) Add Iterable type and runtime object
Title: Message Title Henrik Lindberg commented on PUP-5648 Re: Add Iterable type and runtime object If we add type promotion / transformation yes, than we never need to know the type in the Puppet Language. An implementor of a function in Ruby should expect certain methods to be there if it is one or the other. We must deliver something that ruby is_a? Array since we have specified that Puppet Array is represented by Ruby Array. Hence, the conversion must be considered when matching against types in a a dispatcher, and the invocation logic must handle the type transformation. The transformation must also kick in when serializing. (It is both serialized and deserialized as an array, and if the Iterable is unbound it is an error to serialize it, or transform it into an Array. As long as that is not handled, we should not have any functions that returns an implementation of an Iterable other than the already supported concrete data types (e.g. instances of Array). The same rationale as for lambda (you are not allowed to return one since it is not first order in the language. (For lambda, when we have a sane stack implementation, we can implement the call operation or a call function). Same thing here. At the same time, we are in no particular hurry. It is very nice to have but no one is screaming for it. I can imagine adding the type first without exposing the functions to the puppet language.. The idea of representing the "iterator" is that you would not have to do all that yet. It is defined what it is, and the operators does not support it, and there is no promotion. Serialization must however be handled or they will for sure end up in catalogs with completely weird behavior as the result. This does not hide the implementation details completely, but to a very large degree, as the "iterator" type would include all such implementations whatever they may be (they must share some Ruby method API, but that is all). (I tried to find a synonym to Iterator, but found none, and Iterable/Iterator, sort of goes hand in hand (Enumerble and Enumerator in Ruby terminlogy). I do agree that it is not an Iterator in the sense of a Java Iterator as it does not hold iteration state, the actual iterator in puppet is the function that drives the iteration. At the same time, I would rather have the nice and opaque implementation. Do you want to do it that way? If so, we do not release this as a feature until all parts are ready - say Puppet 5.0.0 (I don't think this has high enough priority for 4.4.0 to push out some of the other things (and 4.4.0 is not far away)). Add Comment
Jira (PUP-42) Support data and puppet extensions contributed from modules
Title: Message Title Bill Niestempski updated an issue Puppet / PUP-42 Support data and puppet extensions contributed from modules Change By: Bill Niestempski CS Priority: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5120) Send checksum_type and static_catalog query params in catalog request
Title: Message Title Michael Smith commented on PUP-5120 Re: Send checksum_type and static_catalog query params in catalog request Does the node end-point need to know we're using a static catalog? Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5378) acceptance: backport call all parser functions test to 3.x
Title: Message Title Steve Barlow updated an issue Puppet / PUP-5378 acceptance: backport call all parser functions test to 3.x Change By: Steve Barlow Fix Version/s: PUP 4.3.2 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-1316) [Facter 2.4.5] On Virtuozzo containers "ipaddress" becomes 127.0.0.1
Title: Message Title Adi Pircalabu created an issue Facter / FACT-1316 [Facter 2.4.5] On Virtuozzo containers "ipaddress" becomes 127.0.0.1 Issue Type: Bug Affects Versions: FACT 2.4.5 Assignee: Unassigned Components: Community Created: 2016/01/21 2:13 PM Priority: Major Reporter: Adi Pircalabu facter virtual openvz Facter 2.4.4: facter | grep "^ip" ipaddress => 192.168.1.171 ipaddress_lo => 127.0.0.1 ipaddress_venet0 => 127.0.0.1 ipaddress_venet0_0 => 192.168.1.171 ipaddress_venet0_1 => 192.168.1.172 Facter 2.4.5: facter | grep "^ip" ipaddress => 127.0.0.1 ipaddress_lo => 127.0.0.1 ipaddress_venet0 => 127.0.0.1 ipaddress_venet0_0 => 192.168.1.171 ipaddress_venet0_1 => 192.168.1.172 Didn't replicate it for Xen domU or physical nodes.
Jira (PUP-917) Identify why a cached catalog was used
Title: Message Title William Hopper commented on PUP-917 Re: Identify why a cached catalog was used Hey Nicholas Fagerlund! I'm now to the stage where I'm remembering how bad I am at naming things and could use some advice on how we ought to represent the values of this new entry in the report. Like Kylo said, the three basic states will essentially be: Not used Used because use_cached_catalog was set Used because new catalog failed to compile and usecacheonfailure was set I've come up with the key cached_catalog_status for the report, but we'd like to try and come up with short (maybe even one word?) descriptors for these states that can be used down the line in things like queries by PuppetDB. Do you think you might have any ideas? Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5625) Problems with the "allow_duplicate_csr" acceptance test
Title: Message Title Steve Barlow updated an issue Puppet / PUP-5625 Problems with the "allow_duplicate_csr" acceptance test Change By: Steve Barlow Fix Version/s: PUP 4.3.2 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5653) Remove static node config for Cumulus
Title: Message Title Steve Barlow updated an issue Puppet / PUP-5653 Remove static node config for Cumulus Change By: Steve Barlow Fix Version/s: PUP 4.3.2 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5654) Remove static node config for Arista
Title: Message Title Steve Barlow updated an issue Puppet / PUP-5654 Remove static node config for Arista Change By: Steve Barlow Fix Version/s: PUP 4.3.2 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-474) Make runtime objects immutable in a safe way
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-474 Make runtime objects immutable in a safe way Change By: Henrik Lindberg Summary: Make Puppet Data types runtime objects immutable in a safe way Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5713) ClassInformationService.classes_per_environment errantly evaluates parameter default expression
Title: Message Title Kylo Ginsberg commented on PUP-5713 Re: ClassInformationService.classes_per_environment errantly evaluates parameter default _expression_ Ah, our good friend, The Law of Unintended Consequence has struck. This is a regression so it's targeted at stable. Stable is locked for the moment because of our (current, I'm not a fan) puppet-agent de facto release process. Anyhoo, that lock will be lifted real soon now, puppet#stable will be merged to puppet#master (by hand, but we usually do this real soon after a stable merge), and then master will be promoted to 2016.1.x. tldr: wait a few days. Won't be weeks. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-474) Make Puppet Data types immutable in a safe way
Title: Message Title Henrik Lindberg commented on PUP-474 Re: Make Puppet Data types immutable in a safe way This is about making the instances immutable to avoid things like rogue functions using the Ruby API to modify the runtime objects. In Ruby, we could probably deep freeze all instances that the language creates, but it becomes more difficult elsewhere (time consuming if not built into serializers (say you read large hash from hiera), or via pupptdb query and get a large set back. Will change the title to make the distinction "instances" runtime-objects vs. Data Type (e.g. Integer, Variant) clear. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-474) Make runtime objects immutable in a safe way
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-474 Make runtime objects immutable in a safe way Change By: Henrik Lindberg It is a benefit to have runtime implementation of the data types (i.e. immutable String, Array, Hash etc.) used by puppet because:PRO:* Implementations of Hash and Array can ensure immutability* Strings can be automatically frozen to ensure immutability* Type calculations on Array and Hash can be cached since collection can only be constructed, not altered (i.e. type is inferred only once)* Easier to serializeCON:* Probably slower since impl is in Ruby* Potential breaks because of is_a? checks in functions/types etc.* Conversion to regular types may be required at boundariesALTERNATIVE* freeze strings at boundary* recursively freeze collections at boundaryfreezing something given requires a copy since it may have bad effect on caller (i.e. side effect on given argument).OR:* do it like now; "lucky go happy" + documentation Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5578) parse_string doesnt interpolate %{key} with Puppet 4.0
Title: Message Title
John Duarte commented on PUP-5578
Re: parse_string doesnt interpolate %{key} with Puppet 4.0
Daniel Scott, the puppetserver nighties pin to released versions of puppet.
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
--
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-5560) Look at Improving Unicode for all Windows gems
Title: Message Title
Ethan Brown updated an issue
Puppet / PUP-5560
Look at Improving Unicode for all Windows gems
Change By:
Ethan Brown
* {{win32-security}} has problems - https://github.com/puppetlabs/puppet-win32-ruby/blob/2.1.x-x64/ruby/lib/ruby/gems/2.1.0/gems/win32-security-0.2.5/lib/win32/security/windows/functions.rb - see {{ConvertSidToStringSidA}}, {{ConvertStringSidToSidA}}, {{LookupAccountNameA}}, {{LookupAccountSidA}} - this has mostly been addressed in PUP-5538, and an additional ticket for some minor cleanup has opened as PUP-5735* {{win32-service}} has problems - https://github.com/puppetlabs/puppet-win32-ruby/blob/2.1.x-x64/ruby/lib/ruby/gems/2.1.0/gems/win32-service-0.8.6/lib/win32/windows/functions.rb#L24-L75 - see {{CreateEventA}}, {{FormatMessageA}}, {{ChangeServiceConfigA}}, {{ChangeServiceConfig2A}}, {{CreateServiceA}}, {{EnumServicesStatusExA}}, {{GetServiceDisplayNameA}}, {{GetServiceKeyNameA}}, {{LookupPrivilegeValueA}}, {{OpenSCManagerA}}, {{OpenServiceA}}, {{QueryServiceConfigA}}, {{QueryServiceConfig2A}}, {{RegisterServiceCtrlHandlerExA}}, {{StartServiceA}}, {{StartServiceCtrlDispatcherA}}* {{win32-process}} has problems - https://github.com/puppetlabs/puppet-win32-ruby/blob/2.1.x-x64/ruby/lib/ruby/gems/2.1.0/gems/win32-process-0.7.4/lib/win32/process/functions.rb - see {{GetModuleHandleA}}, {{GetVersionExA}}, {{GetVolumeInformationA}}, {{CreateJobObjectA}}, {{OpenJobObjectA}}, {{ConvertSidToStringSidA}} - filed as PUP-5736 * {{win32-eventlog}} has problems - https://github.com/puppetlabs/puppet-win32-ruby/blob/2.1.x-x64/ruby/lib/ruby/gems/2.1.0/gems/win32-eventlog-0.6.2/lib/win32/windows/functions.rb - see {{ClearEventLogA}}, {{LookupAccountSidA}}, {{OpenEventLogA}}, {{OpenBackupEventLogA}}, {{ReadEventLogA}}, {{RegConnectRegistryA}}, {{RegCreateKeyExA}}, {{RegisterEventSourceA}}, {{RegOpenKeyExA}}, {{RegQueryValueExA}}, {{RegSetValueExA}}, {{ReportEventA}}, {{CreateEventA}}, {{ExpandEnvironmentStringsA}}, {{FormatMessageA}}, {{LoadLibraryExA}}I have filed upstream tickets* https://github.com/djberg96/win32-security/issues/8* https://github.com/djberg96/win32-service/issues/32* https://github.com/djberg96/win32-process/issues/21* https://github.com/djberg96/win32-eventlog/issues/19
Add Comment
Jira (PUP-5736) Remove usage of win32-process gem
Title: Message Title Ethan Brown created an issue Puppet / PUP-5736 Remove usage of win32-process gem Issue Type: Task Assignee: Unassigned Created: 2016/01/21 1:29 PM Priority: Normal Reporter: Ethan Brown For starters, the affected parts appear to be: lib/puppet/feature/base.rb lib/puppet/util/windows/process.rb lib/puppet/util/pidlock.rb puppet/ext/windows/service/daemon.rb puppet/install.rb However, note that Win32::Process actually monkey patches the process object - https://github.com/djberg96/win32-process/blob/ffi/lib/win32/process.rb So we'll also want to look for calls to these functions as well: get_affinity getpriority
Jira (PUP-5560) Look at Improving Unicode for all Windows gems
Title: Message Title
Ethan Brown updated an issue
Puppet / PUP-5560
Look at Improving Unicode for all Windows gems
Change By:
Ethan Brown
h4. win32-security - PUP-5538 / PUP-5735 * {{win32-security}} has problems - https://github.com/puppetlabs/puppet-win32-ruby/blob/2.1.x-x64/ruby/lib/ruby/gems/2.1.0/gems/win32-security-0.2.5/lib/win32/security/windows/functions.rb - see {{ConvertSidToStringSidA}}, {{ConvertStringSidToSidA}}, {{LookupAccountNameA}}, {{LookupAccountSidA}} - this has mostly been addressed in * PUP-5538 , and an additional ticket for some the majority of the work + minor cleanup has opened as in PUP-5735 * {{ h4. win32-service }} has problems - * https://github.com/puppetlabs/puppet-win32-ruby/blob/2.1.x-x64/ruby/lib/ruby/gems/2.1.0/gems/win32-service-0.8.6/lib/win32/windows/functions.rb#L24-L75 - see {{CreateEventA}}, {{FormatMessageA}}, {{ChangeServiceConfigA}}, {{ChangeServiceConfig2A}}, {{CreateServiceA}}, {{EnumServicesStatusExA}}, {{GetServiceDisplayNameA}}, {{GetServiceKeyNameA}}, {{LookupPrivilegeValueA}}, {{OpenSCManagerA}}, {{OpenServiceA}}, {{QueryServiceConfigA}}, {{QueryServiceConfig2A}}, {{RegisterServiceCtrlHandlerExA}}, {{StartServiceA}}, {{StartServiceCtrlDispatcherA}} * {{ h4. win32-process }} has problems - PUP-5736* https://github.com/puppetlabs/puppet-win32-ruby/blob/2.1.x-x64/ruby/lib/ruby/gems/2.1.0/gems/win32-process-0.7.4/lib/win32/process/functions.rb - see {{GetModuleHandleA}}, {{GetVersionExA}}, {{GetVolumeInformationA}}, {{CreateJobObjectA}}, {{OpenJobObjectA}}, {{ConvertSidToStringSidA}} - filed as PUP-5736 * {{ h4. win32-eventlog }} has problems - * https://github.com/puppetlabs/puppet-win32-ruby/blob/2.1.x-x64/ruby/lib/ruby/gems/2.1.0/gems/win32-eventlog-0.6.2/lib/win32/windows/functions.rb - see {{ClearEventLogA}}, {{LookupAccountSidA}}, {{OpenEventLogA}}, {{OpenBackupEventLogA}}, {{ReadEventLogA}}, {{RegConnectRegistryA}}, {{RegCreateKeyExA}}, {{RegisterEventSourceA}}, {{RegOpenKeyExA}}, {{RegQueryValueExA}}, {{RegSetValueExA}}, {{ReportEventA}}, {{CreateEventA}}, {{ExpandEnvironmentStringsA}}, {{FormatMessageA}}, {{LoadLibraryExA}}I have filed upstream tickets* https://github.com/djberg96/win32-security/issues/8* https://github.com/djberg96/win32-service/issues/32* https://github.com/djberg96/win32-process/issues/21* https://github.com/djberg96/win32-eventlog/issues/19
Add Comment
Jira (PUP-5117) Inline file checksums
Title: Message Title Branan Riley updated an issue Puppet / PUP-5117 Inline file checksums Change By: Branan Riley Sprint: Client 2016- 02 01 - 10 27 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-4818) PUP-121 (relative namespacing) was never actually resolved in 3.x future parser
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-4818 PUP-121 (relative namespacing) was never actually resolved in 3.x future parser Change By: Henrik Lindberg Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-494) Interpolation of the empty variable %{} has changed
Title: Message Title
Henrik Lindberg updated an issue
Hiera / HI-494
Interpolation of the empty variable %{} has changed
This is bug, the output of the scope array is unintentional.
Change By:
Henrik Lindberg
Fix Version/s:
HI 3.0.6
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
--
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-5538) Puppet fails to convert Windows Unicode group or user names to sids
Title: Message Title Ethan Brown updated an issue Puppet / PUP-5538 Puppet fails to convert Windows Unicode group or user names to sids Change By: Ethan Brown Release Notes Summary: The handling of Unicode user and group names in Windows was previously deficient, and could present a number of errors when used in manifests, depending on the characters used in the name and the current local codepage. The user/group might fail to be created, might be created with the wrong characters, or might present failures on subsequent runs after initial creation. Using the SID of the user/group as a workaround could also fail. These issues have been corrected. Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-1292) Disk partition & mount point for Windows OS
Title: Message Title Dylan Ratcliffe commented on FACT-1292 Re: Disk partition & mount point for Windows OS Joshuatly Tee In the meantime I have created a simple module, if you have customer that wants it urgently feel free to point them to it: https://forge.puppetlabs.com/dylanratcliffe/disk_facts Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5591) undefined local variable or method `data' for Puppet::Provider::Package::Windows::Package:Class
Title: Message Title Fabio Vimercati commented on PUP-5591 Re: undefined local variable or method `data' for Puppet::Provider::Package::Windows::Package:Class Thanks for the updates Guys. Looking forward to the next release. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5117) Inline file checksums
Title: Message Title Branan Riley updated an issue Puppet / PUP-5117 Inline file checksums Change By: Branan Riley Scope Change Reason: bandwidth Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5117) Inline file checksums
Title: Message Title Branan Riley assigned an issue to Branan Riley Puppet / PUP-5117 Inline file checksums Change By: Branan Riley Assignee: Branan Riley Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5117) Inline file checksums
Title: Message Title Branan Riley updated an issue Puppet / PUP-5117 Inline file checksums Change By: Branan Riley Scope Change Category: Adopted Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-494) Interpolation of the empty variable %{} has changed
Title: Message Title
Henrik Lindberg updated an issue
Hiera / HI-494
Interpolation of the empty variable %{} has changed
Change By:
Henrik Lindberg
Sprint:
Language 2016-02- 24 (Burn FF) 10
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
--
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-5740) lookup does not honor environment.conf setting 'environment_data_provider = "function"'
Title: Message Title Sean Griffin created an issue Puppet / PUP-5740 lookup does not honor environment.conf setting 'environment_data_provider = "function"' Issue Type: Bug Assignee: Unassigned Created: 2016/01/21 5:17 PM Priority: Normal Reporter: Sean Griffin Setting environment_data_provider = "function" in $config_dir/environments/production/environment.conf should direct puppet lookup to find the value for a key in the hash returned by $config_dir/environments/production/lib/puppet/functions/environment/data.rb. Instead, puppet lookup prefers to return the value found by hiera, and will use data.rb only if the key is not found in hiera. To reproduce: 1. apply the attached catalog. 2. execute 'puppet lookup production_key'. 3. observe the value looked up is from hiera. [root@t17ic0vd14jnf0a
