Jira (PUP-6210) Report overall status should not be noop because of only one noop resource
Title: Message Title Fabien Malfoy commented on PUP-6210 Re: Report overall status should not be noop because of only one noop resource As I read it from you, yes it should. Thank you. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4742) Bring semantic_puppet library into Puppet
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-4742 Bring semantic_puppet library into Puppet Change By: Kylo Ginsberg Fix Version/s: PUP 5.0.0 Fix Version/s: PUP 4.5.0 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6232) generated modules will not work with ruby 1.8.7
Title: Message Title John Duarte commented on PUP-6232 Re: generated modules will not work with ruby 1.8.7 FYI, the explicit error when using puppet with ruby < 1.9.3 was added at https://github.com/puppetlabs/puppet/commit/105040e41915bf6a106ee7d54c01e2c18b7c970f See PUP-2563 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-490) Move hiera.yaml from codedir to confdir
Title: Message Title Steve Barlow commented on HI-490 Re: Move hiera.yaml from codedir to confdir Kenn Hussey I added the language scrum team this this ticket. Do you want me to add the RE team as well? Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-490) Move hiera.yaml from codedir to confdir
Title: Message Title Steve Barlow updated an issue Hiera / HI-490 Move hiera.yaml from codedir to confdir Change By: Steve Barlow Scrum Team/s: Language Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-510) Look for hiera.yaml in codedir first, then confdir
Title: Message Title Steve Barlow updated an issue Hiera / HI-510 Look for hiera.yaml in codedir first, then confdir Change By: Steve Barlow Fix Version/s: HI 3.1.3 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-490) Move hiera.yaml from codedir to confdir
Title: Message Title Henrik Lindberg updated an issue Hiera / HI-490 Move hiera.yaml from codedir to confdir Change By: Henrik Lindberg Scrum Team/s: Language Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-490) Move hiera.yaml from codedir to confdir
Title: Message Title Steve Barlow updated an issue Hiera / HI-490 Move hiera.yaml from codedir to confdir Change By: Steve Barlow Scrum Team/s: Language Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6178) Look for hiera.yaml in codedir first, then confdir
Title: Message Title Henrik Lindberg assigned an issue to Thomas Hallgren Puppet / PUP-6178 Look for hiera.yaml in codedir first, then confdir Change By: Henrik Lindberg Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-510) Look for hiera.yaml in codedir first, then confdir
Title: Message Title Henrik Lindberg assigned an issue to Thomas Hallgren Hiera / HI-510 Look for hiera.yaml in codedir first, then confdir Change By: Henrik Lindberg Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6232) generated modules will not work with ruby 1.8.7
Title: Message Title John Duarte assigned an issue to Unassigned Puppet / PUP-6232 generated modules will not work with ruby 1.8.7 Change By: John Duarte Assignee: John Duarte Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6251) Empty Array type broken, neither Array[0,0] nor Array[T,0,0] works
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6251 Empty Array type broken, neither Array[0,0] nor Array[T,0,0] works Change By: Henrik Lindberg Priority: Major Normal Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6232) generated modules will not work with ruby 1.8.7
Title: Message Title John Duarte commented on PUP-6232 Re: generated modules will not work with ruby 1.8.7 The generated module Gemfile also specifies installed puppet version as a dependency as well and puppet itself requires ruby >= 1.9.3 https://github.com/puppetlabs/puppet/blob/master/lib/puppet.rb#L3 Therefore ruby 1.8.7 is still not supported by puppet module generate Test results Tested with puppet-agent at sha ab9e395 containing puppet at sha a3c6ffa. [root@npf1i987o60v7cv bar]# ruby --version ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux] [root@npf1i987o60v7cv bar]# bundle exec rake rake aborted! LoadError: Puppet 4.4.2 requires ruby 1.9.3 or greater. Steps to reproduce Confirm ruby 1.8.7 [root@npf1i987o60v7cv bar]# ruby --version
Jira (PUP-6232) generated modules will not work with ruby 1.8.7
Title: Message Title John Duarte updated an issue Puppet / PUP-6232 generated modules will not work with ruby 1.8.7 Change By: John Duarte QA Risk Assessment: Medium Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6232) generated modules will not work with ruby 1.8.7
Title: Message Title John Duarte updated an issue Puppet / PUP-6232 generated modules will not work with ruby 1.8.7 Change By: John Duarte QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6232) generated modules will not work with ruby 1.8.7
Title: Message Title John Duarte assigned an issue to John Duarte Puppet / PUP-6232 generated modules will not work with ruby 1.8.7 Change By: John Duarte Assignee: qa John Duarte Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6257) Add --allow-authorization-extensions to puppet cert sign
Title: Message Title Nathaniel Smith updated an issue Puppet / PUP-6257 Add --allow-authorization-extensions to puppet cert sign Change By: Nathaniel Smith In Scope* Support a new flag in the "puppet cert sign" tool, "--allow-authorization-extensions"* Determine if a cert given to "puppet cert sign" has any extensions under the puppet.1.3 OID arc* Fail the signing unless the --allow-authorization-extensions flag is present * Audit the cert-related tools in puppet to see if any need to be updated with respect to this work; ca, certificate, certificate-request, certificate-revocation-list. Hopefully they don't need to be updated. Out of Scope* Worrying about any extensions other than those under puppet.1.3 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6258) Update Puppet OID lists to add new authorized extensions
Title: Message Title Nathaniel Smith updated an issue Puppet / PUP-6258 Update Puppet OID lists to add new authorized extensions Change By: Nathaniel Smith In Scope* Add new extensions to puppet's oids.rb* Add new extensions to Clojure CAOut of Scope* Functional changes anywhereOpen Questions* Do we have sources of truth beyond the oids.rb file in puppet and the clojure ca's list?* Do we need to do anything Official(tm) about the new arc? * What exactly are the new authorized extensions? Just an "auth'd" mirror of the current list? Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6258) Update Puppet OID lists to add new authorized extensions
Title: Message Title Nathaniel Smith assigned an issue to Nathaniel Smith Puppet / PUP-6258 Update Puppet OID lists to add new authorized extensions Change By: Nathaniel Smith Assignee: Nathaniel Smith Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6258) Update Puppet OID lists to add new authorized extensions
Title: Message Title Nathaniel Smith created an issue Puppet / PUP-6258 Update Puppet OID lists to add new authorized extensions Issue Type: New Feature Assignee: Unassigned Created: 2016/05/02 3:08 PM Priority: Normal Reporter: Nathaniel Smith In Scope Add new extensions to puppet's oids.rb Add new extensions to Clojure CA Out of Scope Functional changes anywhere Open Questions Do we have sources of truth beyond the oids.rb file in puppet and the clojure ca's list? Do we need to do anything Official about What exactly are the new authorized extensions? Just an "auth'd" mirror of the current list?
Jira (PUP-6258) Update Puppet OID lists to add new authorized extensions
Title: Message Title Nathaniel Smith updated an issue Puppet / PUP-6258 Update Puppet OID lists to add new authorized extensions Change By: Nathaniel Smith Sub-team: jade In Scope* Add new extensions to puppet's oids.rb* Add new extensions to Clojure CAOut of Scope* Functional changes anywhereOpen Questions* Do we have sources of truth beyond the oids.rb file in puppet and the clojure ca's list?* Do we need to do anything Official( ? tm ) about * What exactly are the new authorized extensions? Just an "auth'd" mirror of the current list? Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6232) generated modules will not work with ruby 1.8.7
Title: Message Title William Hopper assigned an issue to qa Puppet / PUP-6232 generated modules will not work with ruby 1.8.7 Change By: William Hopper Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6232) generated modules will not work with ruby 1.8.7
Title: Message Title William Hopper updated an issue Puppet / PUP-6232 generated modules will not work with ruby 1.8.7 Change By: William Hopper Sprint: Client 2016-05-04 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6232) generated modules will not work with ruby 1.8.7
Title: Message Title Anderson Mills updated an issue Puppet / PUP-6232 generated modules will not work with ruby 1.8.7 Change By: Anderson Mills Scope Change Category: Adopted Scope Change Reason: community PR Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6232) generated modules will not work with ruby 1.8.7
Title: Message Title Anderson Mills updated an issue Puppet / PUP-6232 generated modules will not work with ruby 1.8.7 Change By: Anderson Mills Scrum Team: Code Management Client Platform Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6257) Add --allow-authorization-extensions to puppet cert sign
Title: Message Title Nathaniel Smith updated an issue Puppet / PUP-6257 Add --allow-authorization-extensions to puppet cert sign Change By: Nathaniel Smith Sub-team: jade Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6257) Add --allow-authorization-extensions to puppet cert sign
Title: Message Title Nathaniel Smith created an issue Puppet / PUP-6257 Add --allow-authorization-extensions to puppet cert sign Issue Type: New Feature Assignee: Unassigned Created: 2016/05/02 2:48 PM Priority: Normal Reporter: Nathaniel Smith In Scope Support a new flag in the "puppet cert sign" tool, "--allow-authorization-extensions" Determine if a cert given to "puppet cert sign" has any extensions under the puppet.1.3 OID arc Fail the signing unless the --allow-authorization-extensions flag is present Out of Scope Worrying about any extensions other than those under puppet.1.3
Jira (PUP-6230) Data in modules interpret nil as {}
Title: Message Title
Henrik Lindberg commented on PUP-6230
Re: Data in modules interpret nil as {}
In Test 4 - you would assign undef to a key to achieve the same as having a ~ assigned in a data file.
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6230) Data in modules interpret nil as {}
Title: Message Title
Sean Griffin updated an issue
Puppet / PUP-6230
Data in modules interpret nil as {}
Change By:
Sean Griffin
Attachment:
pup-6230-manifest
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6230) Data in modules interpret nil as {}
Title: Message Title
Sean Griffin assigned an issue to Unassigned
Puppet / PUP-6230
Data in modules interpret nil as {}
Change By:
Sean Griffin
Assignee:
Sean Griffin
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6256) Cannot convert Puppet::Util::Log to integer
Title: Message Title Jon McKenzie created an issue Puppet / PUP-6256 Cannot convert Puppet::Util::Log to integer Issue Type: Bug Affects Versions: PUP 3.8.6 Assignee: Kylo Ginsberg Components: Client Created: 2016/05/02 1:40 PM Priority: Normal Reporter: Jon McKenzie Re-creating this issue. There seems to be a bug in a particular method where an integer return value is expected, but a log object is returned instead. This prevents the exception from bubbling up into an error that the user can actually understand Add Comment
Jira (PDB-2666) Add a manage_db parameter to let the user the freedom to manage
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-2666 Add a manage_db parameter to let the user the freedom to manage Issue Type: Bug Assignee: Unassigned Created: 2016/05/02 12:26 PM Priority: Normal Reporter: gepetto-bot the postgresql database creation outside of the puppetdb module. An other option would be to include the functionality within the manage_dbserver parameter, if set to false/true, instead of introducing another parameter. Let me know if you would be in favor of the manage_dbserver parameter takes care of it, and I change it, or if you prefer, what I did so far. Then I can change if necessary, and add some tests for it. cheers, Add Comment
Jira (PUP-1364) Yum package arch and version ensuring failing
Title: Message Title Branan Riley updated an issue Puppet / PUP-1364 Yum package arch and version ensuring failing Change By: Branan Riley Comment: Work for this ticket was done as part of PUP-5025. Functional review should be rolled up in that ticket. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6097) YUM/APT package providers require architecture as part of package version
Title: Message Title William Hopper commented on PUP-6097 Re: YUM/APT package providers require architecture as part of package version Work for this ticket was done as part of PUP-5025. Functional review should be rolled up in that ticket. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1364) Yum package arch and version ensuring failing
Title: Message Title William Hopper commented on PUP-1364 Re: Yum package arch and version ensuring failing Work for this ticket was done as part of PUP-5025. Functional review should be rolled up in that ticket. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2419) Deprecate "req_bits" Setting
Title: Message Title Branan Riley updated an issue Puppet / PUP-2419 Deprecate "req_bits" Setting Change By: Branan Riley Sprint: Client 2016-05- 18 (Freeze) 04 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3941) Puppet agent will accept yaml content
Title: Message Title Branan Riley updated an issue Puppet / PUP-3941 Puppet agent will accept yaml content Change By: Branan Riley Sprint: Client 2016-05- 18 (Freeze) 04 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3740) Update puppet package dependencies to require ruby 1.9.3 or greater
Title: Message Title Branan Riley updated an issue Puppet / PUP-3740 Update puppet package dependencies to require ruby 1.9.3 or greater Change By: Branan Riley Sprint: Client 2016-05-18 (Freeze) Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4742) Bring semantic_puppet library into Puppet
Title: Message Title Anderson Mills commented on PUP-4742 Re: Bring semantic_puppet library into Puppet I don't know of any breaking changes this causes. I hadn't dived in enough to explore SemVer and it's differences with semantic_puppet, and it wasn't high priority at the time it was created. Feel free to switch to a new version if you don't believe it has breaking changes. Kylo Ginsberg Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6241) puppet agent ostensibly succeeds when environment directory has wrong permissions
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6241 puppet agent ostensibly succeeds when environment directory has wrong permissions Change By: Eric Thompson QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6241) puppet agent ostensibly succeeds when environment directory has wrong permissions
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6241 puppet agent ostensibly succeeds when environment directory has wrong permissions Change By: Eric Thompson QA Highest Test Level: Acceptance Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6241) puppet agent ostensibly succeeds when environment directory has wrong permissions
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6241 puppet agent ostensibly succeeds when environment directory has wrong permissions Change By: Eric Thompson QA Risk Assessment: Medium Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6241) puppet agent ostensibly succeeds when environment directory has wrong permissions
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6241 puppet agent ostensibly succeeds when environment directory has wrong permissions Change By: Eric Thompson Acceptance Criteria: agent should fail with some error if the environment is unreadable. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-490) Move hiera.yaml from codedir to confdir
Title: Message Title Morgan Rhodes commented on HI-490 Re: Move hiera.yaml from codedir to confdir (thumbsup) the comment makes more sense now. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6252) reorganize documentation of function 'new'
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-6252 reorganize documentation of function 'new' Change By: Kenn Hussey Scrum Team: Language Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6097) YUM/APT package providers require architecture as part of package version
Title: Message Title Brandon High commented on PUP-6097 Re: YUM/APT package providers require architecture as part of package version William Hopper Excellent! This won't help on the puppet-agent module since it is upgrading from a version without this fix, but I'm sure some users will be appreciative. Thanks! Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5907) Define the PCore Serialization API and Features
Title: Message Title Henrik Lindberg commented on PUP-5907 Re: Define the PCore Serialization API and Features This ticket has been used as an umbrella for the Pcore specification work. Originally it was for specifying the serialization format but in order to do so, it was first needed to first specify what exactly was going to be serialized, how to express that, define it, etc. Thus, this ticket has taken on epic proportions. The exploratory / presentation document for Pcore is now in reasonable shape, and I am therefore moving this ticket along in favor of new, more specific tickets for the remaining work. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2501) add ability to test against puppetserver nightlies
Title: Message Title Melissa Stone assigned an issue to Melissa Stone PuppetDB / PDB-2501 add ability to test against puppetserver nightlies Change By: Melissa Stone Assignee: Melissa Stone Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6255) Add documentation for Object.new in function new
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-6255 Add documentation for Object.new in function new Issue Type: Improvement Assignee: Unassigned Created: 2016/05/02 9:29 AM Fix Versions: PUP 4.5.0 Priority: Normal Reporter: Henrik Lindberg Add documentation about Object.new in the function new as that is the only place such documentation can surface to users at the moment. Add Comment
Jira (PUP-6254) Windows Service start reports failures instead of success under some states
Title: Message Title Glenn Sarti created an issue Puppet / PUP-6254 Windows Service start reports failures instead of success under some states Issue Type: Bug Assignee: Unassigned Created: 2016/05/02 9:28 AM Priority: Normal Reporter: Glenn Sarti During FM-5175, the WSUS_Client module failed acceptance tests intermittently due to a service start failure; 16:23:14 Failures: 16:23:14 16:23:14 1) wsus_client auto_update_option => notifyonly 16:23:14 Failure/Error: apply_manifest_on(default, pp, :catch_failures => true)
Jira (PUP-5975) Remove Range#intersection monkey patch
Title: Message Title Josh Cooper commented on PUP-5975 Re: Remove Range#intersection monkey patch I'm not sure if we need a deprecation warning. I assume the only affected code is in PMT when it does module version comparison, but the monkey patch could affect custom type/provider logic that compare versions? Might also be interesting to see if tests still pass with the monkey patch removed. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6225) Add 'new' function to the Puppet Object type
Title: Message Title Henrik Lindberg commented on PUP-6225 Re: Add 'new' function to the Puppet Object type Merged to master at: 1c19147 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6225) Add 'new' function to the Puppet Object type
Title: Message Title Henrik Lindberg assigned an issue to Unassigned Puppet / PUP-6225 Add 'new' function to the Puppet Object type Change By: Henrik Lindberg Assignee: Henrik Lindberg Acceptance Criteria: It should be possible to define and create basic Object Type definitions. The acceptance criteria are covered by unit tests. The now added logic is the foundation for additional work that builds out the complete set of features for the Object Type and Pcore. Release Notes Summary: Part of the larger feature Pcore. Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from
Jira (PUP-6252) reorganize documentation of function 'new'
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-6252 reorganize documentation of function 'new' Issue Type: Improvement Assignee: Unassigned Created: 2016/05/02 9:14 AM Fix Versions: PUP 4.5.0 Priority: Normal Reporter: Henrik Lindberg The documentation of the function new is not well organized. This is a problem because it is currently the only way for the various new operations on types to surface their documentation. With the recent addition of SemVer and SemVerRange it became clear that a reorganization is needed. An index should be added that more clearly shows the conversions to/from types and for types where it is more of just an instantiation. This ticket blocks the documentation work for SemVer and SemVerRange types. Longer term, we must have a way to generate the documentation for types and their operations. Add Comment
Jira (PUP-6253) Add documentation for SemVer and SemVerRange in function new
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-6253
Add documentation for SemVer and SemVerRange in function new
Change By:
Henrik Lindberg
Add documentation about SemVer.new and SemVerRange.new to the documentation for function {{new}} Also add specification of SemVer and SemVerRange to the Puppet Language specification repo .
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2665) Missing PostgreSQL extension `pg_trgm`
Title: Message Title nobody updated an issue PuppetDB / PDB-2665 Missing PostgreSQL extension `pg_trgm` Change By: nobody Environment: Ater intsall module puppetlabs-puppetdb (v5.1.2) in logs we see:2016-05-02 20:58:16,405 WARN [p.p.s.migrate] Missing PostgreSQL extension `pg_trgm`We are unable to create the recommended pg_trgm indexes due tothe extension not being installed correctly. Run the command:CREATE EXTENSION pg_trgm;as the database super user on the PuppetDB database to correctthis, then restart PuppetDB.It's fix with install postgresql94-contrib.x86_64So... can we install it at once with puppet automatically ? Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6253) Add documentation for SemVer and SemVerRange in function new
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-6253 Add documentation for SemVer and SemVerRange in function new Issue Type: Improvement Assignee: Thomas Hallgren Created: 2016/05/02 9:16 AM Fix Versions: PUP 4.5.0 Priority: Normal Reporter: Henrik Lindberg Add documentation about SemVer.new and SemVerRange.new to the documentation for function new. Add Comment This message was sent by Atlassian JIRA
Jira (PDB-2665) Missing PostgreSQL extension `pg_trgm`
Title: Message Title nobody updated an issue PuppetDB / PDB-2665 Missing PostgreSQL extension `pg_trgm` Change By: nobody Affects Version/s: PDB module-5.1.0 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2665) Missing PostgreSQL extension `pg_trgm`
Title: Message Title nobody created an issue PuppetDB / PDB-2665 Missing PostgreSQL extension `pg_trgm` Issue Type: Bug Assignee: Unassigned Components: Module Created: 2016/05/02 9:13 AM Environment: Ater intsall module puppetlabs-puppetdb (v5.1.2) in logs we see: 2016-05-02 20:58:16,405 WARN [p.p.s.migrate] Missing PostgreSQL extension `pg_trgm` We are unable to create the recommended pg_trgm indexes due to the extension not being installed correctly. Run the command: CREATE EXTENSION pg_trgm; as the database super user on the PuppetDB database to correct this, then restart PuppetDB. It's fix with install postgresql94-contrib.x86_64 So... can we install it at once with puppet? Priority: Normal Reporter: nobody Add Comment
Jira (PUP-6221) Add SemVer and SemVerRange types to the Puppet Type System
Title: Message Title Henrik Lindberg assigned an issue to Unassigned Merged to master at: 6e1794c Puppet / PUP-6221 Add SemVer and SemVerRange types to the Puppet Type System Change By: Henrik Lindberg Assignee: Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2501) add ability to test against puppetserver nightlies
Title: Message Title Melissa Stone commented on PDB-2501 Re: add ability to test against puppetserver nightlies Yes, I am doing this work Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6249) Semantic::Version should implement operator eql? and operator '=='
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6249 Semantic::Version should implement operator eql? and operator '==' Added to triage sprint - but this should be possible to resolve now. Change By: Henrik Lindberg Story Points: 1 Sprint: Language Triage Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6251) Empty Array type broken, neither Array[0,0] nor Array[T,0,0] works
Title: Message Title Henrik Lindberg assigned an issue to Thomas Hallgren Puppet / PUP-6251 Empty Array type broken, neither Array[0,0] nor Array[T,0,0] works Change By: Henrik Lindberg Assignee: Thomas Hallgren Scope Change Category: Found Scope Change Reason: found by community in 4.4.2 - no workaround for this regression Sprint: Language Triage 2016-05-04 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6251) Empty Array type broken, neither Array[0,0] nor Array[T,0,0] works
Title: Message Title Henrik Lindberg commented on PUP-6251 Re: Empty Array type broken, neither Array[0,0] nor Array[T,0,0] works Ping Kylo Ginsberg this is a pretty bad regression it what was perceived as a format change only. We made a bad decision (error when type is given and size is 0) + managed to also introduce a bug that made it impossible to create an Array[0,0] type. There is no real work around. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6251) Empty Array type broken, neither Array[0,0] nor Array[T,0,0] works
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6251 Empty Array type broken, neither Array[0,0] nor Array[T,0,0] works Change By: Henrik Lindberg Acceptance Criteria: * That it is accepted to create a type like Array[Integer, 0,0] and that it will erase the type and present itself as Array[0,0]* That is is acceptable to create a type like Hash[K, V, 0, 0] and that it will erase the types and present itself as Hash[0,0]* That it is possible to create and use Array[0,0], and Hash[0,0] and that they match the corresponding empty structures. Story Points: 1 Release Notes Summary: Changes to the representation of empty Array and Hash led to problems in that it became impossible to state these types. Both Array[0,0], and Array[T, 0,0] resulted in errors. Summary: Impossible to easily check for empty arrays Empty Array type broken, neither Array[0,0] nor Array[T,0,0] works Sprint: Language Triage Release Notes: Bug Fix Add Comment
Jira (PUP-6251) Impossible to easily check for empty arrays
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6251 Impossible to easily check for empty arrays Change By: Henrik Lindberg Fix Version/s: PUP 4.5.0 Fix Version/s: PUP 4.4.3 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6251) Impossible to easily check for empty arrays
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6251 Impossible to easily check for empty arrays Change By: Henrik Lindberg Priority: Normal Major Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2501) add ability to test against puppetserver nightlies
Title: Message Title Susan McNerney commented on PDB-2501 Re: add ability to test against puppetserver nightlies Melissa Stone is this being done by your team? As PDB doesn't have QA at the moment I am unclear who will do the actual work. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6251) Impossible to easily check for empty arrays
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-6251 Impossible to easily check for empty arrays Change By: Kenn Hussey Scrum Team: Language Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6251) Impossible to easily check for empty arrays
Title: Message Title Henrik Lindberg commented on PUP-6251 Re: Impossible to easily check for empty arrays Oh - this is bad - how did that happen?!? henrik$ puppet apply -e 'notice [] =~ Array[0,0]' Error: Evaluation Error: Array-Type[] arguments must be types. Got Fixnum at line 1:20 henrik$ puppet apply -e 'notice [] =~ Array[Integer, 0,0]' Error: Evaluation Error: Error while evaluating a '[]' _expression_, An empty collection may not specify an element type at line 1:14 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (PDB-2501) add ability to test against puppetserver nightlies
Title: Message Title Melissa Stone updated an issue PuppetDB / PDB-2501 add ability to test against puppetserver nightlies Change By: Melissa Stone Scope Change Category: Found Scope Change Reason: This needs to be handled now so as to not impact xenial landing in couch Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2501) add ability to test against puppetserver nightlies
Title: Message Title Melissa Stone updated an issue PuppetDB / PDB-2501 add ability to test against puppetserver nightlies Change By: Melissa Stone Sprint: RE 2016-05- 11 04 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6249) Semantic::Version should implement operator eql? and operator '=='
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-6249 Semantic::Version should implement operator eql? and operator '==' Change By: Kenn Hussey Scrum Team: Language Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6251) Impossible to easily check for empty arrays
Title: Message Title Julien Pivotto commented on PUP-6251 Re: Impossible to easily check for empty arrays Henrik Lindberg I mean that trying Array[0,0] like in the release notes does not work Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6251) Impossible to easily check for empty arrays
Title: Message Title Henrik Lindberg commented on PUP-6251 Re: Impossible to easily check for empty arrays Julien Pivotto do you mean the problem that it ended up using the first 0 to mean an Array of Integer type. I believe that has been addressed already. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6251) Impossible to easily check for empty arrays
Title: Message Title Julien Pivotto commented on PUP-6251 Re: Impossible to easily check for empty arrays We also need to make Array[0,0] work Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6210) Report overall status should not be noop because of only one noop resource
Title: Message Title Verne Lindner commented on PUP-6210 Re: Report overall status should not be noop because of only one noop resource Fabien Malfoy With the next PE release, the PE console will display run statuses with event types failed, changed, or unchanged and whether or not the run occurred in no-op mode; the no-op resource flag alone will no longer determine run status. It sounds like that should address the issue you describe? Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6251) Impossible to easily check for empty arrays
Title: Message Title Thomas Hallgren commented on PUP-6251 Re: Impossible to easily check for empty arrays Yes. Erasing the type sounds like the best option. That way, Array[String,0,0] == Array[0,0] Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6251) Impossible to easily check for empty arrays
Title: Message Title Henrik Lindberg commented on PUP-6251 Re: Impossible to easily check for empty arrays Ping Thomas Hallgren Change it so that type is ignored/erased when min/max are both 0 ? Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6251) Impossible to easily check for empty arrays
Title: Message Title
Julien Pivotto updated an issue
Puppet / PUP-6251
Impossible to easily check for empty arrays
Change By:
Julien Pivotto
Since 4.4.2 it is impossible to do the following:{code:puppet}if $nodes =~ Array[Data,0,0]{code}I get the following error:{quote}Error while evaluating a '[]' _expression_, An empty collection may not specify an element type{quote}h2. Non technical problems# I would not expect such a change in a _minor (.z) release_# This change does not make sense because it is a valid usecase (e.g when the upper limit is a variable) to have a type.h2. Technical problemsh3. To me, the following statements are true{code:puppet}[] =~ Array[String, 0, 0][] =~ Array[Integer, 0, 0]{code}h3. Alternative writing does not work{code}cat test.pp$test = assert_type(Array[0,0],[])puppet apply test.ppError: Evaluation Error: Array-Type[] arguments must be types. Got Fixnum at /home/roidelapluie/test.pp:1:27 on node nitrogen{code}So there is NO workaround to get the feature working again.h3. Impossible to have a variable as length{code}$test = assert_type(Array[ Integer, $min,$max],[]){code}will noly work with max > 0. Hence an extra {{if}} in the code etc etc
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-6225) Add 'new' function to the Puppet Object type
Title: Message Title Thomas Hallgren assigned an issue to Henrik Lindberg Puppet / PUP-6225 Add 'new' function to the Puppet Object type Change By: Thomas Hallgren Assignee: Thomas Hallgren Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6251) Impossible to easily check for empty arrays
Title: Message Title Julien Pivotto commented on PUP-6251 Re: Impossible to easily check for empty arrays I do agree with PUP-6089 . It does not make sense to display a type for empty arrays. But the extra mile of not allowing a type is too much. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6251) Impossible to easily check for empty arrays
Title: Message Title
Julien Pivotto updated an issue
Puppet / PUP-6251
Impossible to easily check for empty arrays
Change By:
Julien Pivotto
Since 4.4.2 it is impossible to do the following:{code:puppet}if $nodes =~ Array[Data,0,0]{code}I get the following error:{quote}Error while evaluating a '[]' _expression_, An empty collection may not specify an element type{quote}h2. Problems: Non technical problems # I would not expect such a change in a _minor (.z) release_# Array[0,0] does not work# This change does not make sense. h2. Technical problemsh3. To me, the following statements are true : {code:puppet}[] =~ Array[String, 0, 0][] =~ Array[Integer, 0, 0]{code} Another bug: h3. Alternative writing does not work {code}cat test.pp$test = assert_type(Array[0,0],[])puppet apply test.ppError: Evaluation Error: Array-Type[] arguments must be types. Got Fixnum at /home/roidelapluie/test.pp:1:27 on node nitrogen{code}So there is NO workaround to get the feature working again. h3. Impossible to have a variable as length{code}$test = assert_type(Array[$min,$max],[]){code}will noly work with max > 0. Hence an extra {{if}} in the code etc etc
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For
Jira (PUP-6251) Impossible to easily check for empty arrays
Title: Message Title
Julien Pivotto updated an issue
Puppet / PUP-6251
Impossible to easily check for empty arrays
Change By:
Julien Pivotto
Since 4.4.2 it is impossible to do the following:{code:puppet}if $nodes =~ Array[Data,0,0]{code}I get the following error:{quote}Error while evaluating a '[]' _expression_, An empty collection may not specify an element type{quote}h2. Non technical problems# I would not expect such a change in a _minor (.z) release_# This change does not make sense because it is a valid usecase (e . g when the upper limit is a variable) to have a type. h2. Technical problemsh3. To me, the following statements are true{code:puppet}[] =~ Array[String, 0, 0][] =~ Array[Integer, 0, 0]{code}h3. Alternative writing does not work{code}cat test.pp$test = assert_type(Array[0,0],[])puppet apply test.ppError: Evaluation Error: Array-Type[] arguments must be types. Got Fixnum at /home/roidelapluie/test.pp:1:27 on node nitrogen{code}So there is NO workaround to get the feature working again.h3. Impossible to have a variable as length{code}$test = assert_type(Array[$min,$max],[]){code}will noly work with max > 0. Hence an extra {{if}} in the code etc etc
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-6251) Impossible to easily check for empty arrays
Title: Message Title
Julien Pivotto updated an issue
Puppet / PUP-6251
Impossible to easily check for empty arrays
Change By:
Julien Pivotto
Since 4.4.2 it is impossible to do the following:{code:puppet}if $nodes =~ Array[Data,0,0]{code}I get the following error:{quote}Error while evaluating a '[]' _expression_, An empty collection may not specify an element type{quote}h2. Problems:# I would not expect such a change in a _minor (.z) release_# Array[0,0] does not work# This change does not make sense.To me, the following statements are true:{code:puppet}[] =~ Array[String, 0, 0][] =~ Array[Integer, 0, 0]{code}Another bug:{code}cat test.pp$test = assert_type(Array[0,0],[])puppet apply test.ppError: Evaluation Error: Array-Type[] arguments must be types. Got Fixnum at /home/roidelapluie/test.pp:1:27 on node nitrogen .low.cert.mil.be {code}So there is NO workaround to get the feature working again.
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6251) Impossible to easily check for empty arrays
Title: Message Title
Julien Pivotto updated an issue
Puppet / PUP-6251
Impossible to easily check for empty arrays
Change By:
Julien Pivotto
Since 4.4.2 it is impossible to do the following:{code:puppet}if $nodes =~ Array[Data,0,0]{code}I get the following error:{quote}Error while evaluating a '[]' _expression_, An empty collection may not specify an element type{quote} 2 things here h2. Problems :# I would not expect such a change in a _minor (.z) release_# Array[0,0] does not work# This change does not make sense.To me, the following statements are true:{code:puppet}[] =~ Array[String, 0, 0][] =~ Array[Integer, 0, 0]{code} Another bug:{code}cat test.pp$test = assert_type(Array[0,0],[])puppet apply test.ppError: Evaluation Error: Array-Type[] arguments must be types. Got Fixnum at /home/roidelapluie/test.pp:1:27 on node nitrogen.low.cert.mil.be{code}So there is NO workaround to get the feature working again.
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6251) Impossible to easily check for empty arrays
Title: Message Title
Julien Pivotto updated an issue
Puppet / PUP-6251
Impossible to easily check for empty arrays
Change By:
Julien Pivotto
Since 4.4.2 it is impossible to do the following:{code:puppet}if $nodes =~ Array[Data,0,0]{code}I get the following error:{quote}Error while evaluating a '[]' _expression_, An empty collection may not specify an element type{quote}2 things here:# I would not expect such a change in a _minor (.z) release_# This change does not make sense.To me, the following statements are true:{code:puppet}[] =~ Array[String , 0, 0 ][] =~ Array[Integer , 0, 0 ]{code} With that change, it implies that {{Array[String]}} should always be {{Array[String,1]}}. It sounds not great. {{Array[String,1]}} should be enforced by style guides, not like this.
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6251) Impossible to easily check for empty arrays
Title: Message Title
Julien Pivotto updated an issue
Puppet / PUP-6251
Impossible to easily check for empty arrays
Change By:
Julien Pivotto
Since 4.4.2 it is impossible to do the following:{code:puppet}if $nodes =~ Array[Data,0,0]{code}I get the following error:{quote}Error while evaluating a '[]' _expression_, An empty collection may not specify an element type{quote}2 things here:# I would not expect such a change in a _minor (.z) release_# This change does not make sense.To me , the following statements are true :{code:puppet}[] =~ Array[String][] =~ Array[Integer]{code}With that change, it implies that {{Array[String]}} should always be {{Array[String,1]}}. It sounds not great. {{Array[String,1]}} should be enforced by style guides, not like this.
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6251) Impossible to easily check for empty arrays
Title: Message Title
Julien Pivotto updated an issue
Puppet / PUP-6251
Impossible to easily check for empty arrays
Change By:
Julien Pivotto
Since 4.4.2 it is impossible to do the following:{code:puppet}if $nodes =~ Array[Data,0,0]{code}I get the following error:{quote}Error while evaluating a '[]' _expression_, An empty collection may not specify an element type{quote}2 things here: 1. # I would not expect such a change in a _minor (.z) release_ 2. # This change does not make sense.To me:{code:puppet}[] =~ Array[String][] =~ Array[Integer]{code}With that change, it implies that {{Array[String]}} should always be {{Array[String,1]}}. It sounds not great. {{Array[String,1]}} should be enforced by style guides, not like this.
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6251) Impossible to easily check for empty arrays
Title: Message Title
Julien Pivotto updated an issue
Puppet / PUP-6251
Impossible to easily check for empty arrays
Change By:
Julien Pivotto
Since 4.4.2 it is impossible to do the followinq following :{code:puppet}if $nodes =~ Array[Data,0,0]{code}I get the following error:{quote}Error while evaluating a '[]' _expression_, An empty collection may not specify an element type{quote}2 things here:1. I would not expect such a change in a minor _minor (.z) release release_ 2. This change does not make sense.To me:{code:puppet}[] =~ Array[String][] =~ Array[Integer]{code}With that change, it implies that {{Array[String]}} should always be {{Array[String,1]}}. It sounds not great. {{Array[String,1]}} should be enforced by style guides, not like this.
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6251) Impossible to easily check for empty arrays
Title: Message Title
Julien Pivotto updated an issue
Puppet / PUP-6251
Impossible to easily check for empty arrays
Change By:
Julien Pivotto
Since 4.4.2 it is impossible to do the followinq:{code:puppet}if $nodes =~ Array[Data,0,0]{code}I get the following error: {quote} Error while evaluating a '[]' _expression_, An empty collection may not specify an element type {quote} 2 things here:1. I would not expect such a change in a minor (.z) release2. This change does not make sense.To me:{code:puppet}[] =~ Array[String][] =~ Array[Integer]{code}With that change, it implies that {{Array[String]}} should always be {{Array[String,1]}}. It sounds not great. {{Array[String,1]}} should be enforced by style guides, not like this.
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6251) Impossible to easily check for empty arrays
Title: Message Title
Julien Pivotto updated an issue
Puppet / PUP-6251
Impossible to easily check for empty arrays
Change By:
Julien Pivotto
Since 4.4.2 it is impossible to do the followinq:{code:puppet}if $nodes =~ Array[Data,0,0]{code}I get the following error:Error while evaluating a '[]' _expression_, An empty collection may not specify an element type2 things here:1. I would not expect such a change in a minor (.z) release2. This change does not make sense.To me:{code:puppet}[] =~ Array[String][] =~ Array[Integer]{code}With that change, it implies that ` {{ Array[String] ` }} should always be ` {{ Array[String,1] ` }} . It sounds not great. ` {{ Array[String,1] ` }} should be enforced by style guides, not like this.
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6251) Impossible to easily check for empty arrays
Title: Message Title
Julien Pivotto updated an issue
Puppet / PUP-6251
Impossible to easily check for empty arrays
Change By:
Julien Pivotto
Since 4.4.2 it is impossible to do the followinq: ``` {code: puppet } if $nodes =~ Array[Data,0,0] ``` {code} I get the following error:Error while evaluating a '[]' _expression_, An empty collection may not specify an element type2 things here:1. I would not expect such a change in a minor (.z) release2. This change does not make sense.To me: ``` {code: puppet } [] =~ Array[String][] =~ Array[Integer] ``` {code} With that change, it implies that `Array[String]` should always be `Array[String,1]`. It sounds not great. `Array[String,1]` should be enforced by style guides, not like this.
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6251) Impossible to easily check for empty arrays
Title: Message Title Julien Pivotto updated an issue Puppet / PUP-6251 Impossible to easily check for empty arrays Change By: Julien Pivotto Since 4.4.2 it is impossible to do the followinq: ```puppet if $nodes =~ Array[Data,0,0] ``` I get the following error:Error while evaluating a '[]' _expression_, An empty collection may not specify an element type2 things here:1. I would not expect such a change in a minor (.z) release2. This change does not make sense.To me: ```puppet [] =~ Array[String][] =~ Array[Integer] ``` With that change, it implies that ` Array[String] ` should always be ` Array[String,1] ` . It sounds not great. `Array[String,1]` should be enforced by style guides, not like this. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6251) Impossible to easily check for empty arrays
Title: Message Title Julien Pivotto created an issue Puppet / PUP-6251 Impossible to easily check for empty arrays Issue Type: Bug Affects Versions: PUP 4.4.2 Assignee: Unassigned Components: Language Created: 2016/05/02 4:44 AM Priority: Normal Reporter: Julien Pivotto Since 4.4.2 it is impossible to do the followinq: if $nodes =~ Array[Data,0,0] I get the following error: Error while evaluating a '[]' _expression_, An empty collection may not specify an element type 2 things here: 1. I would not expect such a change in a minor (.z) release 2. This change does not make sense. To me: [] =~ Array[String] [] =~ Array[Integer] With that change, it implies that Array[String] should always be Array[String,1]. It sounds not great.
Jira (PUP-6221) Add SemVer and SemVerRange types to the Puppet Type System
Title: Message Title Thomas Hallgren assigned an issue to Henrik Lindberg Puppet / PUP-6221 Add SemVer and SemVerRange types to the Puppet Type System Change By: Thomas Hallgren Assignee: Thomas Hallgren Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6221) Add SemVer and SemVerRange types to the Puppet Type System
Title: Message Title
Thomas Hallgren updated an issue
Puppet / PUP-6221
Add SemVer and SemVerRange types to the Puppet Type System
Change By:
Thomas Hallgren
Acceptance Criteria:
* An instance of SemVer can be created from a String* An instance of SemVer can be compared to another SemVer for magnitude (<, <=, >, >=) and equality (==, !=).* An instance of SemVerRange can answer if an instance of SemVer is within range (=\~, !\~)* An instance of SemVerRange can answer if a string representing a SemVer is within range (=\~, !\~)* An instance of SemVer matches against SemVerRange case options using range match semantics* A string matches against SemVerRange case options using range match semantics* A SemVer type can be bounded by one or many range expressions in string form.* An instance of SemVerRange can be created from a String* The intersection of multiple SemVerRange instances can form a new SemVerRange (ruby only) * The {{in}} operator answers if a SemVer is in a SemVerRange * The {{in}} operator answers if a string representing a SemVer is in a SemVerRange
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6221) Add SemVer and SemVerRange types to the Puppet Type System
Title: Message Title
Thomas Hallgren updated an issue
Puppet / PUP-6221
Add SemVer and SemVerRange types to the Puppet Type System
Change By:
Thomas Hallgren
Acceptance Criteria:
* An instance of SemVer can be created from a String* An instance of SemVer can be compared to another SemVer for magnitude (<, <=, >, >=) and equality (==, !=).* An instance of SemVerRange can answer if an instance of SemVer is within range (=\~, !\~)* An instance of SemVerRange can answer if a string representing a SemVer is within range (=\~, !\~)* An instance of SemVer matches against SemVerRange case options using range match semantics* A string matches against SemVerRange case options using range match semantics* A SemVer type can be bounded by a one or many range _expression_ expressions in string form.* An instance of SemVerRange can be created from a String* The intersection of multiple SemVerRange instances can form a new SemVerRange* The {{in}} operator answers if a SemVer is in a SemVerRange
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6221) Add SemVer and SemVerRange types to the Puppet Type System
Title: Message Title
Thomas Hallgren updated an issue
Puppet / PUP-6221
Add SemVer and SemVerRange types to the Puppet Type System
Change By:
Thomas Hallgren
Acceptance Criteria:
* An instance of SemVer can be created from a String* An instance of SemVer can be compared to another SemVer for magnitude (<, <=, >, >=) and equality (==, !=).* An instance of SemVerRange can answer if an instance of SemVer is within range (=\~, !\~)* An instance of SemVer matches against SemVerRange case options using range match semantics* A string matches against SemVerRange case options using range match semantics* A SemVer type can be bounded by a range _expression_ in string form.* An instance of SemVerRange can be created from a String* The intersection of multiple SemVerRange instances can form a new SemVerRange* The {{in}} operator answers if a SemVer is in a SemVerRange
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6221) Add SemVer and SemVerRange types to the Puppet Type System
Title: Message Title
Thomas Hallgren commented on PUP-6221
Re: Add SemVer and SemVerRange types to the Puppet Type System
The first _expression_ works. The second doesn't. This is analog to how String/Regexp works where:
case "abc" { /abc/ : { true } default : { false }}
yields true whereas:
case /abc/ { "abc" : { true } default : { false }}
yields false.
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send
