Jira (PUP-1291) scheduled_task : add support for "every X minutes or hours" mode
Title: Message Title Dima commented on PUP-1291 Re: scheduled_task : add support for "every X minutes or hours" mode Ok, the newly and imroved pull request: https://github.com/puppetlabs/puppet/pull/3637 Includes some fixes on the old one, includes spec tests and a small bonus by adding support for managing the comment field of the scheduled task. 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-4031) Resource collectors can't be used as metaparameter values
Title: Message Title Henrik Lindberg assigned an issue to Alex Jurkiewicz Puppet / PUP-4031 Resource collectors can't be used as metaparameter values Change By: Henrik Lindberg Assignee: Alex Jurkiewicz 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-4031) Resource collectors can't be used as metaparameter values
Title: Message Title
Henrik Lindberg commented on PUP-4031
Re: Resource collectors can't be used as metaparameter values
This does not work on 3x with classic parser either. Are you saying this is a regression from some earlier version of puppet? If so, which?
3x. results in:
Could not parse for environment production: Syntax error at '<|'; expected '|>'
And 3x with future parser:
Could not parse for environment production: Invalid use of _expression_. A Virtual Query does not produce a value
My suspicion is that this has never worked because of the required lazy evaluation of the query - it will be evaluated at the end, and this creates a very hard ordering problem.
You can instead use the relationship operators directly between resources and queries:
# like this (with a reverse arrow)
exec { 'whatever': }
<- Network_route <| |>
Jira (HI-274) :merge_behavior with deep_merge gem missing should error instead of falling back
Title: Message Title Henrik Lindberg commented on HI-274 Re: :merge_behavior with deep_merge gem missing should error instead of falling back Changed status back to "Ready for CI" as the code is merged and we are waiting for it to clear this stage. There is nothing more to do on this ticket afaikt, the problems that have been encountered are because appropriate configuration of adding the deep_merge gem is missing elsewhere. (Better to add specific tickets that block this ticket). 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-1806) Varargs support for the new function API
Title: Message Title Henrik Lindberg assigned an issue to Unassigned Puppet / PUP-1806 Varargs support for the new function API Change By: Henrik Lindberg Assignee: Andy Parker 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-1806) Varargs support for the new function API
Title: Message Title
Henrik Lindberg commented on PUP-1806
Re: Varargs support for the new function API
Adding an extra optional parameter to param is easy to use. This works well for :required (the default), and :optional, but is trickier for the capturing semantics since it can _expression_ minimum and maximum as well. We may also want to expand on the set of options in the future.
Suggest that the third parameter is either a shorthand notation of :optional, :required or :captures or an options hash where the details are spelled out as follows:
min_occurs => 0 for optional, 1 for required, is 1 by default
max_occurs => :default for infinity otherwise integer count, is infinity by default
captures => boolean
This means that the most common cases are obtained with a single symbol, and that the more complex capture with a cap requires a hash with options.
param 'Integer', :the_rest, {:min_occurs => 2, :max_occurs => 10, :captures => true }
We can either deprecate arg_count and make it an error to use at the same time as giving details to each parameter or update all functions that use arg_count to use the new way of specifying optionality and capture.
I would very much like to get this into 3.7.5 as it affects the API and ease of writing 4x functions.
Add Comment
Jira (PUP-1806) Varargs support for the new function API
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-1806 Varargs support for the new function API Change By: Henrik Lindberg Story Points: 3 2 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-1806) Varargs support for the new function API
Title: Message Title Henrik Lindberg commented on PUP-1806 Re: Varargs support for the new function API Specifying a max_occurs > 1 without a captures is an error. Only the last param may have captures. 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-1806) Varargs support for the new function API
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-1806 Varargs support for the new function API Change By: Henrik Lindberg Fix Version/s: PUP 4.x Fix Version/s: PUP 3.7.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-2769) new function api should have a way to get caller / source location
Title: Message Title Henrik Lindberg assigned an issue to Thomas Hallgren Puppet / PUP-2769 new function api should have a way to get caller / source location Change By: Henrik Lindberg Assignee: Thomas Hallgren 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-2769) new function api should have a way to get caller / source location
Title: Message Title Henrik Lindberg assigned an issue to Unassigned Puppet / PUP-2769 new function api should have a way to get caller / source location Change By: Henrik Lindberg Assignee: Thomas Hallgren 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-1806) Varargs support for the new function API
Title: Message Title Henrik Lindberg assigned an issue to Thomas Hallgren Puppet / PUP-1806 Varargs support for the new function API Change By: Henrik Lindberg Assignee: Thomas Hallgren 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-3948) Let lookup be the impl for agnostic lookup of data
Title: Message Title John Duarte assigned an issue to QA Puppet / PUP-3948 Let lookup be the impl for agnostic lookup of data Change By: John Duarte Status: Ready for CI Test 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-4032) puppet device always exits 0
Title: Message Title Hunter Haugen created an issue Puppet / PUP-4032 puppet device always exits 0 Issue Type: Bug Assignee: Unassigned Created: 2015/02/20 9:36 AM Priority: Normal Reporter: Hunter Haugen Compile errors, resource failures, --detailed-exitcodes... it always exits 0. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
Jira (PUP-4032) puppet device always exits 0
Title: Message Title Hunter Haugen commented on PUP-4032 Re: puppet device always exits 0 https://github.com/puppetlabs/puppet/pull/3633 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-4032) puppet device always exits 0
Title: Message Title Hunter Haugen assigned an issue to Kylo Ginsberg Puppet / PUP-4032 puppet device always exits 0 Change By: Hunter Haugen Assignee: Kylo Ginsberg 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-3948) Let lookup be the impl for agnostic lookup of data
Title: Message Title Kylo Ginsberg commented on PUP-3948 Re: Let lookup be the impl for agnostic lookup of data One consideration not mentioned above is the implications for the puppetserver dependency on puppet-agent. With deep_merge added as a hard dependency, puppetserver no longer can compile catalogs because it can't find deep_merge. Since puppetserver currently (at least for the puppetserver 2.x / puppet-agent 1.x timeframe, see SERVER-352 for an alternate proposal) depends on puppet-agent, and because puppetserver doesn't have access to puppet-agent's gems, we didn't have any great options. We discussed: bundling deep_merge with puppetserver, but that means embedding a transitive dependency in puppetserver, which is asking for trouble having puppetserver use puppet-agent gems, but this was a conscious decision by the puppetserver team around isolating native gems, etc adding symlinks to the puppet-agent package so that the deep_merge gem just shows up in the load path, but this is a hack and violates the principle of least surprise (e.g. 'gem list' wouldn't show it) So consensus was that we should go with #3 (i.e. vendoring deep_merge into puppet) for now, and circle back to #1 further down the road. /cc Josh Cooper Michael Smith Justin Stoller who attended the pow wow on this subject. Please feel free to amend this comment with anything I missed. /cc Henrik Lindberg and Thomas Hallgren for add'l concerns. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
Jira (PUP-3948) Let lookup be the impl for agnostic lookup of data
Title: Message Title Henrik Lindberg commented on PUP-3948 Re: Let lookup be the impl for agnostic lookup of data The vendoring of deep_merge is merged to master: 9f80d65 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-340) Fix Hiera acceptance under new paths
Title: Message Title Michael Smith created an issue Hiera / HI-340 Fix Hiera acceptance under new paths Issue Type: Bug Affects Versions: HI 1.3.4 Assignee: Unassigned Created: 2015/02/20 3:29 PM Fix Versions: HI 2.0.0 Priority: Normal Reporter: Michael Smith Hiera acceptance tests haven't been fully updated for the new vardir paths, as described in https://github.com/puppetlabs/puppet-specifications/blob/master/file_paths.md. Update the tests to query Puppet for the correct paths and use them in all tests so they pass. Add Comment
Jira (HI-340) Fix Hiera acceptance under new paths
Title: Message Title Michael Smith updated an issue Hiera / HI-340 Fix Hiera acceptance under new paths Change By: Michael Smith 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 (HI-340) Fix Hiera acceptance under new paths
Title: Message Title Michael Smith updated an issue Hiera / HI-340 Fix Hiera acceptance under new paths Change By: Michael Smith Sprint: Client 2015-03-04 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-1246) Add V3 API deprecation message
Title: Message Title Brian LaMetterey created an issue PuppetDB / PDB-1246 Add V3 API deprecation message Issue Type: Task Assignee: Unassigned Created: 2015/02/20 3:44 PM Fix Versions: PDB 2.3.x Priority: Normal Reporter: Brian LaMetterey V3 API is slated to be deprecated in 3.x and beyond, so we need to ensure there is a deprecation warning in the 2.x line. Add Comment This message was sent by Atlas
Jira (HI-340) Fix Hiera acceptance under new paths
Title: Message Title Michael Smith commented on HI-340 Re: Fix Hiera acceptance under new paths Henrik Lindberg 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-4031) Resource collectors can't be used as metaparameter values
Title: Message Title Alex Jurkiewicz commented on PUP-4031 Re: Resource collectors can't be used as metaparameter values Sorry, I just mentioned "future parser" so it was clear this looks to be an issue that won't go away with puppet 4.0. I'd like this functionality added to the 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.
