Jira (PUP-1457) fail should be usable in a selector
Title: Message Title
Victor Engmark commented on PUP-1457
Re: fail should be usable in a selector
+1 Using the `case` statement means duplicating at least the variable name for every case. Which one is nicer:
case $foo { one: { $bar = x }
two: { $bar = y }
default: fail(Unknown foo: $ {foo}) } or: $bar = $foo ? { one: x, two: y, default: fail(Unknown foo: ${foo}
) }
The former has five tokens per case ('one:', '{', '$bar', '=', 'x'), while the latter has two ('one:', 'x,') or three depending on whether you count the comma separately. This scales linearly with the number of cases.
Add Comment
This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4280) Implement Catalog Diff
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-4280 Implement Catalog Diff Change By: Henrik Lindberg Scope Change Reason: Ticketmissing Scope Change Category: Found Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4280) Implement Catalog Diff
Title: Message Title Henrik Lindberg assigned an issue to Thomas Hallgren Puppet / PUP-4280 Implement Catalog Diff Change By: Henrik Lindberg Assignee: ThomasHallgren Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4118) Create a preview catalog indirection to compile a preview
Title: Message Title Henrik Lindberg assigned an issue to Henrik Lindberg Puppet / PUP-4118 Create a preview catalog indirection to compile a preview Change By: Henrik Lindberg Assignee: HenrikLindberg Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1322) fix nrepl.markdown so the repl example works when pasted
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-1322 fix nrepl.markdown so the repl example works when pasted Issue Type: Bug Assignee: Unassigned Created: 2015/03/23 7:46 AM Priority: Normal Reporter: Wyatt Alt Currently if you paste the import there's name clash between the garbage-collect! in storage.clj and the one in services.clj. In addition, there's no explanation of what configuration is. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
Jira (PUP-4280) Implement Catalog Diff
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-4280 Implement Catalog Diff Issue Type: Sub-task Assignee: Unassigned Created: 2015/03/23 7:56 AM Priority: Normal Reporter: Henrik Lindberg Implement a catalog diff utility that produces a diff in accordance with the catalog-delta json schema. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
Jira (FACT-864) Update facter#2.x acceptance config names to match puppet's
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-864 Update facter#2.x acceptance config names to match puppet's Change By: Kylo Ginsberg Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4259) puppet 0.9.1 2015-03-25 Release
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-4259 puppet 0.9.1 2015-03-25 Release Change By: Kylo Ginsberg Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-350) hiera 2.0.0 2015-03-25 Release
Title: Message Title Kylo Ginsberg updated an issue Hiera / HI-350 hiera 2.0.0 2015-03-25 Release Change By: Kylo Ginsberg Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4243) puppet 3.7.5 2015-03-24 Release
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-4243 puppet 3.7.5 2015-03-24 Release Change By: Kylo Ginsberg Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-366) Update hiera#master acceptance configs to match puppet#master's
Title: Message Title Kylo Ginsberg updated an issue Hiera / HI-366 Update hiera#master acceptance configs to match puppet#master's Change By: Kylo Ginsberg Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-855) Ensure acceptance tests pass
Title: Message Title Michael Smith assigned an issue to Michael Smith Facter / FACT-855 Ensure acceptance tests pass Change By: Michael Smith Assignee: MichaelSmith Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4123) Add infrastructure for a MigrationChecker
Title: Message Title Thomas Hallgren commented on PUP-4123 Re: Add infrastructure for a MigrationChecker PR-3738 merged to branch 3.8 at 905ddfb Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4232) add acceptance tests for lookup()
Title: Message Title Thomas Hallgren commented on PUP-4232 Re: add acceptance tests for lookup() Merged to master at 0f23eaa. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4201) Add support for structured logging
Title: Message Title Henrik Lindberg commented on PUP-4201 Re: Add support for structured logging Merged to 3.8 branch at: e4341c8 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4123) Add infrastructure for a MigrationChecker
Title: Message Title Thomas Hallgren assigned an issue to Unassigned Puppet / PUP-4123 Add infrastructure for a MigrationChecker Change By: Thomas Hallgren Assignee: ThomasHallgren Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2315) function call error message about mis-matched arguments is hard to understand
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-2315 function call error message about mis-matched arguments is hard to understand Change By: Henrik Lindberg Sprint: Language2015-03-04,Language2015-03-18 ,Language2015-04-01 Scope Change Reason: Capacity Takenoutofsprint-noworkplannedthissprint( was freeandwantedUXtobeabletocomment carriedover) Scope Change Category: Adopted Found Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4283) Update PMT to use only semantic_puppet versions (not SemVer)
Title: Message Title Anderson Mills created an issue Puppet / PUP-4283 Update PMT to use only semantic_puppet versions (not SemVer) Issue Type: Bug Affects Versions: PUP 4.0.0 Assignee: Unassigned Created: 2015/03/23 10:40 PM Fix Versions: PUP 4.x Priority: Normal Reporter: Anderson Mills Currently, PMT uses both the vendored Semantic library and the Puppet::SemVer module to check version numbers for modules. PMT should be only using the vendored Semantic library. Add Comment
Jira (PUP-4283) Update PMT to use only semantic_puppet versions (not SemVer)
Title: Message Title Anderson Mills commented on PUP-4283 Re: Update PMT to use only semantic_puppet versions (not SemVer) Steve Barlow Is this targeted at the correct version? Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1931) mount provider improvement when options property is not specified
Title: Message Title Melissa Stone updated an issue Puppet / PUP-1931 mount provider improvement when options property is not specified Change By: Melissa Stone Story Points: 2 5 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4086) File and line numbers often missing from errors
Title: Message Title Eric Thompson assigned an issue to Eric Thompson Puppet / PUP-4086 File and line numbers often missing from errors Change By: Eric Thompson Assignee: QA EricThompson Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4205) Puppet 4 lexer fails to parse multiple heredocs on the same line
Title: Message Title
Eric Thompson commented on PUP-4205
Re: Puppet 4 lexer fails to parse multiple heredocs on the same line
verified on rhel7 at SHA: c46c45a
[root@tddwf6n6v0g4vzw puppet]# puppet apply mult_heredocs.pp
Notice: Scope(Class[main]): {hello = world}
Notice: Compiled catalog for tddwf6n6v0g4vzw.delivery.puppetlabs.net in environment production in 0.39 seconds
Notice: Applied catalog in 0.01 seconds
[root@tddwf6n6v0g4vzw puppet]# cat mult_heredocs.pp
notice({ @(foo) = @(bar) })
hello
-foo
world
-bar
Jira (PUP-4205) Puppet 4 lexer fails to parse multiple heredocs on the same line
Title: Message Title Eric Thompson assigned an issue to Unassigned Puppet / PUP-4205 Puppet 4 lexer fails to parse multiple heredocs on the same line Change By: Eric Thompson Assignee: EricThompson Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-855) Ensure acceptance tests pass
Title: Message Title Kylo Ginsberg commented on FACT-855 Re: Ensure acceptance tests pass Re per-platform schema validation, I think https://github.com/puppetlabs/facter/blob/master/lib/tests/facts/schema.cc#L662-L677 does that, and that's what my comments above were based on. But I could be off-base so let's track that down. Re AIO pipelines, I'm not sure what the timeline is either, but the AIO focus is so heavily on initial AIO release right now that I don't think we should block this ticket on that decision / process. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4206) Fedora package naming convention doesn't match acceptance install assumptions
Title: Message Title Matthaus Owens updated an issue Puppet / PUP-4206 Fedora package naming convention doesn't match acceptance install assumptions Change By: Matthaus Owens Fix Version/s: PUP4.0.0 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4206) Fedora package naming convention doesn't match acceptance install assumptions
Title: Message Title Matthaus Owens updated an issue Puppet / PUP-4206 Fedora package naming convention doesn't match acceptance install assumptions Change By: Matthaus Owens Labels: AIO AIO_TechDebt Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4281) Autoload metaparams from modules.
Title: Message Title Henrik Lindberg commented on PUP-4281 Re: Autoload metaparams from modules. I am curious about the use cases - why is this needed? How would it be done today? Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4281) Autoload metaparams from modules.
Title: Message Title Henrik Lindberg assigned an issue to Dean Wilson Puppet / PUP-4281 Autoload metaparams from modules. Change By: Henrik Lindberg Assignee: DeanWilson Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-366) Update hiera#master acceptance configs to match puppet#master's
Title: Message Title Michael Smith commented on HI-366 Re: Update hiera#master acceptance configs to match puppet#master's Updating https://jenkins.puppetlabs.com/view/Hiera/view/Master/ Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-855) Ensure acceptance tests pass
Title: Message Title Michael Smith commented on FACT-855 Re: Ensure acceptance tests pass Not sure what the time-frame is on a second AIO pipeline to test against. Currently using the Facter/master Jenkins pipeline to verify acceptance tests. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4201) Add support for structured logging
Title: Message Title Eric Thompson commented on PUP-4201 Re: Add support for structured logging sounds like the probability could be medium/high but if existing tests should cover, then risk assessment is fine as-is, i'd say. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4201) Add support for structured logging
Title: Message Title Eric Thompson updated an issue Puppet / PUP-4201 Add support for structured logging Change By: Eric Thompson QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4206) Fedora package naming convention doesn't match acceptance install assumptions
Title: Message Title Kylo Ginsberg commented on PUP-4206 Re: Fedora package naming convention doesn't match acceptance install assumptions Re-opening for if/when we decide to remove the 'f'. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4123) Add infrastructure for a MigrationChecker
Title: Message Title Thomas Hallgren assigned an issue to Thomas Hallgren Puppet / PUP-4123 Add infrastructure for a MigrationChecker Change By: Thomas Hallgren Assignee: ThomasHallgren Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-337) Hiera Backends should distinguish key with null value from key not found
Title: Message Title Henrik Lindberg commented on HI-337 Re: Hiera Backends should distinguish key with null value from key not found Nicholas Fagerlund I think it is a good strategy to describe the Hiera 2.0 API for the backend and link back to the 1.x documentation for the method having the 1.x signature. The 2.x. signature is described in pre-docs. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1154) Close all resolved tickets and release version in Jira
Title: Message Title Wyatt Alt assigned an issue to Wyatt Alt PuppetDB / PDB-1154 Close all resolved tickets and release version in Jira Change By: Wyatt Alt Resolution: Fixed Assignee: WyattAlt Status: ReadyforEngineering Closed Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4090) Zypper provider doesn't work correctly on SLES 10.4 with install_options set
Title: Message Title Melissa Stone assigned an issue to Melissa Stone Puppet / PUP-4090 Zypper provider doesn't work correctly on SLES 10.4 with install_options set Change By: Melissa Stone Assignee: MelissaStone Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1305) Update install from source docs for PuppetDB 2.3.0 with AIO
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-1305 Update install from source docs for PuppetDB 2.3.0 with AIO Change By: Wyatt Alt Fix Version/s: PDB2.3.0 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-337) Hiera Backends should distinguish key with null value from key not found
Title: Message Title Henrik Lindberg commented on HI-337 Re: Hiera Backends should distinguish key with null value from key not found Nicholas Fagerlund description and predocs the hiera/lookup-2.x-api.md document have both been updated. (Thomas Hallgren, you are off the hook, but please add to, or change the description/predocs if there was something I missed. Nick, it started with just one small change in the backend, but then more things were added to the 2.0 API. Naturally a 2.0 compliant backend needs to implement all of the changes. The hiera implementation will detect if it is a new (2.0) or old (1.0) backend based on the signature of the backend's lookup method (number of parameters it takes). Not sure how much documentation we have regarding how to implement a backend - happy to review it (or help modifying it). Let us know. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-337) Hiera Backends should distinguish key with null value from key not found
Title: Message Title Nicholas Fagerlund commented on HI-337 Re: Hiera Backends should distinguish key with null value from key not found Henrik Lindberg Oh, this signature detection thing is completely new to us. Was that described anywhere? My understanding was that if you programmed to accommodate parts of the new behavior, you got the new behavior a la carte. If the lookup method signature takes four arguments, does Hiera 2's behavior exactly match what we describe here? https://docs.puppetlabs.com/hiera/1/custom_backends.html Or is it a slightly modified version of the 1.x api? If it's exact, we should be able to just add a note to the top of the custom backends page, linking back to the previous version... Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-337) Hiera Backends should distinguish key with null value from key not found
Title: Message Title Nicholas Fagerlund commented on HI-337 Re: Hiera Backends should distinguish key with null value from key not found Henrik Lindberg Is raise an exception the correct way to describe what's happening here? It sounds like that's not quite right. Is there another way to describe this? What happens if the backend author uses `raise` instead? (I assume it blows up) Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1127) remove experimental endpoint
Title: Message Title Wyatt Alt assigned an issue to Wyatt Alt PuppetDB / PDB-1127 remove experimental endpoint Change By: Wyatt Alt Assignee: WyattAlt Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1127) remove experimental endpoint
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-1127 remove experimental endpoint Change By: Wyatt Alt Sprint: PuppetDB2015-03-25 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-337) Hiera Backends should distinguish key with null value from key not found
Title: Message Title Henrik Lindberg commented on HI-337 Re: Hiera Backends should distinguish key with null value from key not found Nicholas Fagerlund yes, doh... will fix my bad comments Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4090) Zypper provider doesn't work correctly on SLES 10.4 with install_options set
Title: Message Title Melissa Stone commented on PUP-4090 Re: Zypper provider doesn't work correctly on SLES 10.4 with install_options set I've updated this with a pull request that I believe addresses the need to use the `--no-gpg-check` option, while both maintaining previous functionality, and fixing up how it was failing previously. Peter Huene may be interested in this, since he previously did some work on this. Note, the scenario I posted about above, I haven't been able to find a good solution to. If a user wants to install something that isn't a conventional package (like a langauge, or srcpackage), they need to specify `- type srcpackage`, or something along those lines. The problem that I ran into, and didn't put in much time trying to diagnose, was that specifying `install_options = [ ' type srcpackage' ]` would give us `zypper install -type srcpackage --name zoo`. The double quotes break the zypper command. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-337) Hiera Backends should distinguish key with null value from key not found
Title: Message Title Henrik Lindberg commented on HI-337 Re: Hiera Backends should distinguish key with null value from key not found I think it is better to say throw the symbol :not_found since that is what the ruby could will say throw :not_found - the ruby term is throwing an exception (as opposed to raising an error), but better be explicit about what is thrown (the symbol :not_found. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-337) Hiera Backends should distinguish key with null value from key not found
Title: Message Title Henrik Lindberg commented on HI-337 Re: Hiera Backends should distinguish key with null value from key not found Nicholas Fagerlund the signature detection is based on the signature of the backend's lookup method. It is described in the predocs. The pre-docs does not say though that hiera 1.0 backend semantics are retained for all the duties performed by a backend. Note that a lot of the behavior of hiera is implemented in the backends (recursion guards, nil value vs. not found etc.). Hiera 2.0 creates a wrapper around 1.x backends and that wrapper adapts the old behavior. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-337) Hiera Backends should distinguish key with null value from key not found
Title: Message Title Nicholas Fagerlund commented on HI-337 Re: Hiera Backends should distinguish key with null value from key not found Henrik Lindberg You mean throw :no_such_key, right? Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1628) Add mount provider for AIX
Title: Message Title Kylo Ginsberg commented on PUP-1628 Re: Add mount provider for AIX No more in 3.7.5 because we're planning to release tomorrow/Wed. But it's fair game for 3.8.0 in my book. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1323) Make producer_timestamp a required field
Title: Message Title Russell Mull created an issue PuppetDB / PDB-1323 Make producer_timestamp a required field Issue Type: Task Assignee: Unassigned Created: 2015/03/23 3:19 PM Priority: Normal Reporter: Russell Mull The producer_timestamp field of catalogs and factsets is the basis of conflict resolution for HA, so we need to make sure it's there. It's currently always provided by the master (via our terminus), but we should change the API to make it required. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
Jira (PDB-1323) Make producer_timestamp a required field
Title: Message Title Russell Mull assigned an issue to Russell Mull PuppetDB / PDB-1323 Make producer_timestamp a required field Change By: Russell Mull Assignee: RussellMull Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-337) Hiera Backends should distinguish key with null value from key not found
Title: Message Title
Henrik Lindberg updated an issue
Hiera / HI-337
Hiera Backends should distinguish key with null value from key not found
Change By:
Henrik Lindberg
UPDATEThehierabackendAPIforHiera2.0defines(amongotherthingssuchasacceptingarecursionguard),thatthebackendshouldraiseanexceptionastheresultofalookupthatproducesnoresultinsteadofreturningnil.Thistodifferentiatebetweentheresultofanexplicitnilandnotfound. A backendthatcomplieswiththenewAPIshoulddothiswhentheresultis'notfound':{code}throw(:no_such_key){code}NotethatHiera2.0isbackwardscompatiblewithexistingbackends-olderbackendsthatreturnnilisinterpretedasnotfound,vs.2.0compliantbackends(i.e.theyamlandjsonbackendsdeliveredwith hiera 2.0)thatcanreturnnil.ORIGINALAhiera backendwillreturnnilwhennovalueisfoundforagivenkey.Itwilldothesameifthekeyisfoundbutassociatedwithanilvalue.Thismakesitimpossibletodistinguishbetweenthetwocases.Apossiblesolutionforthiswouldbeifthebackendwouldthrowanexceptionwhenthekeydoesnotexist.Hieracouldthencatchthisexceptionand,whennobackendsfindthegivenkey,resorttothedefaultvalue(orextrashash).Ifanilvalueisfoundhoweverit'streatedasanyothervalueandthedefaulthandlingwouldnotkickin.Thisenablesthecallertoprovideadefaultvaluethatactsasaplaceholderfor'notfound'andthencheckthereturnedvalue.Ifnilisreturned,thennilwasfound.Ifthegivendefaultisreturned,thentherewasnomatchforthekey.Onethingtoconsiderwiththisapproachiswhatimpactvalidnilvalueshaveonthe'array'lookup.Aretheylegalatall?(currentlyonlyStringandArrayareallowed),andifso,shouldtheresultingarraybecompactedattheend?
Add Comment
This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
Jira (FACT-855) Ensure acceptance tests pass
Title: Message Title Michael Smith commented on FACT-855 Re: Ensure acceptance tests pass Kylo Ginsberg I think your description of the new schema test is a little confused. The schema test in unit tests populates all facts, then compares against the schema. Running it on different machines won't make a difference. We probably still want a separate test that confirms that actual runs on a machine emit the facts we expect, as specified in the schema. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4133) Future parser error when interpolating name segment starting with underscore
Title: Message Title
Eric Thompson commented on PUP-4133
Re: Future parser error when interpolating name segment starting with underscore
verified on rhel7 at SHA: c46c45a
[root@tddwf6n6v0g4vzw puppet]# cat leading_underscore.pp
class bar ($foo) {
$_foo = $foo
notify {Name of resource ${bar::_foo}:
message = 'something witty here'
}
}
class {'bar':
foo = 'one',
}
[root@tddwf6n6v0g4vzw puppet]# puppet apply leading_underscore.pp
Jira (FACT-864) Update facter#2.x acceptance config names to match puppet's
Title: Message Title Michael Smith commented on FACT-864 Re: Update facter#2.x acceptance config names to match puppet's Updating https://jenkins.puppetlabs.com/view/Facter/view/2.x%20Classic/ Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4281) Autoload metaparams from modules.
Title: Message Title Dean Wilson created an issue Puppet / PUP-4281 Autoload metaparams from modules. Issue Type: New Feature Assignee: Unassigned Created: 2015/03/23 9:24 AM Priority: Normal Reporter: Dean Wilson It would be very helpful if the puppet master/server would autoload metaparams from inside a module. This would allow them to be distributed via the forge. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
Jira (PUP-4133) Future parser error when interpolating name segment starting with underscore
Title: Message Title Eric Thompson assigned an issue to QA Puppet / PUP-4133 Future parser error when interpolating name segment starting with underscore Change By: Eric Thompson Assignee: EricThompson QA Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4086) File and line numbers often missing from errors
Title: Message Title Eric Thompson assigned an issue to QA Puppet / PUP-4086 File and line numbers often missing from errors Change By: Eric Thompson Assignee: QA Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4205) Puppet 4 lexer fails to parse multiple heredocs on the same line
Title: Message Title Eric Thompson assigned an issue to Eric Thompson Puppet / PUP-4205 Puppet 4 lexer fails to parse multiple heredocs on the same line Change By: Eric Thompson Assignee: QA EricThompson Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4086) File and line numbers often missing from errors
Title: Message Title Eric Thompson commented on PUP-4086 Re: File and line numbers often missing from errors verified on rhel7 at SHA: c46c45a [root@tddwf6n6v0g4vzw ~]# puppet module install puppetlabs/stdlib Notice: Preparing to install into /etc/puppetlabs/code/modules ... Notice: Created target directory /etc/puppetlabs/code/modules Notice: Downloading from https://forgeapi.puppetlabs.com ... Notice: Installing -- do not interrupt ... /etc/puppetlabs/code/modules └── puppetlabs-stdlib (v4.5.1) [root@tddwf6n6v0g4vzw ~]# puppet apply -e 'notice pick($empty, )' Error: Evaluation Error: Error while evaluating a Function Call, pick(): must receive at least one non empty value at line 1:8 on node tddwf6n6v0g4vzw.delivery.puppetlabs.net Error: Evaluation
Jira (PUP-4086) File and line numbers often missing from errors
Title: Message Title Eric Thompson assigned an issue to Unassigned Puppet / PUP-4086 File and line numbers often missing from errors Change By: Eric Thompson Assignee: EricThompson Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4133) Future parser error when interpolating name segment starting with underscore
Title: Message Title Eric Thompson assigned an issue to Eric Thompson Puppet / PUP-4133 Future parser error when interpolating name segment starting with underscore Change By: Eric Thompson Assignee: QA EricThompson Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4205) Puppet 4 lexer fails to parse multiple heredocs on the same line
Title: Message Title Eric Thompson assigned an issue to Eric Thompson Puppet / PUP-4205 Puppet 4 lexer fails to parse multiple heredocs on the same line Change By: Eric Thompson Assignee: EricThompson Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4205) Puppet 4 lexer fails to parse multiple heredocs on the same line
Title: Message Title
Eric Thompson commented on PUP-4205
Re: Puppet 4 lexer fails to parse multiple heredocs on the same line
verified on windows2012r2-rubyx64 at SHA: c46c45a
$ cmd /c puppet apply mult_heredocs.pp
Notice: Scope(Class[main]): {hello = world}
Notice: Compiled catalog for lkocn4uy71ehg8m.delivery.puppetlabs.net in environment production in 0.44 seconds
Notice: Applied catalog in 0.03 seconds
Add Comment
This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
--
You received this message because you are subscribed to the Google Groups
Jira (PUP-4133) Future parser error when interpolating name segment starting with underscore
Title: Message Title
Eric Thompson updated an issue
Puppet / PUP-4133
Future parser error when interpolating name segment starting with underscore
Change By:
Eric Thompson
Variablesstartingwithunderscorearestillsupposedtobevalidwiththefutureparser,butinterpolationofthemdoesn'tworkifthey'reaccessedusingtheirqualifiedvariablename.eg{code}$catleading_underscore.ppclassbar($foo){$_foo=$foonotify{Nameofresource${bar::_foo}:message='somethingwittyhere'}}class{'bar':foo='one',}$puppetapply--parser=futureleading_underscore.ppError:Couldnotparseforenvironmentproduction:Illegalfullyqualifiednameinfile/home/alex/github/test/leading_underscore.ppatline3:36onnodealex-virtualbox.example.comError:Couldnotparseforenvironmentproduction:Illegalfullyqualifiednameinfile/home/alex/github/test/leading_underscore.ppatline3:36onnodealex-virtualbox.example.com{code}IdiscussedthisonIRCand[~richard]cameupwiththefollowingexamplethatprobablydemonstratestheissuemoreclearlythanmine.{code}$catleading_underscore.ppclassbar{$_foo=one}includebarnotice(${bar::_foo})$puppetapply--parser=futureleading_underscore.ppError:Couldnotparseforenvironmentproduction:Illegalfullyqualifiednameinfile/Users/richardc/src/leading_underscore.ppatline10:18onnodesocks.localError:Couldnotparseforenvironmentproduction:Illegalfullyqualifiednameinfile/Users/richardc/src/leading_underscore.ppatline10:18onnodesocks.local$catleading_underscoreworking.ppclassbar{$_foo=one}includebarnotice($bar::_foo)$puppetapply--parser=futureleading_underscoreworking.ppNotice:Scope(Class[main]):oneNotice:Compiledcatalogforsocks.localinenvironmentproductionin0.51secondsNotice:Finishedcatalogrunin0.03seconds{code}Thanks,Alex riskassessment:medium(FRonlyfornow)probability:low(variablesstartingwithunderscores)severity:medium(workaroundsexist)testlayer:
Add Comment
This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
Jira (PUP-4133) Future parser error when interpolating name segment starting with underscore
Title: Message Title Eric Thompson updated an issue Puppet / PUP-4133 Future parser error when interpolating name segment starting with underscore Change By: Eric Thompson QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4133) Future parser error when interpolating name segment starting with underscore
Title: Message Title Eric Thompson updated an issue Puppet / PUP-4133 Future parser error when interpolating name segment starting with underscore Change By: Eric Thompson QA Contact: KurtWall EricThompson Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4259) puppet 0.9.1 2015-03-25 Release
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-4259 puppet 0.9.1 2015-03-25 Release Change By: Kylo Ginsberg Labels: AIO Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4086) File and line numbers often missing from errors
Title: Message Title Eric Thompson commented on PUP-4086 Re: File and line numbers often missing from errors verified on windows2012r2-rubyx64 at SHA: c46c45a Administrator@lkocn4uy71ehg8m /opt/puppet-git-repos/puppet $ puppet apply -e 'notice pick($empty, )' C:\cygwin64\bin\ruby.exe: No such file or directory -- /usr/bin/puppet (LoadError) Administrator@lkocn4uy71ehg8m /opt/puppet-git-repos/puppet $ cmd /c puppet apply -e 'notice pick($empty, )' Error: Evaluation Error: Error while evaluating a Function Call, pick(): must receive at least one non empty value at line 1:8 on node lkocn4uy71ehg8m.delivery.puppetlabs.net Error: Evaluation Error: Error while evaluating a Function Call, pick(): must receive at least one non empty value at line 1:8 on node lkocn4uy71ehg8m.delivery.puppetlabs.net
Jira (PUP-4133) Future parser error when interpolating name segment starting with underscore
Title: Message Title
Eric Thompson updated an issue
Puppet / PUP-4133
Future parser error when interpolating name segment starting with underscore
Change By:
Eric Thompson
Variablesstartingwithunderscorearestillsupposedtobevalidwiththefutureparser,butinterpolationofthemdoesn'tworkifthey'reaccessedusingtheirqualifiedvariablename.eg{code}$catleading_underscore.ppclassbar($foo){$_foo=$foonotify{Nameofresource${bar::_foo}:message='somethingwittyhere'}}class{'bar':foo='one',}$puppetapply--parser=futureleading_underscore.ppError:Couldnotparseforenvironmentproduction:Illegalfullyqualifiednameinfile/home/alex/github/test/leading_underscore.ppatline3:36onnodealex-virtualbox.example.comError:Couldnotparseforenvironmentproduction:Illegalfullyqualifiednameinfile/home/alex/github/test/leading_underscore.ppatline3:36onnodealex-virtualbox.example.com{code}IdiscussedthisonIRCand[~richard]cameupwiththefollowingexamplethatprobablydemonstratestheissuemoreclearlythanmine.{code}$catleading_underscore.ppclassbar{$_foo=one}includebarnotice(${bar::_foo})$puppetapply--parser=futureleading_underscore.ppError:Couldnotparseforenvironmentproduction:Illegalfullyqualifiednameinfile/Users/richardc/src/leading_underscore.ppatline10:18onnodesocks.localError:Couldnotparseforenvironmentproduction:Illegalfullyqualifiednameinfile/Users/richardc/src/leading_underscore.ppatline10:18onnodesocks.local$catleading_underscoreworking.ppclassbar{$_foo=one}includebarnotice($bar::_foo)$puppetapply--parser=futureleading_underscoreworking.ppNotice:Scope(Class[main]):oneNotice:Compiledcatalogforsocks.localinenvironmentproductionin0.51secondsNotice:Finishedcatalogrunin0.03seconds{code}Thanks,Alexriskassessment:medium(FRonlyfornow)probability:low(variablesstartingwithunderscores)severity:medium(workaroundsexist)testlayer: unit(https://github.com/puppetlabs/puppet/blob/dda2430457cd06c3381f02163dc9c15925b4bff7/spec/unit/pops/parser/lexer2_spec.rb#L230-L236)
Add Comment
This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
Jira (PUP-4133) Future parser error when interpolating name segment starting with underscore
Title: Message Title Eric Thompson commented on PUP-4133 Re: Future parser error when interpolating name segment starting with underscore verified on windows2012r2-rubyx64 at SHA: c46c45a Administrator@lkocn4uy71ehg8m /opt/puppet-git-repos/puppet $ cmd /c puppet apply leading_underscore.pp Notice: Scope(Class[main]): one Notice: Compiled catalog for lkocn4uy71ehg8m.delivery.puppetlabs.net in environment production in 0.66 seconds Notice: Applied catalog in 0.02 seconds Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
Jira (PUP-4282) numeric comparison error
Title: Message Title
Larry Orcutt created an issue
Puppet / PUP-4282
numeric comparison error
Issue Type:
Bug
Affects Versions:
PUP 3.7.4
Assignee:
Unassigned
Components:
Puppet Server
Created:
2015/03/23 10:45 AM
Environment:
Linux RHEL/Centos 6
Priority:
Normal
Reporter:
Larry Orcutt
Test code:
{ $num50 = 5.0 $x = $::memorysize_mb * 1000 if is_float($x) { notify {x is a float:}
} if is_float($num50) { notify {num50 is a float:}
} #if ( $::x = $num50 ) #{ notify {$x greater or equal to $num50:}
} #else #{ notify {$x less than than $num50:}
} }
Produces Notice: x is a float Notice: num50 is a float
OK.
Uncomment the comparison lines and I get an error:
Jira (PUP-4281) Autoload metaparams from modules.
Title: Message Title Dean Wilson commented on PUP-4281 Re: Autoload metaparams from modules. I currently maintain some metaparams that I patch in in to puppet/type.rb and then build local packages with my changes. I'd like to be able to distribute them inside of modules instead, especially with the upcoming all in one packages. One example of a local metaparam is from https://groups.google.com/forum/#!topic/puppet-dev/SATMNVUTPw4 After a conversation with Hunnar in #puppet-dev there are a few possible ways around this missing feature, such as using a combination of facts, features and util libs to trigger a load or creating (and adding to the catalog) a fake type but this is a large amount of hacky boilerplate to address the missing functionality. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4281) Autoload metaparams from modules.
Title: Message Title Dean Wilson assigned an issue to Henrik Lindberg Puppet / PUP-4281 Autoload metaparams from modules. Change By: Dean Wilson Assignee: DeanWilson HenrikLindberg Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4205) Puppet 4 lexer fails to parse multiple heredocs on the same line
Title: Message Title
Eric Thompson updated an issue
Puppet / PUP-4205
Puppet 4 lexer fails to parse multiple heredocs on the same line
Change By:
Eric Thompson
Parsingthismanifest:{code}notice({@(foo)=@(bar)})hello-fooworld-bar{code}Resultsin:{code}$puppetapplyfoo.ppError:Couldnotparseforenvironmentproduction:undefinedlocalvariableormethod`lexing_context'for#Puppet::Pops::Parser::Lexer2:0x007faadd1551a0onnodepeterhu-osx{code}Expectedresults:{code}$puppetapplyfoo.ppNotice:Scope(Class[main]):{hello=world}Notice:Compiledcatalogforpeterhu-osxinenvironmentproductionin1.18secondsNotice:Appliedcatalogin0.08seconds{code} QAriskassessment:medium(FRonlyfornow)probability:low(multipleheredocsonsameline)severity:medium(workaroundsexist)testlayer:
Add Comment
This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4205) Puppet 4 lexer fails to parse multiple heredocs on the same line
Title: Message Title
Eric Thompson updated an issue
Puppet / PUP-4205
Puppet 4 lexer fails to parse multiple heredocs on the same line
Change By:
Eric Thompson
Parsingthismanifest:{code}notice({@(foo)=@(bar)})hello-fooworld-bar{code}Resultsin:{code}$puppetapplyfoo.ppError:Couldnotparseforenvironmentproduction:undefinedlocalvariableormethod`lexing_context'for#Puppet::Pops::Parser::Lexer2:0x007faadd1551a0onnodepeterhu-osx{code}Expectedresults:{code}$puppetapplyfoo.ppNotice:Scope(Class[main]):{hello=world}Notice:Compiledcatalogforpeterhu-osxinenvironmentproductionin1.18secondsNotice:Appliedcatalogin0.08seconds{code}QAriskassessment:medium(FRonlyfornow)probability:low(multipleheredocsonsameline)severity:medium(workaroundsexist)testlayer: unit(https://github.com/puppetlabs/puppet/blob/26ad83f62e1ff1d1df51591f1c2c9b555484d3e0/spec/unit/pops/parser/parse_heredoc_spec.rb#L117-L136)
Add Comment
This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4205) Puppet 4 lexer fails to parse multiple heredocs on the same line
Title: Message Title Eric Thompson updated an issue Puppet / PUP-4205 Puppet 4 lexer fails to parse multiple heredocs on the same line Change By: Eric Thompson QA Contact: EricThompson Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4205) Puppet 4 lexer fails to parse multiple heredocs on the same line
Title: Message Title Eric Thompson updated an issue Puppet / PUP-4205 Puppet 4 lexer fails to parse multiple heredocs on the same line Change By: Eric Thompson QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4133) Future parser error when interpolating name segment starting with underscore
Title: Message Title Eric Thompson assigned an issue to Eric Thompson Puppet / PUP-4133 Future parser error when interpolating name segment starting with underscore Change By: Eric Thompson Assignee: QA EricThompson Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-865) Native facter lost the output from stderr in external (and custom?) facts
Title: Message Title Michael Smith created an issue Facter / FACT-865 Native facter lost the output from stderr in external (and custom?) facts Issue Type: Bug Affects Versions: FACT 3.0.0 Assignee: Eric Sorenson Created: 2015/03/23 3:47 PM Fix Versions: FACT 3.0.0 Priority: Normal Reporter: Michael Smith Fix output, and restore the original behavior from the acceptance test runs_external_facts_once.rb. We don't want to just dump output like facter does; this seems to make sense as a log warning. Add Comment
Jira (PDB-1325) PR (1317): (BKR-147) add Gemfile setting for BEAKER_VERSION for puppet, ... - anodelman
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-1325 PR (1317): (BKR-147) add Gemfile setting for BEAKER_VERSION for puppet, ... - anodelman Issue Type: Task Assignee: Unassigned Created: 2015/03/23 3:53 PM Labels: github Priority: Normal Reporter: gepetto-bot (BKR-147) add Gemfile setting for BEAKER_VERSION for puppet, ... Author: alice nodelman al...@puppetlabs.com Company: Puppet Labs Github ID: anodelman Pull Request 1317 Discussion Pull Request 1317 File Diff Pull Request Description ... puppetdb, etc add support for BEAKER_VERSION
Jira (PDB-1324) PR (1316): (BKR-147) add Gemfile setting for BEAKER_VERSION for puppet, ... - anodelman
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-1324 PR (1316): (BKR-147) add Gemfile setting for BEAKER_VERSION for puppet, ... - anodelman Issue Type: Task Assignee: Unassigned Created: 2015/03/23 3:50 PM Labels: github Priority: Normal Reporter: gepetto-bot (BKR-147) add Gemfile setting for BEAKER_VERSION for puppet, ... Author: alice nodelman al...@puppetlabs.com Company: Puppet Labs Github ID: anodelman Pull Request 1316 Discussion Pull Request 1316 File Diff Pull Request Description ... puppetdb, etc add support for BEAKER_VERSION
Jira (PDB-1324) PR (1316): (BKR-147) add Gemfile setting for BEAKER_VERSION for puppet, ... - anodelman
Title: Message Title gepetto-bot commented on PDB-1324 Re: PR (1316): (BKR-147) add Gemfile setting for BEAKER_VERSION for puppet, ... - anodelman pljenkinsro commented: Can one of the admins verify this patch? Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-282) hiera binary with `-i nodename.domain.com` fails under puppet 3
Title: Message Title Kjetil Torgrim Homme commented on HI-282 Re: hiera binary with `-i nodename.domain.com` fails under puppet 3 the original patch + changing terminus_class to :puppetdb instead of :rest works for me. perhaps it would be better to make a new option since this is a different API than the inventory service. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4250) Prepare long form release notes and short form release story
Title: Message Title Nicholas Fagerlund updated an issue Puppet / PUP-4250 Prepare long form release notes and short form release story Some edited ticket summaries, no tix added or removed. Change By: Nicholas Fagerlund Attachment: puppet3.7.5mar23.txt Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1325) PR (1317): (BKR-147) add Gemfile setting for BEAKER_VERSION for puppet, ... - anodelman
Title: Message Title gepetto-bot commented on PDB-1325 Re: PR (1317): (BKR-147) add Gemfile setting for BEAKER_VERSION for puppet, ... - anodelman wkalt commented: @pljenkinsro okay to test Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4282) numeric comparison error
Title: Message Title Christopher Price commented on PUP-4282 Re: numeric comparison error Henrik Lindberg any ideas? Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4282) numeric comparison error
Title: Message Title Christopher Price updated an issue Puppet / PUP-4282 numeric comparison error Change By: Christopher Price Scrum Team: PuppetServer Language Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4282) numeric comparison error
Title: Message Title Christopher Price updated an issue Puppet / PUP-4282 numeric comparison error Change By: Christopher Price Component/s: PuppetServer Component/s: Language Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4282) numeric comparison error
Title: Message Title Henrik Lindberg assigned an issue to Larry Orcutt Puppet / PUP-4282 numeric comparison error Change By: Henrik Lindberg Assignee: LarryOrcutt Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4282) numeric comparison error
Title: Message Title
Henrik Lindberg commented on PUP-4282
Re: numeric comparison error
First, I assume that 'parser = future' or the ModelLabelProvider would never have been involved. Secondly, there seems to be something wrong with the error message production itself, it seems to output the label provider, not the value that is being compared. (Will look into that asap).
I tried this on what will be 3.7.5 like this:
$num50 = 5.0
$x = $::memorysize_mb * 1000
if $x =~ Float {
notice x is a float
}
if $num50 =~ Float {
notice num50 is a float
}
if $x = $num50 {
notice $x is greater or equal to $num50
Jira (HI-348) Enable deep-merge options to be passed in lookup
Title: Message Title Nicholas Fagerlund commented on HI-348 Re: Enable deep-merge options to be passed in lookup Is there any user-facing interface to this, using the Puppet functions or the hiera command line? Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1325) PR (1317): (BKR-147) add Gemfile setting for BEAKER_VERSION for puppet, ... - anodelman
Title: Message Title gepetto-bot commented on PDB-1325 Re: PR (1317): (BKR-147) add Gemfile setting for BEAKER_VERSION for puppet, ... - anodelman pljenkinsro commented: Can one of the admins verify this patch? Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-348) Enable deep-merge options to be passed in lookup
Title: Message Title Henrik Lindberg commented on HI-348 Re: Enable deep-merge options to be passed in lookup The user facing part of this is in the new lookup function in Puppet 4.0. The UI for hiera itself (hiera command and hiera functions in puppet) are not affected - they continue to work as before. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4282) numeric comparison error
Title: Message Title
Henrik Lindberg commented on PUP-4282
Re: numeric comparison error
Please also check the content of the file lib/puppet/pops/issues.rb, the error in question looks like this on master:
COMPARISON_NOT_POSSIBLE = hard_issue :COMPARISON_NOT_POSSIBLE, :operator, :left_value, :right_value, :detail do
Comparison of: #{label(left_value)} #{operator} #{label(right_value)}, is not possible. Caused by '#{detail}'.
end
and the reported problem would probably occur if the first interpolation has been tampered with to read something else. I cannot find any commits between the old way of reporting the error (which was):
fail(Comparison of #{left.class} #{o.operator} #{right.class} is not possible. Caused by #{e.message}., o, scope)
and when a switch was made to use the new issue reporting system in commit f61cdde810eccd3a08a8206b7c6650713a9df5f0 and it is unchanged since then afaict.
It is thus quite surprising. Please try on a fresh copy of puppet to ensure puppet source has not been tampered with. And if possible try this on 3.7.5 (stable branch at the moment, very soon to be released).
Add Comment
