Jira (PUP-2904) Make string/symbol use consistent i new function API
Title: Message Title Andy Parker updated an issue Puppet / PUP-2904 Make string/symbol use consistent i new function API Change By: Andy Parker Sprint: Week2014-7-23to2014-8-6 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-2862) Validate that default value expression for param does not define variable
Title: Message Title Andy Parker updated an issue Puppet / PUP-2862 Validate that default value _expression_ for param does not define variable Change By: Andy Parker Sprint: Week2014-7-23to2014-8-6 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-2858) remove --evaluator current switch for future parser
Title: Message Title Andy Parker updated an issue Puppet / PUP-2858 remove --evaluator current switch for future parser Change By: Andy Parker Sprint: Week2014- 7 6 - 9 25 to2014-7- 23 9 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-2858) remove --evaluator current switch for future parser
Title: Message Title Andy Parker assigned an issue to Andy Parker Puppet / PUP-2858 remove --evaluator current switch for future parser Change By: Andy Parker Assignee: AndyParker Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-2910) Need ability to remove all unmanaged resources
Title: Message Title Andy Parker assigned an issue to Jay Wallace Jay Wallace, could you provide some information about this request? At the moment this is far to broad for us to take any action on. Puppet / PUP-2910 Need ability to remove all unmanaged resources Change By: Andy Parker Assignee: JayWallace Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-2909) Incorporate linting and static verification with rubocop
Title: Message Title Andy Parker updated an issue Puppet / PUP-2909 Incorporate linting and static verification with rubocop Change By: Andy Parker Affects Version/s: 4.x Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-2909) Incorporate linting and static verification with rubocop
Title: Message Title Andy Parker commented on an issue Re: Incorporate linting and static verification with rubocop Rahul Gopinath, do you have any ideas about what rules it should enforce or when it should enforce those rules? Add Comment Puppet / PUP-2909 Incorporate linting and static verification with rubocop Enable Rubocop static verification and linting in puppet This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-2909) Incorporate linting and static verification with rubocop
Title: Message Title Andy Parker assigned an issue to Rahul Gopinath Puppet / PUP-2909 Incorporate linting and static verification with rubocop Change By: Andy Parker Assignee: RahulGopinath Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-2858) remove --evaluator current switch for future parser
Title: Message Title Andy Parker commented on an issue Re: remove --evaluator current switch for future parser Merged into master in 1d218c. This removes the --evaluator current option and any associated code. It also removes the --biff setting, which was not really used at all. Add Comment Puppet / PUP-2858 remove --evaluator current switch for future parser In 3.7.0 we should remove the ability to fall back to --evaluator current as we do not want to maintain the hybrid mode (it is not how Puppet 4.0 will work), and we have not been running any tests as more and more has shifted over to the new evaluator. Removing the switch also means much of the hybrid code can be removed. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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
Jira (PUP-2858) remove --evaluator current switch for future parser
Title: Message Title Andy Parker updated an issue Puppet / PUP-2858 remove --evaluator current switch for future parser Change By: Andy Parker Component/s: DOCS Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-2831) Puppet does not work with RGen 0.7.0
Title: Message Title Andy Parker updated an issue Puppet / PUP-2831 Puppet does not work with RGen 0.7.0 Change By: Andy Parker Sprint: Week2014- 7 6 - 9 25 to2014-7- 23 9 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-2831) Puppet does not work with RGen 0.7.0
Title: Message Title Andy Parker commented on an issue Re: Puppet does not work with RGen 0.7.0 Merged into master in eadb59 Add Comment Puppet / PUP-2831 Puppet does not work with RGen 0.7.0 As discovered in PUP-2755, strange things happen when using RGen 0.7.0 with puppet. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-2914) Update packages to use RGen 0.7.0
Title: Message Title Andy Parker created an issue Puppet / PUP-2914 Update packages to use RGen 0.7.0 Issue Type: Improvement Affects Versions: 3.7.0 Assignee: Melissa Stone Components: RE Created: 08/Jul/14 3:32 PM Priority: Normal Reporter: Andy Parker PUP-2831 updated puppet to work with rgen 0.7.0. Before those fixes it made some mistakes that caused 0.7.0 to create issues, which might cause a problem for old packages of puppet that simply rely on = 0.6.5. We need to update the various packages that we make to depend on 0.7.0 and publish an RGen 0.7.0 package. Add Comment
Jira (PUP-2831) Puppet does not work with RGen 0.7.0
Title: Message Title Andy Parker commented on an issue Re: Puppet does not work with RGen 0.7.0 I've filed PUP-2914 to track getting RGen 0.7.0 packaged, published, and depended upon. Add Comment Puppet / PUP-2831 Puppet does not work with RGen 0.7.0 As discovered in PUP-2755, strange things happen when using RGen 0.7.0 with puppet. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-2532) parameter lookup produces screwy result for default values
Title: Message Title Andy Parker assigned an issue to Andy Parker Puppet / PUP-2532 parameter lookup produces screwy result for default values Change By: Andy Parker Assignee: AndyParker Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-743) Report retrieval fails on JSON::ParserError
Title: Message Title Andy Parker updated an issue PuppetDB / PDB-743 Report retrieval fails on JSON::ParserError Change By: Andy Parker Summary: Report submission retrieval failsonJSON::ParserError Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-743) Report retrieval fails on JSON::ParserError
Title: Message Title Andy Parker commented on an issue Re: Report retrieval fails on JSON::ParserError I just updated the title of this issue. The problem isn't on report submission, it is on report retrieval. The test is performing a puppet agent run and then fetching the report that should be available. Periodically the response on the retrieval request is returning no body, which then doesn't parse as JSON and the test fails. Add Comment PuppetDB / PDB-743 Report retrieval fails on JSON::ParserError We've seen this failure a number of times. Digging into the puppetdb log, I can see that PuppetDB drops a connection for an unknown reason. A couple of recent examples: * http://jenkins-enterprise.delivery.puppetlabs.net/view/PE%20Platform/view/Puppet/job/PE%20Puppet%20Acceptance%20Tests/111/label=modgud.delivery.puppetlabs.net,layout=64mcd-64a,platfo... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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,
Jira (PUP-2885) Periodic timeouts when reading from master
Title: Message Title Andy Parker updated an issue Puppet / PUP-2885 Periodic timeouts when reading from master Change By: Andy Parker Sprint: Week2014- 7 6 - 23 25 to2014- 8 7 - 6 9 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-2885) Periodic timeouts when reading from master
Title: Message Title Andy Parker assigned an issue to Unassigned Puppet / PUP-2885 Periodic timeouts when reading from master Change By: Andy Parker Assignee: AndyParker Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-2885) Periodic timeouts when reading from master
Title: Message Title Andy Parker updated an issue Puppet / PUP-2885 Periodic timeouts when reading from master Change By: Andy Parker Fix Version/s: 3.7.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-2885) Periodic timeouts when reading from master
Title: Message Title Andy Parker updated an issue Puppet / PUP-2885 Periodic timeouts when reading from master Change By: Andy Parker Story Points: 1 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-2885) Periodic timeouts when reading from master
Title: Message Title Andy Parker updated an issue Puppet / PUP-2885 Periodic timeouts when reading from master Change By: Andy Parker Sprint: Week2014-7-23to2014-8-6 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-2885) Periodic timeouts when reading from master
Title: Message Title Andy Parker commented on an issue Re: Periodic timeouts when reading from master I think the correct fix for this will involve: Audit that the timeout that Josh identified isn't needed Remove the timeout if it turns out that it truly is redundant Push the timeout down closer to where it is needed if it turns out there are other issues the timeout could have been covering. Add Comment Puppet / PUP-2885 Periodic timeouts when reading from master Periodically, there are failures where the agent performs a pluginsync, a number of files are downloaded from the master, and eventually one of the files hangs, timeouts, and causes the pluginsync to abort. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2711) The manifests directory should be recursively loaded when using directory environments
Title: Message Title Andy Parker commented on an issue Re: The manifests directory should be recursively loaded when using directory environments Merged into master in bb4608. Add Comment Puppet / PUP-2711 The manifests directory should be recursively loaded when using directory environments We have a manifest directory with multiples subdirectories full of node definitions. We would prefer to stay with this layout rather than moving all the node definition files into the manifests directory. It would also make migration easier to directory environments as all one would need to do is remove the import function calls. {code} manifests ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-2532) parameter lookup produces screwy result for default values
Title: Message Title Andy Parker updated an issue Puppet / PUP-2532 parameter lookup produces screwy result for default values Change By: Andy Parker Component/s: DOCS Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-2532) parameter lookup produces screwy result for default values
Title: Message Title Andy Parker commented on an issue Re: parameter lookup produces screwy result for default values Merged into master in 13186f Add Comment Puppet / PUP-2532 parameter lookup produces screwy result for default values When the future parser lookup resource parameter evaluates and there is no parameter value set by the evaluated manifest logic at that point, the evaluator then looks up the default value for that parameter. This unfortunately looks up the default value as seen from the perspective of the lookup resource parameter scope/context, and not the context... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-1970) regression on puppet 3.4.3, exec fail log does not appear when executing on behalf of another user
Title: Message Title Andy Parker updated an issue Puppet / PUP-1970 regression on puppet 3.4.3, exec fail log does not appear when executing on behalf of another user Change By: Andy Parker Component/s: TypesandProviders Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-1970) regression on puppet 3.4.3, exec fail log does not appear when executing on behalf of another user
Title: Message Title Andy Parker updated an issue Puppet / PUP-1970 regression on puppet 3.4.3, exec fail log does not appear when executing on behalf of another user Change By: Andy Parker Labels: regression Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-2794) Specify signatures for blocks of block-accepting methods
Title: Message Title Andy Parker commented on an issue Re: Specify signatures for blocks of block-accepting methods Merged code changes into master in dc6c81. Add Comment Puppet / PUP-2794 Specify signatures for blocks of block-accepting methods Since PUP-2755, the iteration functions are implemented using the new function API, which allows specifying dispatches on parameter types, as well as the signature of the block that is accepted. However, the current implementation doesn't specify the block's signature and leaves at the default of {{Callable[Object]}}. Ideally the block signature should... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-500) Test CollectExpressions
Title: Message Title Andy Parker commented on an issue Re: Test CollectExpressions Merged new tests into master in 651af2 Add Comment Puppet / PUP-500 Test CollectExpressions Implement evaluation of CollectExpression, Query, ExportedQuery, VirtualQuery to support the equivalent 3x expressions. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-2885) Periodic timeouts when reading from master
Title: Message Title Andy Parker assigned an issue to Henrik Lindberg Puppet / PUP-2885 Periodic timeouts when reading from master Change By: Andy Parker Assignee: HenrikLindberg Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-2833) All concrete types do not inherit PAnyType
Title: Message Title Andy Parker updated an issue Puppet / PUP-2833 All concrete types do not inherit PAnyType Change By: Andy Parker Sprint: Week2014- 7 6 - 9 25 to2014-7- 23 9 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-2825) Change Ruby type to Runtime
Title: Message Title Andy Parker assigned an issue to Andy Parker Puppet / PUP-2825 Change Ruby type to Runtime Change By: Andy Parker Assignee: AndyParker Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-2825) Change Ruby type to Runtime
Title: Message Title Andy Parker updated an issue Puppet / PUP-2825 Change Ruby type to Runtime Change By: Andy Parker Sprint: Week2014- 7 6 - 9 25 to2014-7- 23 9 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-2833) All concrete types do not inherit PAnyType
Title: Message Title Andy Parker assigned an issue to Andy Parker Puppet / PUP-2833 All concrete types do not inherit PAnyType Change By: Andy Parker Assignee: AndyParker Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-2833) All concrete types do not inherit PAnyType
Title: Message Title Andy Parker commented on an issue Re: All concrete types do not inherit PAnyType Merged into master in b20e46 This change doesn't have any real user-visible changes. It can skip Functional Review Add Comment Puppet / PUP-2833 All concrete types do not inherit PAnyType All concrete types in the type system should inherit from the PAnyType. Now, some types still inherit from the abstract PAbstractType. For some reason this manages to work even if it is wrong. It should be corrected. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-500) Test CollectExpressions
Title: Message Title Andy Parker commented on an issue Re: Test CollectExpressions Spec updated with PR-7 in commit 1bf754 Add Comment Puppet / PUP-500 Test CollectExpressions Implement evaluation of CollectExpression, Query, ExportedQuery, VirtualQuery to support the equivalent 3x expressions. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-2902) collection of classes should raise a meaningful error
Title: Message Title Andy Parker assigned an issue to Andy Parker Puppet / PUP-2902 collection of classes should raise a meaningful error Change By: Andy Parker Assignee: AndyParker Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-2902) collection of classes should raise a meaningful error
Title: Message Title Andy Parker updated an issue Puppet / PUP-2902 collection of classes should raise a meaningful error Change By: Andy Parker Sprint: Week2014-6-25to2014-7-9 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-2857) Add a Default type
Title: Message Title Andy Parker updated an issue Puppet / PUP-2857 Add a Default type Change By: Andy Parker Sprint: Week2014- 7 6 - 9 25 to2014-7- 23 9 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-2902) collection of classes should raise a meaningful error
Title: Message Title Andy Parker commented on an issue Re: collection of classes should raise a meaningful error Merged into master in b119f6 Add Comment Puppet / PUP-2902 collection of classes should raise a meaningful error If an attempt is made to collect classes {code} Class | | {code} The 3x runtime issues an error that says: {code} Error: Resource type class doesn't exist {code} Which is misleading. The 4x runtime fails with this message: (essentially the same). {code} Error while evaluating a Virtual Query, Resource type class doesn't exist {code} The... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-2825) Change Ruby type to Runtime
Title: Message Title Andy Parker commented on an issue Re: Change Ruby type to Runtime Merged into master in f71608 There isn't really anything to FR on this. It is almost entirely an internal item at this point. Add Comment Puppet / PUP-2825 Change Ruby type to Runtime The type system has space in it for referring to types internal the the runtime that implements the puppet language. At the moment this is the word {{Ruby}}, but space has been made in the language specification for other languages as well. Unfortunately, that name sits on a name that is also very likely to be used in describing configurations, since o... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-2857) Add a Default type
Title: Message Title Andy Parker assigned an issue to Andy Parker Puppet / PUP-2857 Add a Default type Change By: Andy Parker Assignee: AndyParker Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-500) Test CollectExpressions
Title: Message Title Andy Parker assigned an issue to Henrik Lindberg Puppet / PUP-500 Test CollectExpressions Change By: Andy Parker Assignee: HenrikLindberg Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-2711) The manifests directory should be recursively loaded when using directory environments
Title: Message Title Andy Parker assigned an issue to Andy Parker Puppet / PUP-2711 The manifests directory should be recursively loaded when using directory environments Change By: Andy Parker Assignee: AndyParker Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-2794) Specify signatures for blocks of block-accepting methods
Title: Message Title Andy Parker assigned an issue to Andy Parker Puppet / PUP-2794 Specify signatures for blocks of block-accepting methods Change By: Andy Parker Assignee: AndyParker Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-2552) Future parser breaks concat module
Title: Message Title Andy Parker commented on an issue Re: Future parser breaks concat module Nitzan Raz, thank you for the report. I think the behavior you are seeing is because you are specifying the fragment order like so: order = 001. Under the current parser 001 is actually treated as a bareword string, which means that it is equivalent to 001. However, the new parser is treating anything that is a numeric literal as a number, which causes 001 to be treated as the octal number 1. When the number is then interpolated into the string to construct the filename it is then stringified as the decimal representation of the number 1, which is simply 1. You can fix this in your manifests by specifying the value 001 as a string literal of 001. Add Comment Puppet / PUP-2552 Future parser breaks concat module When enabling future parser by specifying {quote} parser = future {quote} in puppet.conf, leading zeroes are removed from integers, disrupting file order in concat. For example, with future parser, keepalived creates this fragment: {quote} 1_keepalived.conf_header {quote} and not: {quote} 001_keepalived.conf_header {quote} Creating bad orderin... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2552) Future parser breaks concat module
Title: Message Title Andy Parker assigned an issue to Nitzan Raz Nitzan Raz, I'm assigning this back to you so that you can confirm that I've assessed the problem correctly and the suggested fix works. If that does work, then I'll close this as won't fix as this is just a side effect of the new number semantics. Puppet / PUP-2552 Future parser breaks concat module Change By: Andy Parker Assignee: AndyParker NitzanRaz Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-2552) Future parser breaks concat module
Title: Message Title Andy Parker commented on an issue Re: Future parser breaks concat module Ashley Penney, is there anything that could be done in the concat module to mitigate this change in the language? Add Comment Puppet / PUP-2552 Future parser breaks concat module When enabling future parser by specifying {quote} parser = future {quote} in puppet.conf, leading zeroes are removed from integers, disrupting file order in concat. For example, with future parser, keepalived creates this fragment: {quote} 1_keepalived.conf_header {quote} and not: {quote} 001_keepalived.conf_header {quote} Creating bad orderin... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-2509) puppet resource service on Solaris needs -H flag
Title: Message Title Andy Parker assigned an issue to Kylo Ginsberg Puppet / PUP-2509 puppet resource service on Solaris needs -H flag Change By: Andy Parker Assignee: AndyParker KyloGinsberg Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-2428) Puppet incorrectly records packages as installed if the puppet process is killed while installing
Title: Message Title Andy Parker assigned an issue to Kylo Ginsberg Puppet / PUP-2428 Puppet incorrectly records packages as installed if the puppet process is killed while installing Change By: Andy Parker Assignee: AndyParker KyloGinsberg Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-2428) Puppet incorrectly records packages as installed if the puppet process is killed while installing
Title: Message Title Andy Parker updated an issue Puppet / PUP-2428 Puppet incorrectly records packages as installed if the puppet process is killed while installing Change By: Andy Parker Component/s: Modules Component/s: TypesandProviders Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-2509) puppet resource service on Solaris needs -H flag
Title: Message Title Andy Parker updated an issue Puppet / PUP-2509 puppet resource service on Solaris needs -H flag Change By: Andy Parker Component/s: Modules Component/s: TypesandProviders Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-2090) (stdlib) concat mutates its arguments
Title: Message Title Andy Parker assigned an issue to John Morton Puppet / PUP-2090 (stdlib) concat mutates its arguments Change By: Andy Parker Assignee: AndyParker JohnMorton Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-1972) pkgdmg can fail when ejecting disk images
Title: Message Title Andy Parker updated an issue Puppet / PUP-1972 pkgdmg can fail when ejecting disk images Change By: Andy Parker Component/s: Modules Component/s: TypesandProviders Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-1972) pkgdmg can fail when ejecting disk images
Title: Message Title Andy Parker assigned an issue to Kylo Ginsberg Puppet / PUP-1972 pkgdmg can fail when ejecting disk images Change By: Andy Parker Assignee: AndyParker KyloGinsberg Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-2885) Periodic timeouts when reading from master
Title: Message Title Andy Parker commented on an issue Re: Periodic timeouts when reading from master Oh! I hadn't noticed the 2 minute timeout around the entire pluginsync. That is a bad thing and possibly the thing that we are hitting. In the apache log that showed the problem we could see that there was about 5 seconds between each request, which means that it would time out if there were more than 12 files being synced. In PE this happens pretty often because it always has stdlib and the tests force complete resyncs pretty often. Add Comment Puppet / PUP-2885 Periodic timeouts when reading from master Periodically, there are failures where the agent performs a pluginsync, a number of files are downloaded from the master, and eventually one of the files hangs, timeouts, and causes the pluginsync to abort. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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
Jira (PUP-2885) Periodic timeouts when reading from master
Title: Message Title Andy Parker commented on an issue Re: Periodic timeouts when reading from master I traced back the timeout for the entire pluginsync as far as I could and ended up at commit 25b28c, which is from 2008. It looks like that has always been there. I suspect that it was there first and then the other timeouts were added later. I agree with Josh that there should only be one or the other of these timeouts. Add Comment Puppet / PUP-2885 Periodic timeouts when reading from master Periodically, there are failures where the agent performs a pluginsync, a number of files are downloaded from the master, and eventually one of the files hangs, timeouts, and causes the pluginsync to abort. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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
Jira (PUP-2885) Periodic timeouts when reading from master
Title: Message Title Andy Parker created an issue Puppet / PUP-2885 Periodic timeouts when reading from master Issue Type: Bug Affects Versions: 3.6.2 Assignee: Andy Parker Components: Networking Services Created: 02/Jul/14 3:02 PM Environment: Rack, Passenger, Apache Priority: Normal Reporter: Andy Parker Periodically, there are failures where the agent performs a pluginsync, a number of files are downloaded from the master, and eventually one of the files hangs, timeouts, and causes the pluginsync to abort. Add Comment
Jira (PUP-1811) in with regexps should set match variables
Title: Message Title Andy Parker assigned an issue to Andy Parker Puppet / PUP-1811 in with regexps should set match variables Change By: Andy Parker Assignee: AndyParker Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-1811) in with regexps should set match variables
Title: Message Title Andy Parker commented on an issue Re: in with regexps should set match variables The changes for this caused a failure in acceptance tests that exercised virtual resource collection. This uncovered that the integration tests we have for resource collection aren't being run against the future parser. In addition the particular case that was in the failed acceptance tests were not covered by the spec/integration test. Add Comment Puppet / PUP-1811 in with regexps should set match variables {noformat} if /.(a)/ in [b, c, baba] { notice($0) notice($1) } {noformat} results in ba and a being output. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-1811) in with regexps should set match variables
Title: Message Title Andy Parker assigned an issue to Henrik Lindberg Puppet / PUP-1811 in with regexps should set match variables Change By: Andy Parker Assignee: HenrikLindberg Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-501) Test Evaluation of ResourceExpressions
Title: Message Title Andy Parker updated an issue Puppet / PUP-501 Test Evaluation of ResourceExpressions Change By: Andy Parker Sprint: Week2014-7-9to2014-7-23 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-511) Specify Resource Expression Evaluation
Title: Message Title Andy Parker updated an issue Puppet / PUP-511 Specify Resource _expression_ Evaluation Change By: Andy Parker Sprint: Week2014-7-9to2014-7-23 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-2845) Move epp() and inline_epp() to 4x function API
Title: Message Title Andy Parker assigned an issue to Andy Parker Puppet / PUP-2845 Move epp() and inline_epp() to 4x function API Change By: Andy Parker Assignee: AndyParker Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-2794) Specify signatures for blocks of block-accepting methods
Title: Message Title Andy Parker assigned an issue to Henrik Lindberg Puppet / PUP-2794 Specify signatures for blocks of block-accepting methods Change By: Andy Parker Assignee: HenrikLindberg Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-511) Specify Resource Expression Evaluation
Title: Message Title Andy Parker updated an issue Puppet / PUP-511 Specify Resource _expression_ Evaluation Change By: Andy Parker Sprint: Week2014-6-25to2014-7-9 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-501) Test Evaluation of ResourceExpressions
Title: Message Title Andy Parker updated an issue Puppet / PUP-501 Test Evaluation of ResourceExpressions Change By: Andy Parker Sprint: Week2014-6-25to2014-7-9 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-480) Complete handling of undef/nil
Title: Message Title Andy Parker commented on an issue Re: Complete handling of undef/nil Functionally this seems to be working, but there are still a lot of cases where :undef is used that need to either be explained or removed. Add Comment Puppet / PUP-480 Complete handling of undef/nil A decision needs to be made regarding handling of undef as nil. There is agreement that it should be handled as a nil value everywhere except one case; when setting an attribute value. Currently setting undef as an attribute value has the meaning do not set this attribute (as opposed to set this attribute to nil) - which has the effect of selectin... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-480) Complete handling of undef/nil
Title: Message Title Andy Parker commented on an issue Re: Complete handling of undef/nil While experimenting with this I put together some functions and puppet code to check how undef was being passed around. Puppet::Parser::Functions.newfunction(:ident, :type = :rvalue) do |args| args[0] end Puppet::Functions.create_function(:ident4) do def ident4(value) value end end undef.pp notice('$x == undef') notice($x == undef) notice('undef == undef') notice(undef == undef) notice(' != undef') notice( != undef) define a($value = 'default', $desc) { notice($desc) notice($value == 'default') } a { a: desc = a { a: } } a { b: value = undef, desc = a { b: value = undef } } a { c: value = $x, desc = 'a { c: value = $x }' } notice(erb w/unbound lookupvar) notice(inline_template(%= scope.lookupvar('x').nil? %)) $missing = undef notice(erb w/bound but undef lookupvar) notice(inline_template(%= scope.lookupvar('missing').nil? %)) notice('match vars without a match ($0 == undef)') notice($0 == undef) notice('undef literal passed to function translated to empty string (3x function)') notice(ident(undef) == '') notice('unbound variable passed to function translated to empty string (3x function)') notice(ident($x) == '') notice('variable bound to undef passed to function translated to empty string (3x function)') notice(ident($missing) == '') if $settings::parser == future { notice(epp w/unbound var) notice(inline_epp('%= $x == undef %')) notice(epp w/bound but undef var) notice(inline_epp('%= $missing == undef %')) notice(epp with undef passed as param uses default) notice(inline_epp('%-|$value = default|-%%= $value == default %'), { value = undef }) notice('undef literal passed to function (4x function)') notice(ident4(undef) == undef) notice('unbound variable passed to function (4x function)') notice(ident4($x) == undef) notice('variable bound to undef passed to function (4x function)') notice(ident4($missing) == undef) } The undef.pp file can be used to show the differences in undef between parser current and parser future. Add Comment
Jira (PUP-480) Complete handling of undef/nil
Title: Message Title Andy Parker assigned an issue to Henrik Lindberg Puppet / PUP-480 Complete handling of undef/nil Change By: Andy Parker Assignee: AndyParker HenrikLindberg Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-500) Test CollectExpressions
Title: Message Title Andy Parker assigned an issue to Andy Parker Puppet / PUP-500 Test CollectExpressions Change By: Andy Parker Assignee: AndyParker Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-2845) Move epp() and inline_epp() to 4x function API
Title: Message Title Andy Parker commented on an issue Re: Move epp() and inline_epp() to 4x function API Merged into master in aa60e3 Add Comment Puppet / PUP-2845 Move epp() and inline_epp() to 4x function API The {{epp()}} and {{inline_epp()}} functions must be moved to the 4x function API in order to work correctly. The 3x function API requires transformation of all undef/nils to empty string, and that catalog entry types are transformed to Resource references. This does not work well when these values again emerge in Puppet logic. This also blocks the wan... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-2711) The manifests directory should be recursively loaded when using directory environments
Title: Message Title Andy Parker commented on an issue Re: The manifests directory should be recursively loaded when using directory environments After talking with William Van Hevelingen in IRC, I think we should try to get this into puppet 3.7, but gate it with the parser future so that users get the Puppet 4 behavior. The problem is that he can't upgrade and use directory environments until it has this functionality and by leaving it out of 3.7 it means that there isn't actually a good upgrade path for him. I'm concerned about adding this functionality without the feature flag because of the possibility of code being loaded that would not have been before this change. Add Comment Puppet / PUP-2711 The manifests directory should be recursively loaded when using directory environments We have a manifest directory with multiples subdirectories full of node definitions. We would prefer to stay with this layout rather than moving all the node definition files into the manifests directory. It would also make migration easier to directory environments as all one would need to do is remove the import function calls. {code} manifests ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2711) The manifests directory should be recursively loaded when using directory environments
Title: Message Title Andy Parker updated an issue Puppet / PUP-2711 The manifests directory should be recursively loaded when using directory environments Change By: Andy Parker Fix Version/s: 4.0.0 Fix Version/s: 3.7.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-2711) The manifests directory should be recursively loaded when using directory environments
Title: Message Title Andy Parker updated an issue Puppet / PUP-2711 The manifests directory should be recursively loaded when using directory environments Change By: Andy Parker Component/s: DSL Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-2868) `puppet config print` confusing for users
Title: Message Title Andy Parker created an issue Puppet / PUP-2868 `puppet config print` confusing for users Issue Type: Bug Affects Versions: 3.4.0 Assignee: Unassigned Created: 30/Jun/14 2:07 PM Priority: Normal Reporter: Andy Parker puppet config print doesn't require a --section to be specified and doesn't inform the user what section of the config file it is showing the value for. Users then get unexpected information from the command. The command needs to change in some way to make it clear what sections the information is coming from and provide a good way to request information from a specific section. Add Comment
Jira (PUP-2868) `puppet config print` confusing for users
Title: Message Title Andy Parker assigned an issue to Zachary Stern Zachary Stern, Nick Walker, could you two provide a bit of a run down about how users have been confused? What commands are they executing and what output do they expect to see? If you have suggestions to have it better match their expectations and have it clearer to them when it isn't, that would be really helpful as well. Puppet / PUP-2868 `puppet config print` confusing for users Change By: Andy Parker Assignee: ZacharyStern Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-480) Complete handling of undef/nil
Title: Message Title Andy Parker assigned an issue to Andy Parker Puppet / PUP-480 Complete handling of undef/nil Change By: Andy Parker Assignee: AndyParker Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-2869) Puppet should be able to use authenticated proxies
Title: Message Title Andy Parker updated an issue Puppet / PUP-2869 Puppet should be able to use authenticated proxies Change By: Andy Parker Issue Type: Bug Improvement Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-480) Complete handling of undef/nil
Title: Message Title Andy Parker commented on an issue Re: Complete handling of undef/nil Merged into master in d32c49 Add Comment Puppet / PUP-480 Complete handling of undef/nil A decision needs to be made regarding handling of undef as nil. There is agreement that it should be handled as a nil value everywhere except one case; when setting an attribute value. Currently setting undef as an attribute value has the meaning do not set this attribute (as opposed to set this attribute to nil) - which has the effect of selectin... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-1811) in with regexps should set match variables
Title: Message Title Andy Parker assigned an issue to Andy Parker Puppet / PUP-1811 in with regexps should set match variables Change By: Andy Parker Assignee: AndyParker Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-1811) in with regexps should set match variables
Title: Message Title Andy Parker updated an issue Puppet / PUP-1811 in with regexps should set match variables Change By: Andy Parker {noformat} if/ . (a)/in[b,c,baba]{ notice($0) notice($1) } {noformat} resultsin baba ba andabeingoutput. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-1811) in with regexps should set match variables
Title: Message Title Andy Parker commented on an issue Re: in with regexps should set match variables Added PR 3 for the specification to update it to have this functionality. Add Comment Puppet / PUP-1811 in with regexps should set match variables {noformat} if /.(a)/ in [b, c, baba] { notice($0) notice($1) } {noformat} results in ba and a being output. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-1811) in with regexps should set match variables
Title: Message Title Andy Parker assigned an issue to Henrik Lindberg Henrik Lindberg, I'm assigning this to you to take a look at the specification changes. Puppet / PUP-1811 in with regexps should set match variables Change By: Andy Parker Assignee: AndyParker HenrikLindberg Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-2654) label provider for class/define should capitalize all segments
Title: Message Title Andy Parker assigned an issue to Andy Parker Puppet / PUP-2654 label provider for class/define should capitalize all segments Change By: Andy Parker Assignee: AndyParker Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-1811) in with regexps should set match variables
Title: Message Title Andy Parker commented on an issue Re: in with regexps should set match variables Merged changes into puppet's master branch in baea55 Add Comment Puppet / PUP-1811 in with regexps should set match variables {noformat} if /.(a)/ in [b, c, baba] { notice($0) notice($1) } {noformat} results in ba and a being output. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-2654) label provider for class/define should capitalize all segments
Title: Message Title Andy Parker commented on an issue Re: label provider for class/define should capitalize all segments Merged into master in 721fe6 Add Comment Puppet / PUP-2654 label provider for class/define should capitalize all segments When the label provider produces a label for a define/class etc. all segments of the name should be capitalized. The label is shown in error messages. Reproduce with: {code} notice Type[Foo::Bar::Fee] {code} Which displays: {code} [Type[Foo::bar::fee] {code} when it should have been {code} [Type[Foo::Bar::Fee] {code} This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-480) Complete handling of undef/nil
Title: Message Title Andy Parker assigned an issue to Andy Parker Puppet / PUP-480 Complete handling of undef/nil Change By: Andy Parker Assignee: AndyParker Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-278) Variables from command line don't work as expected
Title: Message Title Andy Parker created an issue Hiera / HI-278 Variables from command line don't work as expected Issue Type: Bug Affects Versions: 1.3.4 Assignee: Unassigned Created: 27/Jun/14 4:40 PM Priority: Normal Reporter: Andy Parker This is going to be a little bit of a vague bug report. The problem is one of usability. When hiera contains a data file with: --- data: %{::variable} In order to specify a value for ::variable from the command line you have to do Works hiera data ::variable=value instead of, what many users might expect Doesn't Work hiera data variable=value
Jira (HI-278) Variables from command line don't work as expected
Title: Message Title Andy Parker commented on an issue Re: Variables from command line don't work as expected A PR to make some changes to how MCollective data is used by hiera has a similar problem. Add Comment Hiera / HI-278 Variables from command line don't work as expected This is going to be a little bit of a vague bug report. The problem is one of usability. When hiera contains a data file with: {noformat} --- data: %{::variable} {noformat} In order to specify a value for {{::variable}} from the command line you have to do {noformat:title=Works} hiera data ::variable=value {noformat} instead of, what man... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-2682) Trailing commas should be allowed in node definitions
Title: Message Title Andy Parker commented on an issue Re: Trailing commas should be allowed in node definitions The language specification already states that node lists can have trailing commas. No change needed there. Add Comment Puppet / PUP-2682 Trailing commas should be allowed in node definitions Trailing commas are allowed on parametrized classes, node definitions should have the same behaviour. A comma after c should be allowed. {code} node a, b, c, { } {code} This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-1852) deprecate the 'search' function
Title: Message Title Andy Parker assigned an issue to Andy Parker Puppet / PUP-1852 deprecate the 'search' function Change By: Andy Parker Assignee: AndyParker Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-2682) Trailing commas should be allowed in node definitions
Title: Message Title Andy Parker commented on an issue Re: Trailing commas should be allowed in node definitions Merged into master in 5b37a5 Add Comment Puppet / PUP-2682 Trailing commas should be allowed in node definitions Trailing commas are allowed on parametrized classes, node definitions should have the same behaviour. A comma after c should be allowed. {code} node a, b, c, { } {code} This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-2741) remove the 'search' function
Title: Message Title Andy Parker assigned an issue to Andy Parker Puppet / PUP-2741 remove the 'search' function Change By: Andy Parker Assignee: AndyParker Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-1852) deprecate the 'search' function
Title: Message Title Andy Parker commented on an issue Re: deprecate the 'search' function Understanding what the search function even did took some doing, but I eventually figured it out. Example of search() in use class a::c { notice(c) } class b { search(a) include c } include b Add Comment Puppet / PUP-1852 deprecate the 'search' function The {{search}} functions allows a scope to expand the set of searched namespaces used to find something referenced. This does not seem to rhyme with deprecation / removal of dynamic scoping. It should be deprecated in 3.6 and removed in 4.0 (PUP-2741). This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe
Jira (PUP-1852) deprecate the 'search' function
Title: Message Title Andy Parker commented on an issue Re: deprecate the 'search' function I tried to update the deprecation warning to use the new puppet_deprecation_warning method, which provides the file and line in the puppet manifests that are causing the deprecated functionality to be invoked. However, there isn't any way, without hacking something in, that provides a function with its call location. So I scrapped that idea. Merged into master (with the not as nice warning message) in 280305 Add Comment Puppet / PUP-1852 deprecate the 'search' function The {{search}} functions allows a scope to expand the set of searched namespaces used to find something referenced. This does not seem to rhyme with deprecation / removal of dynamic scoping. It should be deprecated in 3.6 and removed in 4.0 (PUP-2741). This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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
Jira (PUP-2741) remove the 'search' function
Title: Message Title Andy Parker commented on an issue Re: remove the 'search' function Merged into puppet-4 in 8e7341 Add Comment Puppet / PUP-2741 remove the 'search' function The {{search}} functions allows a scope to expand the set of searched namespaces used to find something referenced. This does not seem to rhyme with deprecation / removal of dynamic scoping. It should be deprecated in 3.6 (PUP-1852), and removed in 4.0 (this issue). This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-2798) Stop issuing deprecation warnings for reserved words
Title: Message Title Andy Parker assigned an issue to Andy Parker Puppet / PUP-2798 Stop issuing deprecation warnings for reserved words Change By: Andy Parker Assignee: AndyParker Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-2798) Stop issuing deprecation warnings for reserved words
Title: Message Title Andy Parker commented on an issue Re: Stop issuing deprecation warnings for reserved words Merged into master in 73df8d Add Comment Puppet / PUP-2798 Stop issuing deprecation warnings for reserved words PUP-1027 introduced warnings for new keywords that we want to reserve for functionality that will appear during the Puppet 4.x series. Unfortunately this ended up stopping some types (notably ssh_authorized_key) from working since keywords are generally allowed as parameter names. In PUP-2727 the future parser stopped issuing errors when the reserved word... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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.