Jira (PUP-1852) deprecate the 'search' function
Title: Message Title
Henrik Lindberg commented on an issue
Re: deprecate the 'search' function
http://links.puppetlabs.com/search-function-deprecation
Added URL to use in deprecation message - currently a reference to this issue (PUP-1852).
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.
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
Jira (PUP-1852) deprecate the 'search' function
Title: Message Title Henrik Lindberg assigned an issue to Henrik Lindberg Puppet / PUP-1852 deprecate the 'search' function Change By: Henrik Lindberg 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-1852) deprecate the 'search' function
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-1852
deprecate the 'search' function
Change By:
Henrik Lindberg
The{{search}}functionsallowsascopetoexpandthesetofsearchednamespacesusedtofindsomethingreferenced.Thisdoesnotseemtorhymewithdeprecation/removalofdynamicscoping.Itshouldbedeprecatedin3.6andremovedin4.0 (PUP-2741) .
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-2741) remove the 'search' function
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-2741
remove the 'search' function
Change By:
Henrik Lindberg
The{{search}}functionsallowsascopetoexpandthesetofsearchednamespacesusedtofindsomethingreferenced.Thisdoesnotseemtorhymewithdeprecation/removalofdynamicscoping.Itshouldbedeprecatedin3.6 (PUP-1852), andremovedin4.0 (thisissue) .
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-2741) remove the 'search' function
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-2741 remove the 'search' function Issue Type: Improvement Assignee: Henrik Lindberg Components: DSL Created: 08/Jun/14 2:41 PM Fix Versions: 3.7.0 Priority: Normal Reporter: Henrik Lindberg 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. Add Comment
Jira (PUP-2741) remove the 'search' function
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-2741 remove the 'search' function Change By: Henrik Lindberg Fix Version/s: 3.7.0 Fix Version/s: 4.0.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-2741) remove the 'search' function
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-2741 remove the 'search' function Change By: Henrik Lindberg Assignee: HenrikLindberg 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
Henrik Lindberg commented on an issue
Re: deprecate the 'search' function
Added separate issue for the removal (PUP-2741)
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 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
Henrik Lindberg commented on an issue
Re: deprecate the 'search' function
PUP-2741 has a PR targeting the puppet-4 branch and has the removal of the function. (Merge it after this issue has been merged, and master has been merged to puppet-4).
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 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-2650) 3.6.1 issues warning message for deprecation
Title: Message Title Jo Rhett commented on an issue Re: 3.6.1 issues warning message for deprecation If you are going to continue this path, please at least provide documentation for what the user's revised expectations should be. Hiding this in a JIRA issue (as is typical) is completely insufficient for such a big change in development style and production policy at active sites. Add Comment Puppet / PUP-2650 3.6.1 issues warning message for deprecation Message is issued from agent runs at the warning level for a deprecation message. Warning: The package type's allow_virtual parameter will be changing its default value from false to true in a future release. If you do not want to allow virtual packages, please explicitly set allow_virtual to false. (at /usr/lib/ruby/site_ruby/1.8/puppet/type.rb:816:in... 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-1782) Deprecation warning when attempt to match a number with a regexp in 3.x
Title: Message Title Henrik Lindberg commented on an issue Re: Deprecation warning when attempt to match a number with a regexp in 3.x The 3x turns any LHS into a string, as an example of a pathological case: $a = [1,2,3] =~ /, / notice $a Notices true. A deprecation in 3.x. cannot be issued for bare word numericals since they are strings, and it is impossible to make a distinction between bare word numerical, and a string with numerical information. All non string cases can be handled. Add Comment Puppet / PUP-1782 Deprecation warning when attempt to match a number with a regexp in 3.x PUP-483 describes how this is being handled in the future parser. We should issue a deprecation warning a =~ or !~ is performed with an LHS that is numeric in 3.x. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this
Jira (PUP-1782) Deprecation warning when attempt to match a number with a regexp in 3.x
Title: Message Title Henrik Lindberg commented on an issue Re: Deprecation warning when attempt to match a number with a regexp in 3.x Also note that the 3x evaluator performs the same kind of odd matching logic in case and selector expressions. There 4x simply will not match a regexp against anything but String. This means that a 3x deprecation for regexp evaluate_match will potentially produce lots of deprecation warnings, while a deprecation check in the 3x MatchOperator only deprecates the =~ and !~ operators. To correctly handle deprecations for case and selector, it is only the cases where a Regexp actually matches the test value and the test value is not a string that should result in a deprecation warning. (this because it will continue to not match other data types in the future). Will make a PR for the match operator(s) deprecation and leave the rest open for discussion. Add Comment Puppet / PUP-1782 Deprecation warning when attempt to match a number with a regexp in 3.x PUP-483 describes how this is being handled in the future parser. We should issue a deprecation warning a =~ or !~ is performed with an LHS that is numeric in 3.x. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PDB-704) PuppetDB installing postgresql is not optional
Title: Message Title
Aaron Hicks created an issue
PuppetDB / PDB-704
PuppetDB installing postgresql is not optional
Issue Type:
Bug
Assignee:
Unassigned
Components:
Module
Created:
08/Jun/14 4:45 PM
Environment:
All installs where PostgreSQL has multiple services using it.
Labels:
puppetdb postgresql
Priority:
Normal
Reporter:
Aaron Hicks
The puppetlabs-puppetdb module installs PostgreSQL, and this is not optional.
This means it is not possible to install postgresql separately with a tuned configuration for your environment, or in a manner that could be reused by other services.
Either make the installation of the PuppetDB optiona via a parameter, or remove it completely.
By parameter: ``` class {'postgresql::server': }
class {'puppetdb': install_postgresql = false, }
```
..or not at all: ``` class {'postgresql::server': }
Jira (PUP-1782) Deprecation warning when attempt to match a number with a regexp in 3.x
Title: Message Title Henrik Lindberg commented on an issue Re: Deprecation warning when attempt to match a number with a regexp in 3.x Link for deprecation message http://links.puppetlabs.com/deprecate-match-nonstring defined and used in messages. The link currently points to this issue (PUP-1782). Add Comment Puppet / PUP-1782 Deprecation warning when attempt to match a number with a regexp in 3.x PUP-483 describes how this is being handled in the future parser. We should issue a deprecation warning a =~ or !~ is performed with an LHS that is numeric in 3.x. 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-1299) Deprecate and eliminate magic parameter array handling
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-1299 Deprecate and eliminate magic parameter array handling Change By: Henrik Lindberg 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-1299) Deprecate and eliminate magic parameter array handling
Title: Message Title
Henrik Lindberg commented on an issue
Re: Deprecate and eliminate magic parameter array handling
On second thought - this is really difficult to deprecate in a meaningful way as it would output lots of deprecations that a user can do very little about. Seems more to be a documentation issue targeting those that develop types - this since they had to deal with all kinds of data earlier, but from Puppet 4.0, they do not have to.
Changing this to fixed for 3.7 future parser, and marking it with DOCS.
Add Comment
Puppet / PUP-1299
Deprecate and eliminate magic parameter array handling
Puppet's parser will automatically de-arrayify single element arrays for parameters (and properties). See `lib/puppet/parser/resource.rb` {code} result[p] = if v.is_a?(Array) and v.length == 1 v[0] else v end {code} As a result when writing a custom type, the parameter...
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
Jira (PUP-1299) Deprecate and eliminate magic parameter array handling
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-1299 Deprecate and eliminate magic parameter array handling Change By: Henrik Lindberg Labels: future-parser redmine 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-2244) parse error on class parameters named default
Title: Message Title
Henrik Lindberg commented on an issue
Re: parse error on class parameters named default
Can not reproduce this on the latest version, nor with future parser. Both produce the expected output baz and no error is raised. Not sure when this issue was fixed, and 2.7.25 is quite old.
Add Comment
Puppet / PUP-2244
parse error on class parameters named default
It seems that under 2.7.x (or at least 2.7.25) it is valid to define a class in the DSL with a parameter named default but it is invalid to declare a class with a parameter of the same name. Eg. $ be puppet --version 2.7.25 $ be puppet apply -e 'class foo($default = foo) { notify{$default:} } class {foo:}' notice: foo notice: /Stage[main]/Foo/No...
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-1046) puppet module generate should produce a skeleton spec test
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-1046 puppet module generate should produce a skeleton spec test Change By: Kylo Ginsberg Component/s: PMT 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-2301) puppet module list --tree output shows dependencies incorrectly
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-2301 puppet module list --tree output shows dependencies incorrectly Change By: Kylo Ginsberg Component/s: PMT 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-2304) Implement requirements support for the PMT
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-2304 Implement requirements support for the PMT Change By: Kylo Ginsberg Component/s: PMT 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-2186) Add `puppet module show` action
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-2186 Add `puppet module show` action Change By: Kylo Ginsberg Component/s: PMT 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-2300) Prune dead code from PMT
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-2300 Prune dead code from PMT Change By: Kylo Ginsberg Component/s: PMT 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-2432) module skeleton is using deprecated way to configure spec_helper
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-2432 module skeleton is using deprecated way to configure spec_helper Change By: Kylo Ginsberg Component/s: PMT 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.
