Jira (PUP-4483) Add NotUndefined type to the set of Puppet types

2015-04-29 Thread Thomas Hallgren (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Hallgren created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4483 
 
 
 
  Add NotUndefined type to the set of Puppet types  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2015/04/29 3:36 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Thomas Hallgren 
 
 
 
 
 
 
 
 
 
 
The Puppet type system has currently no way of defining a type with the meaning any value except undefined and hence no way of differentiating between a missing value and a given value of any type (the existing Any type accepts undef values). 
The problem becomes apparent when declaring a hash where certain entries must be present but the value is unrestricted. 
Adding a NotUndefined would resolve the issue but the solution is not ideal since the value then becomes restricted (it cannot be undef). It's still not possible to differentiate between a missing key and a key with the value undef. This differentiation can be significant when variants are using different sets of keys. 
To really solve the problem, we would need a way to declare a Struct key to be required or optional in addition to adding the NotUndef type. One way of doing this would be to check if the value is of type Optional, and if it is, consider the key to be optional. Optional[Any] would then be different from Any in that the former affects the key. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
   

Jira (FACT-965) facter doesn't run under jruby

2015-04-29 Thread Christopher Price (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christopher Price commented on  FACT-965 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: facter doesn't run under jruby  
 
 
 
 
 
 
 
 
 
 
Reading the scrollback: this seems like a decent path for now, but, for future consideration... 
All of the calls to facter that Peter Huene and Josh Cooper alluded to above (except for the ones that are effectively FQDN) fall into one of two categories, if I'm not mistaken: 
 

Used by the magic of the settings catalog
 

Side effect of the fact that the compiler loads all the provider code
 
 
Those are both things that we've said we want to get rid of in the not-too-distant future, correct? 
Obviously those are much more work than would be reasonable to take on right now, but in the long-term, it does seem like the vast majority of the occurrences are just implicit things, and that maybe it should still be a long-term goal to get rid of the dependency altogether? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-4483) Add NotUndef type to the set of Puppet types

2015-04-29 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4483 
 
 
 
  Add NotUndef type to the set of Puppet types  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Summary:
 
 Add NotUndefined NotUndef typetothesetofPuppettypes 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-4483) Add NotUndef type to the set of Puppet types

2015-04-29 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4483 
 
 
 
  Add NotUndef type to the set of Puppet types  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 
 
 
 
 
 
 
 ThePuppettypesystemhascurrentlynowayofdefiningatypewiththemeaninganyvalueexceptundefinedandhencenowayofdifferentiatingbetweenamissingvalueandagivenvalueofanytype(theexisting{{Any}}typeaccepts{{undef}}values).Theproblembecomesapparentwhendeclaringahashwherecertainentriesmustbepresentbutthevalueisunrestricted.Addinga{{ NotUndefined NotUndef }}wouldresolvetheissuebutthesolutionisnotidealsincethevaluethenbecomesrestricted(itcannotbe{{undef}}).It'sstillnotpossibletodifferentiatebetweenamissingkeyandakeywiththevalueundef.Thisdifferentiationcanbesignificantwhenvariantsareusingdifferentsetsofkeys.Toreallysolvetheproblem,wewouldneedawaytodeclarea{{Struct}}keytoberequiredoroptionalinadditiontoaddingthe{{NotUndef}}type.Onewayofdoingthiswouldbetocheckifthevalueisoftype{{Optional}},andifitis,considerthekeytobeoptional.{{Optional[Any]}}wouldthenbedifferentfrom{{Any}}inthattheformeraffectsthekey. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-4282) numeric comparison error

2015-04-29 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4282 
 
 
 
  numeric comparison error  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 
 
 
 
 
 
 
 Testcode: {code:puppet} {$num50=5.0$x=$::memorysize_mb*1000ifis_float($x){notify{xisafloat:}}ifis_float($num50){notify{num50isafloat:}}#if($::x=$num50)#{notify{$xgreaterorequalto$num50:}}#else#{notify{$xlessthanthan$num50:}}} {code} Produces {code} Notice:xisafloatNotice:num50isafloat {code} OK.UncommentthecomparisonlinesandIgetanerror: {code} Error:Couldnotretrievecatalogfromremoteserver:Error400onSERVER:EvaluationError:Comparisonof:#Puppet::Pops::Model::ModelLabelProvider:0x9b771f0=Float,isnotpossible.Causedby'OnlyStringsandNumbersarecomparable'. {code} h2.QARiskAnalysisN/Aforunreproduciblebugs 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PDB-1463) PR (178): Add a parameter to manage or not the PostgreSQL database - roidelapluie

2015-04-29 Thread gepetto-bot (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 gepetto-bot commented on  PDB-1463 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: PR (178): Add a parameter to manage or not the PostgreSQL database - roidelapluie  
 
 
 
 
 
 
 
 
 
 
Pull request Add a parameter to manage or not the PostgreSQL database has been closed. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PDB-1463) PR (178): Add a parameter to manage or not the PostgreSQL database - roidelapluie

2015-04-29 Thread gepetto-bot (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 gepetto-bot commented on  PDB-1463 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: PR (178): Add a parameter to manage or not the PostgreSQL database - roidelapluie  
 
 
 
 
 
 
 
 
 
 
roidelapluie commented: 
server.pp inherits params as well so this pr is indeed not wanted. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PDB-1463) PR (178): Add a parameter to manage or not the PostgreSQL database - roidelapluie

2015-04-29 Thread gepetto-bot (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 gepetto-bot created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 PuppetDB /  PDB-1463 
 
 
 
  PR (178): Add a parameter to manage or not the PostgreSQL database - roidelapluie  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Task 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2015/04/29 2:25 AM 
 
 
 

Labels:
 

 github module 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 gepetto-bot 
 
 
 
 
 
 
 
 
 
 
Add a parameter to manage or not the PostgreSQL database 
 

Author: Julien Pivotto 
 

Company: Inuits
 

Github ID: roidelapluie
 

Pull Request 178 Discussion
 

Pull Request 178 File Diff
 
 
Pull Request Description 
 
 
(webhooks-id: 65e15feeb8e8c4c1f5958b3bb82fb8c5) 
 
 
 
  

Jira (PDB-1463) PR (178): Add a parameter to manage or not the PostgreSQL database - roidelapluie

2015-04-29 Thread gepetto-bot (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 gepetto-bot commented on  PDB-1463 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: PR (178): Add a parameter to manage or not the PostgreSQL database - roidelapluie  
 
 
 
 
 
 
 
 
 
 
Pull request Add a parameter to manage or not the PostgreSQL database has been reopened. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PDB-1463) PR (178): Add a parameter to manage or not the PostgreSQL database - roidelapluie

2015-04-29 Thread gepetto-bot (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 gepetto-bot commented on  PDB-1463 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: PR (178): Add a parameter to manage or not the PostgreSQL database - roidelapluie  
 
 
 
 
 
 
 
 
 
 
roidelapluie commented: 
But then params would not be initalized. repoening. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PDB-1463) PR (178): Add a parameter to manage or not the PostgreSQL database - roidelapluie

2015-04-29 Thread gepetto-bot (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 gepetto-bot commented on  PDB-1463 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: PR (178): Add a parameter to manage or not the PostgreSQL database - roidelapluie  
 
 
 
 
 
 
 
 
 
 
roidelapluie commented: 
This PR is obsolete, if you want not to manage the db then use include puppetdb::server instead of include puppetdb 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PDB-1463) PR (178): Add a parameter to manage or not the PostgreSQL database - roidelapluie

2015-04-29 Thread gepetto-bot (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 gepetto-bot commented on  PDB-1463 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: PR (178): Add a parameter to manage or not the PostgreSQL database - roidelapluie  
 
 
 
 
 
 
 
 
 
 
Pull request Add a parameter to manage or not the PostgreSQL database has been closed. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-4484) host resources are not idempotent

2015-04-29 Thread Geoff Williams (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Williams commented on  PUP-4484 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: host resources are not idempotent  
 
 
 
 
 
 
 
 
 
 
Testcase transcript: 
 
 
 
 
 
 
[geoff ~]# puppet apply host2.pp  
 
 
 
 
Notice: Compiled catalog for geoff.puppetlabs.vm in environment production in 0.03 seconds 
 
 
 
 
Notice: Finished catalog run in 0.03 seconds 
 
 
 
 
[geoff ~]# puppet apply host1.pp  
 
 
 
 
Notice: Compiled catalog for geoff.puppetlabs.vm in environment production in 0.03 seconds 
 
 
 
 
Notice: Finished catalog run in 0.03 seconds 
 
 
 
 
[geoff ~]# vi /etc/hosts 
 
 
 
 
  ... make the changes... 
 
 
 
 
[geoff ~]# puppet apply host1.pp  
 
 
 
 
Notice: Compiled catalog for geoff.puppetlabs.vm in environment production in 0.03 seconds 
 
 
 

Jira (PUP-4485) Add a 'hiera' data provider

2015-04-29 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4485 
 
 
 
  Add a 'hiera' data provider  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2015/04/29 6:04 AM 
 
 
 

Fix Versions:
 

 PUP 4.2.0 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Henrik Lindberg 
 
 
 
 
 
 
 
 
 
 
Add DataProvider subtypes for environment and module that is hiera like. This data type should read a 'hiera.yaml' from environment-root/hiera.yaml, or module-root/hiera.yaml, respectively. 
 

The hiera.yaml is a new version of the configuration file. It should include a version entry.
 

If the version is missing or set to a value  3, then the current (old) format is read and the semantics are retained (i.e. search with cartesian product of backends/hierarchy and only one data location per backend)
 

If the version is set, it must be 3 (or an error is raised)
 

The logger entry is not supported in either version - logging is always done using the Puppet logger
 

If an environment is using the hiera data 

Jira (PUP-4485) Add a 'hiera' data provider

2015-04-29 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4485 
 
 
 
  Add a 'hiera' data provider  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 
 
 
 
 
 
 
 AddDataProvidersubtypesforenvironmentandmodulethatishieralike.Thisdatatypeshouldreada'hiera.yaml'from{{environment-root/hiera.yaml}},or{{module-root/hiera.yaml}},respectively.*Thehiera.yamlisanewversionoftheconfigurationfile.Itshouldincludeaversionentry.*Iftheversionismissingorsettoavalue3,thenthecurrent(old)formatisreadandthesemanticsareretained(i.e.searchwithcartesianproductofbackends/hierarchyandonlyonedatalocationperbackend)*Iftheversionisset,itmustbe3(oranerrorisraised)*The{{logger}}entryisnotsupportedineitherversion-loggingisalwaysdoneusingthePuppetlogger*Ifanenvironmentisusingthehieradataproviderandhasno{{hiera.yaml}}fileadefaultconfigurationisusedcomparabletothecurrentdefaultconfigurationfilebutwithadatadirreferencing{{environment/data}}or{{moduleroot/data}}respectivelyforthetwokindsofproviders.Newconfigfileformat:---Thenewconfigfileformatbasicallymergesthebackendandhierarchysettingsintoonecommonstructure.{code:yaml}---:version:3:hierarchy:-{backend:{type:yaml,name:'yaml1',datadir:'somepath'}paths:-path-path}-{backend:{type:yaml,name:'yaml2',datadir:'someotherpath'}path:asinglepath}-{backend:-{type:yaml,name:'yaml3'}-{type:json,name:'json3'}datadir:commondatadirforallbackendsinthisentrypaths:-path-path}:datadir:'defaultdatadirpathifmissinginotherentries'{code}Thisexampleconfigurationfilehasthreeentriesinthehierarchy.Theentriesaresearchedfromtoptobottom.Anentrymayhaveoneormorebackends.Ifmultiplebackendsarespecified,theyaresearchedinorderusingacommonsetofpaths.Iftheyhavetheirownpaths,thosearesearchedbeforethecommonsetofpaths.Adatadirmaybespecifiedperbackend,ahierarchyentry,orforall.Thisactsasadefaultifamorespecificentrydoesnotspecifythedatadir.Thenameofanentryisusedforhumanexplainoutputasitisnotenoughtoidentifyabackendbytypealone.Thebackendsare*not*hierabackendsasspecifiedforhiera=2.0,theyaredataproviders.Eachinstantiateddataprovidergetsthedatadirandthepathsasarguments.Thismakesitpossibletouseotherkindsofprovidersthanfilebased-wheredatadirandpathsmaybeirrelevant,orbadnames.Asanexample,itisofvaluetobeabletouseafunction-itcoulddefaulttothe{{data}}function,butotherfunctionnamescouldbeusedaswellandsearchedjustlikeafilepathissearched.(Someelaborationanddecisionisneededonthemechanism/naming).*Cacheingandlifecycle*:Sincethefirstimplementationisonlyformodulesandenvironments,thedatashouldbecachedforeachcompilation(i.e.associatedwiththecatalog).Datafilesarenotwatched.*ValidationandSchema*:Thereshouldbeaschemafortheconfigurationfile,anditshouldbevalidatedwhenloaded.Thisismadedifficultifsupportisretainedfortheoldformat.Alternativelywesupplyautilitythatconvertshiera.yamlversion3toversion3.Thisshouldbeaverysimpletransformationthatalsohelpsuseruntangle/selectwhattheyreallywant(i.e.pruninguselesscombinationsthatarecreatedbythecurrentcartesianproductapproach).*Tobeelaboratedonanddecided* *DataProviderInfrastructure*:Inordertosupportdataprovidersthatperformhiera-likestringinterpolationthisfunctionalitymustbeavailableinsomeformtothosedataproviders. 
 
 
 
 
 
   

Jira (PUP-4485) Add a 'hiera' data provider

2015-04-29 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4485 
 
 
 
  Add a 'hiera' data provider  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Story Points:
 
 5 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PDB-1272) The -XX:+HeapDumpOnOutOfMemoryError parameter in /etc/sysconfig/puppetdb can cause crashes

2015-04-29 Thread Kenneth Barber (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kenneth Barber commented on  PDB-1272 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: The -XX:+HeapDumpOnOutOfMemoryError parameter in /etc/sysconfig/puppetdb can cause crashes  
 
 
 
 
 
 
 
 
 
 
Trevor Vaughan see my last response to this ticket. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-4484) host resources are not idempotent

2015-04-29 Thread Geoff Williams (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Williams created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4484 
 
 
 
  host resources are not idempotent  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 PUP 3.7.4 
 
 
 

Assignee:
 
 Kylo Ginsberg 
 
 
 

Attachments:
 

 host1.pp, host2.pp 
 
 
 

Components:
 

 Client 
 
 
 

Created:
 

 2015/04/29 5:45 AM 
 
 
 

Environment:
 
 
 
 
 
 
 
 
[geoff ~]# puppet --version 
 
 
 
 
3.7.4 (Puppet Enterprise 3.7.2) 
 
 
 
 
[geoff ~]# cat /etc/redhat-release  
 
 
 
 
CentOS release 6.6 (Final)
 
 

Jira (PUP-4484) host resources are not idempotent

2015-04-29 Thread Geoff Williams (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Williams updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4484 
 
 
 
  host resources are not idempotent  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Williams 
 
 
 

Attachment:
 
 host2.pp 
 
 
 

Attachment:
 
 host1.pp 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-4485) Add a 'hiera' data provider

2015-04-29 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4485 
 
 
 
  Add a 'hiera' data provider  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Issue Type:
 
 Bug NewFeature 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-4484) host resources are not idempotent

2015-04-29 Thread Geoff Williams (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Williams updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4484 
 
 
 
  host resources are not idempotent  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Williams 
 
 
 
 
 
 
 
 
 
 h2.OverviewThe{{host}}resourceisnotidempotentandcanfailsuddenlyinproductionifthe{{/etc/hosts}}fileisaltered*and*youwrittenPuppetcodethatdoesn'tsatisfytheprovider'sexpectationofmandatoryattributes.h2.ExpectedresultExecutingidenticalPuppetcodeshouldgiveanidempotentresult,itshouldeitheralwaysfailoralwayssucceedsothatuserscanhaveconfidenceintheirsystems.h2.ActualresultUndercertainconditionsanidenticallyconfigured{{host}}resourcethatwaspreviouslyworking(ormoreaccuratelynotraisinganerror)cansuddenlyfail,givingtheerrormessage:{{ipisarequiredattributeforhosts}}h2.Stepstoreproduce1.{{puppetapplyhost2.pp}}2.{{puppetapplyhost1.pp}}3.Manuallyedit{{/etc/hosts}}andremovetheentryfor{{testing.puppetlabs.vm}}4.{{puppetapplyhost1.pp}}Atthispointthepreviouslytestedandworkingcodewillgeneratetheaboveerrormessageh2.ProblemsthiscausesUserscouldpotentiallywrite_timebomb_codethatfailswhenentriesinthe{{/etc/hosts}}fileareremoved.Thisisparticularlytroublesomeas{{hosts}}entriesaretypicallyusedtoconfigurenetworkingandthiscouldconceivablycauseaserviceoutage,albeitonethatisduetoerrorsintheuser'sowncode.h2.ExplanationThe{{ip}}attributeismandatoryfor{{hosts}}resourcesbuttheproviderdoesn'tenforcethischeckunlessitneedstore-createtheresourceinquestion.h2.SuggestedfixMandatoryparametersshouldbecheckedbyprovidersatalltimes,notonlyaresourceneedstobere-created.Thiswillaidusersinwritingrobustcodeandwilllimittheopportunityforthisclassofproblemstoappearonproductionsystems. h2.WorkaroundUsersneedtorememberwhichattributesfor{{host}}resourcesaremandatoryandmustcodethemintotheirmanifests 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
  

Jira (PUP-4486) Add a JSON data provider

2015-04-29 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4486 
 
 
 
  Add a JSON data provider  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  New Feature 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2015/04/29 6:08 AM 
 
 
 

Fix Versions:
 

 PUP 4.2.0 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Henrik Lindberg 
 
 
 
 
 
 
 
 
 
 
Add a data provider for a JSON file. The provider is instantiated with a .json file representing a hash that is used to perform lookup. 
This implementation should be hiera-like in that it should perform interpolation as done by hiera version 2.0. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
   

Jira (PUP-4487) Add a YAML data provider

2015-04-29 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4487 
 
 
 
  Add a YAML data provider  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  New Feature 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2015/04/29 6:12 AM 
 
 
 

Fix Versions:
 

 PUP 4.2.0 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Henrik Lindberg 
 
 
 
 
 
 
 
 
 
 
Add a data provider for a yaml file. The data provider is instantiated with a .yaml file. This implementation should be hiera-like and perform interpolation as in hiera version 2.0. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 


Jira (PUP-4483) Add NotUndef type to the set of Puppet types

2015-04-29 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-4483 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Add NotUndef type to the set of Puppet types  
 
 
 
 
 
 
 
 
 
 
We have one more option, and that is to allow a richer specification on the key side. That feels more natural as we are basically adding a constraint on the key. Currently, the Struct type only accepts string keys, but it could accept something else. 
A: Currently the use of a string key can be seen as a shorthand for Optional[Enum['key']], if we reverse the decision that a key is optional if value type is optional, we would instead treat key as shorthand for Enum['key'], and to make the key optional, user can write Optional[Enum['key']]. We could possible allow Optional[astring] be shorthand for Optional[Enum[astring]] to save some typing. 
B: If we keep the behavior that the key may be missing of the value type is optional, then we need a way to change that. We could then use the NotUndef type to do that - i.e. NotUndef[Enum['key']], possibly with shortened notation NotUndef['key']. 
I prefer option A) as I have always thought that the optionality of the value leaking into a constraint on the key is smelly. It is however difficult to change in puppet 4 since it is an API change. We can however add both options. A key can be entered as Optional['key'] or NotUndef['key'], where the NotUndef variant overrules the interpretation that an Optional value means key can be missing, and the use of an Optional key means that the key may be missing even if the value is not declared as being Optional. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-4487) Add a YAML data provider

2015-04-29 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4487 
 
 
 
  Add a YAML data provider  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Scrum Team:
 
 Language 
 
 
 

Story Points:
 
 1 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-4385) Can't write WOMANS HAT emoji with \uXXXX unicode escapes

2015-04-29 Thread Kurt Wall (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kurt Wall updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4385 
 
 
 
  Can't write WOMANS HAT emoji with \u unicode escapes  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kurt Wall 
 
 
 
 
 
 
 
 
 
 Unicodeincludesabunchof5+hexdigitcharactersnow;mostnotablyemoji,butIthinktheremightbesomerealhumanlanguagecharactersintheretoo.Puppet's\uescapesequencesdon'taccommodatethese.The5-digitversionsgettruncated,andthealternate2x4-digitformsresultinanerror.{code}notice(5digitunicode\u1f452hat)#prints:5digitunicodeá˝…2hat#notice(double4digitunicode\uD83D\uDC52hat)#ResultsinError:Couldnotparseforenvironmentproduction:invalidbytesequenceinUTF-8onnodemagpie.lannotice(literalhat)#worksfine{code} h2.QARiskAnalysis|Probability|Medium(anyoneusing5+byteunicodecharacters)||Impact|Medium(brokenUnicodesupportbreakspuppet)||RiskLevel|Medium||TestLevel|Spec| 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-4468) AIO Upgrade Module

2015-04-29 Thread Justin Stoller (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Justin Stoller commented on  PUP-4468 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: AIO Upgrade Module  
 
 
 
 
 
 
 
 
 
 
 

what are the versions of Puppet -

is
- (it) supports (3.x?)
 
We are only supporting upgrades from 3.8.0 to 4.y. There will be behavior differences when running on puppet  3.8 and = 4.0, though I don't think we need acceptance testing for that.
 
This question is for rspec-puppet testing. The module team runs specs via rspec-puppet and different versions of puppet are used like different versions of ruby. The version of puppet to install is passed into the Gemfile via the PUPPET_GEM_VERSION environment variable. See a good example of a Gemfile here. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-4468) AIO Upgrade Module

2015-04-29 Thread Justin Stoller (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Justin Stoller commented on  PUP-4468 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: AIO Upgrade Module  
 
 
 
 
 
 
 
 
 
 
One thing that just struct me was that usually in a request for a module pipeline there's a name for the module already. What will the name for the module be (and there's a convention assumed of being puppetlabs-module-name) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PDB-1462) vector-valued facts cause gc churn on update

2015-04-29 Thread Wyatt Alt (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wyatt Alt updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 PuppetDB /  PDB-1462 
 
 
 
  vector-valued facts cause gc churn on update  
 
 
 
 
 
 
 
 
 

Change By:
 
 Wyatt Alt 
 
 
 
 
 
 
 
 
 
 Whenavector-valuedfactisupdatedatindexzero,allsubsequentpaths(includingmapvaluepathsiftheelementsaremaps)mustupdate.Forexample,ifIhavealength1000vectorwithmapelementseachcontainingfourfields,aninsertionatthefrontofthevectorcauses4000pathstobeorphanedandGC'dintheexecutionofasinglereplace-factscommand.Thepresenceofafactortwoofthisnaturewillcausethecommandqueuetobackupandeventuallyimplodeinamoderately-sizedinstallation(testedat1knodes,15minuteruninterval,2000arrayelements,4mapelementseach,additionsordeletions2/3ofthetime)whenadditions/deletionstothevectorarefrequent.  Thisticketistobetterunderstandthecurrentlimitsand thinkofalternativestoourcurrentscheme documentthemifappropriate . 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PDB-1462) vector-valued facts cause gc churn on update

2015-04-29 Thread Wyatt Alt (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wyatt Alt updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 PuppetDB /  PDB-1462 
 
 
 
  vector-valued facts cause gc churn on update  
 
 
 
 
 
 
 
 
 

Change By:
 
 Wyatt Alt 
 
 
 

Priority:
 
 Major Normal 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-4468) AIO Upgrade Module

2015-04-29 Thread Kylo Ginsberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kylo Ginsberg commented on  PUP-4468 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: AIO Upgrade Module  
 
 
 
 
 
 
 
 
 
 
 

should it include testing against future parser and strict variables (enable Puppet 4 feature flags – default: yes)?
 
Initially I was thinking no, since future parser is no longer a setting in puppet 4. But since the module needs to run on a 3.8 agent where future parser might be enabled, I think it would be good to test. It might also be possible to test this in a unit test.
 
might be enabled = should be enabled. 
Specficially, the module will run on: 
 

3.8 with future parser
 

4.0
 
 
3.8 with current parser is not a supported/recommended way to run the module. That restriction doesn't need to be enforced, but can just be documented. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-4427) Rake Spec tests fail due to missing dependencies

2015-04-29 Thread Steve Barlow (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Steve Barlow updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4427 
 
 
 
  Rake Spec tests fail due to missing dependencies  
 
 
 
 
 
 
 
 
 

Change By:
 
 Steve Barlow 
 
 
 

Sprint:
 
 Client2015-05- 13 27 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-4492) Investigate: plan for module testing with puppet-agent

2015-04-29 Thread Kylo Ginsberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kylo Ginsberg created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4492 
 
 
 
  Investigate: plan for module testing with puppet-agent  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Task 
 
 
 

Assignee:
 
 Kylo Ginsberg 
 
 
 

Created:
 

 2015/04/29 8:42 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Kylo Ginsberg 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (FACT-975) PPC64LE architecture should be treated as PPC64 exactly

2015-04-29 Thread Sergey Shnaidman (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sergey Shnaidman commented on  FACT-975 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: PPC64LE architecture should be treated as PPC64 exactly  
 
 
 
 
 
 
 
 
 
 
https://github.com/puppetlabs/facter/pull/934 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-4493) AIO agent CSR extension not working with passenger

2015-04-29 Thread Eric Thompson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Thompson created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4493 
 
 
 
  AIO agent CSR extension not working with passenger  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2015/04/29 10:05 AM 
 
 
 

Priority:
 
  Critical 
 
 
 

Reporter:
 
 Eric Thompson 
 
 
 
 
 
 
 
 
 
 
acceptance is failing against passenger: AIO stable passenger with: 
 
 
 
 
 
 
--- expected 
 
 
 
 
+++ actual 
 
 
 
 
@@ -1 +1 @@ 
 
 
 
 
-{authenticated=remote, certname=l1hifu2f5tnlspm.delivery.puppetlabs.net-extensions, extensions={pp_uuid=b5e63090-5167-11e3-8f96-0800200c9a66, pp_instance_id=i-3fkva, 1.3.6.1.4.1.34380.1.2.1=db-server, 1.3.6.1.4.1.34380.1.2.2=webops}} 
 
 

Jira (PUP-4405) Ordering dependency exists between certificate_request_spec.rb and autosign_spec.rb

2015-04-29 Thread Steve Barlow (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Steve Barlow updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4405 
 
 
 
  Ordering dependency exists between certificate_request_spec.rb and autosign_spec.rb  
 
 
 
 
 
 
 
 
 

Change By:
 
 Steve Barlow 
 
 
 

Sprint:
 
 Client2015-05- 13 27 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-4465) Document PUP-4201 JSON logging via --logdest

2015-04-29 Thread Kurt Wall (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kurt Wall updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4465 
 
 
 
  Document PUP-4201 JSON logging via --logdest  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kurt Wall 
 
 
 

QA Contact:
 
 KurtWall 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-4465) Document PUP-4201 JSON logging via --logdest

2015-04-29 Thread Kurt Wall (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kurt Wall updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4465 
 
 
 
  Document PUP-4201 JSON logging via --logdest  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kurt Wall 
 
 
 
 
 
 
 
 
 
 PUP-4201addedsupportforspecifying{{--logdest/var/log/somefile.json}}andgettinga(partial)JSONarrayoflogmessageobjects.Thiswasn'tdocumented.Docsfor{{--logdest}}areinseveralfilesinlib/puppet/application/NAME.rb.Themostimportantonesareapply,agent,andmaster.Allthreeofthese,atleast,neededitstoreflectthenewfeature.ThisfeatureisquietenoughandoddenoughthatIbelieveupdatingthedescriptionof{{--logdest}}istheonlydocumentationweneed.  h2.QARiskAnalysis|Probability|Low||Impact|Low||RiskLevel|Low||TestLevel|Spec| 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-4468) AIO Upgrade Module

2015-04-29 Thread Justin Stoller (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Justin Stoller commented on  PUP-4468 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: AIO Upgrade Module  
 
 
 
 
 
 
 
 
 
 
From initial blush, I'd like to just go ahead and create the pipeline once we have a repo set up with the values listed above and then we can iterate if there's issues that arise. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-4385) Can't write WOMANS HAT emoji with \uXXXX unicode escapes

2015-04-29 Thread Kurt Wall (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kurt Wall updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4385 
 
 
 
  Can't write WOMANS HAT emoji with \u unicode escapes  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kurt Wall 
 
 
 

QA Contact:
 
 KurtWall 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-4468) AIO Upgrade Module

2015-04-29 Thread Justin Stoller (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Justin Stoller commented on  PUP-4468 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: AIO Upgrade Module  
 
 
 
 
 
 
 
 
 
 
It may be important to point out that the module team doesn't write bare rspec tests only rspec-puppet and beaker-rspec tests and they have refused any PRs that touch the underlying system. If there's going to be rspec tests that test the underlying operating system the module team's pipeline isn't going to work. There are tickets (related to QENG-1633) to set up module pipelines for the Window's team that are an amalgamation of the platform team's spec workflow and the module team's acceptance testing workflow. However that's a work in progress and isn't as well automated as the module team's workflow yet. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-4483) Add NotUndef type to the set of Puppet types

2015-04-29 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-4483 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Add NotUndef type to the set of Puppet types  
 
 
 
 
 
 
 
 
 
 
We had a discussion and agreed that NotUndef was the best name we could think of as it is explicit. We also agreed that it is of value to be able to have a type parameter - e.g NotUndef[T] and that this removes the validity of Undef if accepted by T. Also agreed is that an NotUndef without a type parameter means the same as NotUndef[Any] (which makes it very easy to implement. 
When dealing with construction of an NotUndef, it should also accept a type parameter being a String, to construct a String['the_string_value'] type, which cannot otherwise be directly constructed in the language - e.g. NotUndef[some_key] becomes NotUndef[String[some_key]] (although that type cannot be constructed directly in puppet). This is done to avoid having to construct an Enum with a single string value. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PDB-1019) respond with 503 when database is unavailable

2015-04-29 Thread Charlie Sharpsteen (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Charlie Sharpsteen commented on  PDB-1019 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: respond with 503 when database is unavailable  
 
 
 
 
 
 
 
 
 
 
Kenneth Barber: I think the issue here isn't with the retry behavior, but with the HTTP error code that is returned while PuppetDB is trying to establish a connection during startup. 
Generally, PuppetDB uses the 404 error code to indicate that a query did not match any data: 
 
 
 
 
 
 
#curl -i http://localhost:8080/v4/nodes/foo.bar.baz 
 
 
 
 
 
 
 
 
 
HTTP/1.1 404 Not Found 
 
 
 
 
Date: Wed, 29 Apr 2015 16:13:40 GMT 
 
 
 
 
Warning: v4 query API is experimental and may change without warning. For stability use the v3 api. 
 
 
 
 
Content-Type: application/json; charset=utf-8 
 
 
 
 
Content-Length: 59 
 
 
 
 
Server: Jetty(9.2.z-SNAPSHOT) 
 
 
 
 
 
 
 
 
 
{ 
   

Jira (PUP-4385) Can't write WOMANS HAT emoji with \uXXXX unicode escapes

2015-04-29 Thread Kurt Wall (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kurt Wall updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4385 
 
 
 
  Can't write WOMANS HAT emoji with \u unicode escapes  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kurt Wall 
 
 
 

QA Status:
 
 Reviewed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-4468) AIO Upgrade Module

2015-04-29 Thread Justin Stoller (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Justin Stoller commented on  PUP-4468 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: AIO Upgrade Module  
 
 
 
 
 
 
 
 
 
 
FWIW, there's also these docs that are important to scoping work with a supported module: 
 

RE Supported Release Process
 

Module Team Checklist
 

Intro to Module Team Practices and Tools
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-4475) Add explain-ability to the lookup and data provider APIs

2015-04-29 Thread Steve Barlow (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Steve Barlow updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4475 
 
 
 
  Add explain-ability to the lookup and data provider APIs  
 
 
 
 
 
 
 
 
 

Change By:
 
 Steve Barlow 
 
 
 

Scrum Team:
 
 Language 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-2315) function call error message about mis-matched arguments is hard to understand

2015-04-29 Thread Steve Barlow (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Steve Barlow updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-2315 
 
 
 
  function call error message about mis-matched arguments is hard to understand  
 
 
 
 
 
 
 
 
 

Change By:
 
 Steve Barlow 
 
 
 

Sprint:
 
 Language2015-03-04,Language2015-03-18,Language2015-04-29 ,Language2015-05-13 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-4458) Refactor validation of 4.x parameter signatures

2015-04-29 Thread Steve Barlow (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Steve Barlow updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4458 
 
 
 
  Refactor validation of 4.x parameter signatures  
 
 
 
 
 
 
 
 
 

Change By:
 
 Steve Barlow 
 
 
 

Sprint:
 
 Language2015-04-29 ,Language2015-05-13 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-2080) Support functions written in pp

2015-04-29 Thread Steve Barlow (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Steve Barlow updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-2080 
 
 
 
  Support functions written in pp  
 
 
 
 
 
 
 
 
 

Change By:
 
 Steve Barlow 
 
 
 

Sprint:
 
 Week2014-4-02to2014-4-09,Week2014-4-09to2014-4-16,Language2015-04-29 ,Language2015-05-13 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-4374) Splatting attributes into an amended attribute block isn't supported

2015-04-29 Thread Steve Barlow (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Steve Barlow updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4374 
 
 
 
  Splatting attributes into an amended attribute block isn't supported  
 
 
 
 
 
 
 
 
 

Change By:
 
 Steve Barlow 
 
 
 

Sprint:
 
 Language2015-04-29 ,Language2015-05-13 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-2630) Server-set global variables like $::environment get overwritten by client facts

2015-04-29 Thread Steve Barlow (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Steve Barlow updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-2630 
 
 
 
  Server-set global variables like $::environment get overwritten by client facts  
 
 
 
 
 
 
 
 
 

Change By:
 
 Steve Barlow 
 
 
 

Sprint:
 
 Language2015-04-29 ,Language2015-05-13 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-4461) manifest changes are ignored when using hiera_include

2015-04-29 Thread Steve Barlow (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Steve Barlow updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4461 
 
 
 
  manifest changes are ignored when using hiera_include  
 
 
 
 
 
 
 
 
 

Change By:
 
 Steve Barlow 
 
 
 

Sprint:
 
 Language2015-04-29 ,Language2015-05-13 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-4385) Can't write WOMANS HAT emoji with \uXXXX unicode escapes

2015-04-29 Thread Steve Barlow (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Steve Barlow updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4385 
 
 
 
  Can't write WOMANS HAT emoji with \u unicode escapes  
 
 
 
 
 
 
 
 
 

Change By:
 
 Steve Barlow 
 
 
 

Sprint:
 
 Language2015-04-29 ,Language2015-05-13 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-4463) split with just Regexp (unparameterized type) splits on whitespace

2015-04-29 Thread Steve Barlow (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Steve Barlow updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4463 
 
 
 
  split with just Regexp (unparameterized type) splits on whitespace  
 
 
 
 
 
 
 
 
 

Change By:
 
 Steve Barlow 
 
 
 

Sprint:
 
 Language2015-04-29 ,Language2015-05-13 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-3814) Duplicated error output

2015-04-29 Thread Steve Barlow (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Steve Barlow updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-3814 
 
 
 
  Duplicated error output  
 
 
 
 
 
 
 
 
 

Change By:
 
 Steve Barlow 
 
 
 

Sprint:
 
 Language2015-04-29 ,Language2015-05-13 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-4193) Add pattern matching to the Puppet DSL

2015-04-29 Thread Steve Barlow (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Steve Barlow updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4193 
 
 
 
  Add pattern matching to the Puppet DSL  
 
 
 
 
 
 
 
 
 

Change By:
 
 Steve Barlow 
 
 
 

Sprint:
 
 Language2015-04-29 ,Language2015-05-13 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-4438) Add required_repeated_param to 4.x function API

2015-04-29 Thread Steve Barlow (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Steve Barlow updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4438 
 
 
 
  Add required_repeated_param to 4.x function API  
 
 
 
 
 
 
 
 
 

Change By:
 
 Steve Barlow 
 
 
 

Scope Change Category:
 
 Found 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-4385) Can't write WOMANS HAT emoji with \uXXXX unicode escapes

2015-04-29 Thread Eric Thompson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Thompson assigned an issue to QA 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4385 
 
 
 
  Can't write WOMANS HAT emoji with \u unicode escapes  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Thompson 
 
 
 

Assignee:
 
 EricThompson QA 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-4462) Single backslash before $ blocks interpolation in heredoc with no escapes enabled

2015-04-29 Thread Steve Barlow (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Steve Barlow updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4462 
 
 
 
  Single backslash before $ blocks interpolation in heredoc with no escapes enabled  
 
 
 
 
 
 
 
 
 

Change By:
 
 Steve Barlow 
 
 
 

Sprint:
 
 Language2015-04-29 ,Language2015-05-13 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-4193) Add pattern matching to the Puppet DSL

2015-04-29 Thread Steve Barlow (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Steve Barlow assigned an issue to Eric Sorenson 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4193 
 
 
 
  Add pattern matching to the Puppet DSL  
 
 
 
 
 
 
 
 
 

Change By:
 
 Steve Barlow 
 
 
 

Assignee:
 
 EricSorenson 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-4458) Refactor validation of 4.x parameter signatures

2015-04-29 Thread Steve Barlow (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Steve Barlow updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4458 
 
 
 
  Refactor validation of 4.x parameter signatures  
 
 
 
 
 
 
 
 
 

Change By:
 
 Steve Barlow 
 
 
 

Scope Change Reason:
 
 Cameoutofimprovingerrormessagesticket-brokeitintomultipletickets 
 
 
 

Scope Change Category:
 
 Adopted 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-4463) split with just Regexp (unparameterized type) splits on whitespace

2015-04-29 Thread Steve Barlow (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Steve Barlow updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4463 
 
 
 
  split with just Regexp (unparameterized type) splits on whitespace  
 
 
 
 
 
 
 
 
 

Change By:
 
 Steve Barlow 
 
 
 

Scope Change Reason:
 
 FoundbyNick 
 
 
 

Scope Change Category:
 
 Found 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-4463) split with just Regexp (unparameterized type) splits on whitespace

2015-04-29 Thread Kurt Wall (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kurt Wall assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4463 
 
 
 
  split with just Regexp (unparameterized type) splits on whitespace  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kurt Wall 
 
 
 

Assignee:
 
 KurtWall 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-4385) Can't write WOMANS HAT emoji with \uXXXX unicode escapes

2015-04-29 Thread Kurt Wall (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kurt Wall assigned an issue to Kurt Wall 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4385 
 
 
 
  Can't write WOMANS HAT emoji with \u unicode escapes  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kurt Wall 
 
 
 

Assignee:
 
 QA KurtWall 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-3539) add additional spec tests to cover globbing ACL matches in fileserver.conf

2015-04-29 Thread Eric Thompson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Thompson updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-3539 
 
 
 
  add additional spec tests to cover globbing ACL matches in fileserver.conf  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Thompson 
 
 
 

Sprint:
 
 Language2015-06-10 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (HI-347) spec edge cases to ensure hiera lookup doesn't contain values from outside of hierarchy

2015-04-29 Thread Eric Thompson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Thompson updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Hiera /  HI-347 
 
 
 
  spec edge cases to ensure hiera lookup doesn't contain values from outside of hierarchy  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Thompson 
 
 
 

Sprint:
 
 Language2015-05- 13 27 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-4374) Splatting attributes into an amended attribute block isn't supported

2015-04-29 Thread Eric Thompson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Thompson updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4374 
 
 
 
  Splatting attributes into an amended attribute block isn't supported  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Thompson 
 
 
 
 
 
 
 
 
 
 Per[~henrik.lindberg]inemail,thisissupposedtowork...butittotallydoesn't.{code}notify{'first':}$myattrs={message=fromareferenceattributeblock}Notify[first]{*=$myattrs}#Error:Couldnotparseforenvironmentproduction:Theoperator'*='inanObjectisnotsupported.at/Users/nick/Documents/splat_reference.pp:5:17onnodemagpie.lannotify{'extra':*=$myattrs}#worksfine.Notify|title=='first'|{*=$myattrs}#Error:Couldnotparseforenvironmentproduction:InPuppet::Pops::Model::CollectExpression:CannotuseaPuppet::Pops::Model::AttributesOperationwhereaPuppet::Pops::Model::AttributeOperationisexpectedonnodemagpie.lan{code} h3.QAprobability:lowseverity:mediumtestlayer:unit 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-4493) AIO agent CSR extension not working with passenger

2015-04-29 Thread Josh Cooper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper commented on  PUP-4493 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: AIO agent CSR extension not working with passenger  
 
 
 
 
 
 
 
 
 
 
Interestingly this doesn't affect webrick. I hacked the setup steps to run against webrick and get: 
 
 
 
 
 
 
  * Create agent csr_attributes.yaml on mk7md30j6ndnegd.delivery.puppetlabs.net 
 
 
 
 
localhost $ scp /var/folders/2q/qhdc5tpx4knd4pjr1hdskmjcgn/T/beaker20150429-18265-ysq25g agent:/tmp/certificate_extensions.oS59S3/csr_attributes.yaml {:ignore = } 
 
 
 
 
 
 
 
 
 
  * Check in as mk7md30j6ndnegd.delivery.puppetlabs.net-extensions 
 
 
 
 
 
 
 
 
 
mk7md30j6ndnegd.delivery.puppetlabs.net (agent) 11:00:06$ env FACTER_TEST_DIR=/tmp/certificate_extensions.oS59S3/ puppet agent --test --server a4rcx5xdrwv9fwo.delivery.puppetlabs.net --waitforcert 0 --csr_attributes /tmp/certificate_extensions.oS59S3/csr_attributes.yaml --certname mk7md30j6ndnegd.delivery.puppetlabs.net-extensions --ssldir /tmp/certificate_extensions.oS59S3/ssldir 
 
 
 
 
Info: Creating a new SSL key for mk7md30j6ndnegd.delivery.puppetlabs.net-extensions 
 
 
 
 
Info: Caching certificate for ca 
 
 
 
 
Info: csr_attributes file loading from 

Jira (PUP-4385) Can't write WOMANS HAT emoji with \uXXXX unicode escapes

2015-04-29 Thread Eric Thompson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Thompson assigned an issue to Eric Thompson 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4385 
 
 
 
  Can't write WOMANS HAT emoji with \u unicode escapes  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Thompson 
 
 
 

Assignee:
 
 QA EricThompson 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-3814) Duplicated error output

2015-04-29 Thread Eric Thompson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Thompson commented on  PUP-3814 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Duplicated error output  
 
 
 
 
 
 
 
 
 
 
validated follow-up commit on ubuntu14.04 at SHA: 8964241 
 
 
 
 
 
 
[root@fv1nemlp2jj6fpm ~]# puppet apply double_error.pp 
 
 
 
 
Notice: Compiled catalog for fv1nemlp2jj6fpm.delivery.puppetlabs.net in environment production in 0.46 seconds 
 
 
 
 
Error: Validation of File[/tmp/content_file_test.Q634Dlmtime] failed: You cannot specify content when using checksum 'mtime' at /root/double_error.pp:1 
 
 
 
 
[root@fv1nemlp2jj6fpm ~]# cat double_error.pp 
 
 
 
 
file { '/tmp/content_file_test.Q634Dlmtime': content = 'This is the test file content', ensure = present, checksum = mtime }
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA 

Jira (PDB-1019) respond with 503 when database is unavailable

2015-04-29 Thread Kenneth Barber (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kenneth Barber commented on  PDB-1019 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: respond with 503 when database is unavailable  
 
 
 
 
 
 
 
 
 
 
Charlie Sharpsteen okay we get it . Look through the history, the original description is what I was commenting on. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-4374) Splatting attributes into an amended attribute block isn't supported

2015-04-29 Thread Eric Thompson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Thompson updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4374 
 
 
 
  Splatting attributes into an amended attribute block isn't supported  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Thompson 
 
 
 
 
 
 
 
 
 
 Per[~henrik.lindberg]inemail,thisissupposedtowork...butittotallydoesn't.{code}notify{'first':}$myattrs={message=fromareferenceattributeblock}Notify[first]{*=$myattrs}#Error:Couldnotparseforenvironmentproduction:Theoperator'*='inanObjectisnotsupported.at/Users/nick/Documents/splat_reference.pp:5:17onnodemagpie.lannotify{'extra':*=$myattrs}#worksfine.Notify|title=='first'|{*=$myattrs}#Error:Couldnotparseforenvironmentproduction:InPuppet::Pops::Model::CollectExpression:CannotuseaPuppet::Pops::Model::AttributesOperationwhereaPuppet::Pops::Model::AttributeOperationisexpectedonnodemagpie.lan{code}h3.QA risk:medium probability:low (passingawholeblock) severity:medium  (work-aroundsavailable,obviousproblem) testlayer:unit -integration 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-4374) Splatting attributes into an amended attribute block isn't supported

2015-04-29 Thread Eric Thompson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Thompson assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4374 
 
 
 
  Splatting attributes into an amended attribute block isn't supported  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Thompson 
 
 
 

Assignee:
 
 EricThompson 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-3814) Duplicated error output

2015-04-29 Thread Eric Thompson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Thompson assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-3814 
 
 
 
  Duplicated error output  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Thompson 
 
 
 

Assignee:
 
 EricThompson 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-3814) Duplicated error output

2015-04-29 Thread Eric Thompson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Thompson assigned an issue to Eric Thompson 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-3814 
 
 
 
  Duplicated error output  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Thompson 
 
 
 

Assignee:
 
 QA EricThompson 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-4463) split with just Regexp (unparameterized type) splits on whitespace

2015-04-29 Thread Kurt Wall (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kurt Wall updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4463 
 
 
 
  split with just Regexp (unparameterized type) splits on whitespace  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kurt Wall 
 
 
 
 
 
 
 
 
 
 Since4.0.0itispossibletogiveaRegexptypetosplit () tospecifythepattern onwhich tosplit on .SinceaRegexpwithouta parameter paramter (pattern)hasanundef/nilpattern,andthisisgivendirectlytotheRubyString#splitmethod,itistakentomeanspliton whitespace whitepsace .Thisisdifferentthatifthe pattern patter issetto the anemptystring,ortoanemptyregular_expression_wherethesplitismadeonnothing-i.e.betweeneverycharacter.Themostreasonable behavior wouldbeif{{Regexp}}and{{Regexp\['']}}resultsinthesameregular_expression_whileastypestheyaredifferentsinceRegexpacceptsanyotherRegexp,whileRegexp['']onlyacceptsthatspecificregexp. h2.QARiskAnalysis|Probability|Medium(howfrequentlydopeoplespltiwith{{Regexp}}?)||Impact|Low(unexpectedresultsbutnodataloss)||RiskLevel|Medium||TestLevel|Spec| 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-4468) AIO Upgrade Module

2015-04-29 Thread Justin Stoller (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Justin Stoller commented on  PUP-4468 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: AIO Upgrade Module  
 
 
 
 
 
 
 
 
 
 
A basic module pipeline is up here (with Ruby 1.8). I will enable it (and iterate on it) once dev is ready to go! 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-4374) Splatting attributes into an amended attribute block isn't supported

2015-04-29 Thread Eric Thompson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Thompson commented on  PUP-4374 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Splatting attributes into an amended attribute block isn't supported  
 
 
 
 
 
 
 
 
 
 
validated on ubuntu14.04 at master SHA:  
 
 
 
 
 
 
[root@fv1nemlp2jj6fpm ~]# puppet apply splat_attrs.pp 
 
 
 
 
Notice: Compiled catalog for fv1nemlp2jj6fpm.delivery.puppetlabs.net in environment production in 0.38 seconds 
 
 
 
 
Notice: from a reference attribute block 
 
 
 
 
Notice: /Stage[main]/Main/Notify[first]/message: defined 'message' as 'from a reference attribute block' 
 
 
 
 
Notice: from a reference attribute block 
 
 
 
 
Notice: /Stage[main]/Main/Notify[extra]/message: defined 'message' as 'from a reference attribute block' 
 
 
 
 
Notice: Applied catalog in 0.01 seconds 
 
 
 
 
[root@fv1nemlp2jj6fpm ~]# cat splat_attrs.pp 
 
 
 
 
notify {'first':} 
 
 
 
 
$myattrs = {message = from a 

Jira (PUP-4462) Single backslash before $ blocks interpolation in heredoc with no escapes enabled

2015-04-29 Thread Eric Thompson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Thompson assigned an issue to Eric Thompson 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4462 
 
 
 
  Single backslash before $ blocks interpolation in heredoc with no escapes enabled  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Thompson 
 
 
 

Assignee:
 
 QA EricThompson 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-4462) Single backslash before $ blocks interpolation in heredoc with no escapes enabled

2015-04-29 Thread Eric Thompson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Thompson updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4462 
 
 
 
  Single backslash before $ blocks interpolation in heredoc with no escapes enabled  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Thompson 
 
 
 
 
 
 
 
 
 
 Ran:{code}$thing=hitherenotice(@(ENDINTERP))Thisstringshouldbeabletointerpolatevariables,andallbackslashesshouldbeinterpretedasplainoldliteralbackslashes.Variablestandingapart:${thing}Variableenjambed:hey${thing}Variablewithsinglebackslashenjambed:\${thing}Variablewithdoublebackslashenjambed:\\${thing}ENDINTERP{code}Thesinglebackslashbeforethe$causesaproblem.I'mprettysurethisisagainst[thespecificationofheredocs|https://github.com/puppetlabs/puppet-specifications/blob/master/language/heredoc.md].Actualresult:{code}Notice:Scope(Class[main]):Thisstringshouldbeabletointerpolatevariables,andallbackslashesshouldbeinterpretedasplainoldliteralbackslashes.Variablestandingapart:hithereVariableenjambed:heyhithereVariablewithsinglebackslashenjambed:\${thing}Variablewithdoublebackslashenjambed:\\hithere{code}Expectedresult:{code}Notice:Scope(Class[main]):Thisstringshouldbeabletointerpolatevariables,andallbackslashesshouldbeinterpretedasplainoldliteralbackslashes.Variablestandingapart:hithereVariableenjambed:heyhithereVariablewithsinglebackslashenjambed:\hithereVariablewithdoublebackslashenjambed:\\hithere{code}3.7.5and4.0.0behaveidentically.Inaddition,ifanyescape(otherthan'$'escapes)areturnedon,italsoturnsonescapingof'$'.Thisiscausedbythesamefaultylogic.h3.QArisk:medium(validateonly)probability:low(singlebackslashdirectlybeforeinterpolationinppheredoc)severity:medium(obviousissue,workarounds)testlevel:  unit 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
   

Jira (PUP-4462) Single backslash before $ blocks interpolation in heredoc with no escapes enabled

2015-04-29 Thread Eric Thompson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Thompson commented on  PUP-4462 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Single backslash before $ blocks interpolation in heredoc with no escapes enabled  
 
 
 
 
 
 
 
 
 
 
Henrik Lindberg it looks like the spec tests for the PR for this is testing the escaped backslash case (two ) but not the single escaping of the interpolation (since with @END escapes are turned off)? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-4463) split with just Regexp (unparameterized type) splits on whitespace

2015-04-29 Thread Kurt Wall (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kurt Wall updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4463 
 
 
 
  split with just Regexp (unparameterized type) splits on whitespace  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kurt Wall 
 
 
 

QA Contact:
 
 KurtWall 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-4463) split with just Regexp (unparameterized type) splits on whitespace

2015-04-29 Thread Kurt Wall (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kurt Wall updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4463 
 
 
 
  split with just Regexp (unparameterized type) splits on whitespace  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kurt Wall 
 
 
 

QA Status:
 
 Reviewed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-4463) split with just Regexp (unparameterized type) splits on whitespace

2015-04-29 Thread Eric Thompson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Thompson updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4463 
 
 
 
  split with just Regexp (unparameterized type) splits on whitespace  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Thompson 
 
 
 
 
 
 
 
 
 
 Since4.0.0itispossibletogiveaRegexptypetosplit () tospecifythepattern onwhich tosplit on .SinceaRegexpwithouta paramter parameter (pattern)hasanundef/nilpattern,andthisisgivendirectlytotheRubyString#splitmethod,itistakentomeanspliton whitepsace whitespace .Thisisdifferentthatifthe patter pattern issetto the anemptystring,ortoanemptyregular_expression_wherethesplitismadeonnothing-i.e.betweeneverycharacter.Themostreasonable behavior wouldbeif{{Regexp}}and{{Regexp\['']}}resultsinthesameregular_expression_whileastypestheyaredifferentsinceRegexpacceptsanyotherRegexp,whileRegexp['']onlyacceptsthatspecificregexp. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-4465) Document PUP-4201 JSON logging via --logdest

2015-04-29 Thread Nicholas Fagerlund (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Nicholas Fagerlund commented on  PUP-4465 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Document PUP-4201 JSON logging via --logdest  
 
 
 
 
 
 
 
 
 
 
Sweet, looks good.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-1295) Yum provider purge target runs irrespective of package installation status

2015-04-29 Thread Peter Huene (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Peter Huene assigned an issue to Peter Huene 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-1295 
 
 
 
  Yum provider purge target runs irrespective of package installation status  
 
 
 
 
 
 
 
 
 

Change By:
 
 Peter Huene 
 
 
 

Assignee:
 
 PeterHuene 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-4374) Splatting attributes into an amended attribute block isn't supported

2015-04-29 Thread Eric Thompson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Thompson updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4374 
 
 
 
  Splatting attributes into an amended attribute block isn't supported  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Thompson 
 
 
 

QA Status:
 
 Reviewed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-4461) manifest changes are ignored when using hiera_include

2015-04-29 Thread Eric Thompson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Thompson updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4461 
 
 
 
  manifest changes are ignored when using hiera_include  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Thompson 
 
 
 
 
 
 
 
 
 
 I'mexperimentingwithpuppetserver2/puppet-agent1andI'mrunningintoanissuewherechangestomanifestsdon'tgetpickedupbytheserver.WhenI'mmakingchangestoamanifestafterstartingpuppetserveritisworkingforthefirst2or3changesImake.Afterthatnewchangesdon'tgetpickedupanymoreuntilIrestartpuppetserver.Icanreproducethatbehavior.Foranexamplesessionsee:https://gist.github.com/roman-mueller/cf776fd180a085a551c2I'mrunning:CentOS7.0.1406(butalsoreproduceditonCentOS7.1.1503)puppetserver-2.0.0-1.el7.noarchpuppet-agent-1.0.0-1.el7.x86_64I'vesetenvironment_timeout=0intheproduction/environment.conf-whichalsoshouldbethedefault.Everythingelseiskeptondefaultsettingstoo.I'vecommittedmyexperimentalVagrantenvironmenthere:https://github.com/roman-mueller/puppet4-sandboxNotethatthisisusingvboxsfbutIgetthesamebehaviorwithlocalfiles.WhenI'mrunningstraceonthepuppetserverPIDIcanseeforthefirst2puppetagentrunsthatglobal/manifests/init.ppgetsaccessed.Afterthatitisnotgettingreadanymore.I'vealsowaited45minutes,butstillthechangewasnotpickedup.Onlyarestartofthepuppetserverfixesitatthatpoint.h3.QArisk:medium( manual validate onlyfornow )probability:medium(hiera_includepickingupmanifestchangesdownstreamonly)severity:medium(changesnotpickedup,confusingbutpossiblynotblocking)testlevel:  acceptance(weshouldupdateexistingacceptancetoensureanalteredmanifestispickedup) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message 

Jira (PUP-4462) Single backslash before $ blocks interpolation in heredoc with no escapes enabled

2015-04-29 Thread Eric Thompson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Thompson updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4462 
 
 
 
  Single backslash before $ blocks interpolation in heredoc with no escapes enabled  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Thompson 
 
 
 
 
 
 
 
 
 
 Ran:{code}$thing=hitherenotice(@(ENDINTERP))Thisstringshouldbeabletointerpolatevariables,andallbackslashesshouldbeinterpretedasplainoldliteralbackslashes.Variablestandingapart:${thing}Variableenjambed:hey${thing}Variablewithsinglebackslashenjambed:\${thing}Variablewithdoublebackslashenjambed:\\${thing}ENDINTERP{code}Thesinglebackslashbeforethe$causesaproblem.I'mprettysurethisisagainst[thespecificationofheredocs|https://github.com/puppetlabs/puppet-specifications/blob/master/language/heredoc.md].Actualresult:{code}Notice:Scope(Class[main]):Thisstringshouldbeabletointerpolatevariables,andallbackslashesshouldbeinterpretedasplainoldliteralbackslashes.Variablestandingapart:hithereVariableenjambed:heyhithereVariablewithsinglebackslashenjambed:\${thing}Variablewithdoublebackslashenjambed:\\hithere{code}Expectedresult:{code}Notice:Scope(Class[main]):Thisstringshouldbeabletointerpolatevariables,andallbackslashesshouldbeinterpretedasplainoldliteralbackslashes.Variablestandingapart:hithereVariableenjambed:heyhithereVariablewithsinglebackslashenjambed:\hithereVariablewithdoublebackslashenjambed:\\hithere{code}3.7.5and4.0.0behaveidentically.Inaddition,ifanyescape(otherthan'$'escapes)areturnedon,italsoturnsonescapingof'$'.Thisiscausedbythesamefaultylogic. h3.QArisk:medium(validateonly)probability:low(singlebackslashdirectlybeforeinterpolationinppheredoc)severity:medium(obviousissue,workarounds)testlevel: 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
  

Jira (PUP-4462) Single backslash before $ blocks interpolation in heredoc with no escapes enabled

2015-04-29 Thread Eric Thompson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Thompson commented on  PUP-4462 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Single backslash before $ blocks interpolation in heredoc with no escapes enabled  
 
 
 
 
 
 
 
 
 
 
validated on ubuntu14.04 at master SHA: 8964241 
 
 
 
 
 
 
[root@fv1nemlp2jj6fpm puppet]# puppet apply interp_heredoc.pp 
 
 
 
 
Notice: Scope(Class[main]): Variable standing apart: hi there 
 
 
 
 
Variable enjambed: heyhi there 
 
 
 
 
Variable with single backslash enjambed: \hi there 
 
 
 
 
Variable with double backslash enjambed: \\hi there 
 
 
 
 
 
 
 
 
 
Notice: Compiled catalog for fv1nemlp2jj6fpm.delivery.puppetlabs.net in environment production in 0.40 seconds 
 
 
 
 
Notice: Applied catalog in 0.02 seconds 
 
 
 
 
[root@fv1nemlp2jj6fpm puppet]# cat interp_heredoc.pp 
 
 
 
 
$thing = hi there 
 

Jira (PUP-4374) Splatting attributes into an amended attribute block isn't supported

2015-04-29 Thread Eric Thompson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Thompson assigned an issue to Eric Thompson 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4374 
 
 
 
  Splatting attributes into an amended attribute block isn't supported  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Thompson 
 
 
 

Assignee:
 
 QA EricThompson 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-4461) manifest changes are ignored when using hiera_include

2015-04-29 Thread Eric Thompson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Thompson assigned an issue to Eric Thompson 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4461 
 
 
 
  manifest changes are ignored when using hiera_include  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Thompson 
 
 
 

Assignee:
 
 QA EricThompson 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-4462) Single backslash before $ blocks interpolation in heredoc with no escapes enabled

2015-04-29 Thread Eric Thompson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Thompson updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4462 
 
 
 
  Single backslash before $ blocks interpolation in heredoc with no escapes enabled  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Thompson 
 
 
 

QA Status:
 
 Reviewed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-4462) Single backslash before $ blocks interpolation in heredoc with no escapes enabled

2015-04-29 Thread Eric Thompson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Thompson updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4462 
 
 
 
  Single backslash before $ blocks interpolation in heredoc with no escapes enabled  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Thompson 
 
 
 

QA Contact:
 
 EricThompson 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PDB-587) Add API support for CORS

2015-04-29 Thread Bruce Lysik (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Bruce Lysik commented on  PDB-587 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Add API support for CORS  
 
 
 
 
 
 
 
 
 
 
Blocker bug is closed. Is it possible for this to be added now? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-4463) split with just Regexp (unparameterized type) splits on whitespace

2015-04-29 Thread Kurt Wall (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kurt Wall assigned an issue to Kurt Wall 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4463 
 
 
 
  split with just Regexp (unparameterized type) splits on whitespace  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kurt Wall 
 
 
 

Assignee:
 
 EricThompson KurtWall 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-4374) Splatting attributes into an amended attribute block isn't supported

2015-04-29 Thread Eric Thompson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Thompson updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4374 
 
 
 
  Splatting attributes into an amended attribute block isn't supported  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Thompson 
 
 
 

QA Contact:
 
 EricThompson 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-4493) AIO agent CSR extension not working with passenger

2015-04-29 Thread Josh Cooper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper assigned an issue to Josh Cooper 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4493 
 
 
 
  AIO agent CSR extension not working with passenger  
 
 
 
 
 
 
 
 
 

Change By:
 
 Josh Cooper 
 
 
 

Assignee:
 
 JoshCooper 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-4461) manifest changes are ignored when using hiera_include

2015-04-29 Thread Eric Thompson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Thompson updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4461 
 
 
 
  manifest changes are ignored when using hiera_include  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Thompson 
 
 
 
 
 
 
 
 
 
 I'mexperimentingwithpuppetserver2/puppet-agent1andI'mrunningintoanissuewherechangestomanifestsdon'tgetpickedupbytheserver.WhenI'mmakingchangestoamanifestafterstartingpuppetserveritisworkingforthefirst2or3changesImake.Afterthatnewchangesdon'tgetpickedupanymoreuntilIrestartpuppetserver.Icanreproducethatbehavior.Foranexamplesessionsee:https://gist.github.com/roman-mueller/cf776fd180a085a551c2I'mrunning:CentOS7.0.1406(butalsoreproduceditonCentOS7.1.1503)puppetserver-2.0.0-1.el7.noarchpuppet-agent-1.0.0-1.el7.x86_64I'vesetenvironment_timeout=0intheproduction/environment.conf-whichalsoshouldbethedefault.Everythingelseiskeptondefaultsettingstoo.I'vecommittedmyexperimentalVagrantenvironmenthere:https://github.com/roman-mueller/puppet4-sandboxNotethatthisisusingvboxsfbutIgetthesamebehaviorwithlocalfiles.WhenI'mrunningstraceonthepuppetserverPIDIcanseeforthefirst2puppetagentrunsthatglobal/manifests/init.ppgetsaccessed.Afterthatitisnotgettingreadanymore.I'vealsowaited45minutes,butstillthechangewasnotpickedup.Onlyarestartofthepuppetserverfixesitatthatpoint. h3.QArisk:medium(validate)probability:medium(hiera_includepickingupmanifestchangesdownstreamonly)severity:medium(changesnotpickedup,confusingbutpossiblynotblocking)testlevel: 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and 

Jira (PUP-4461) manifest changes are ignored when using hiera_include

2015-04-29 Thread Eric Thompson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Thompson updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4461 
 
 
 
  manifest changes are ignored when using hiera_include  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Thompson 
 
 
 

QA Contact:
 
 ErikDasher EricThompson 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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.


  1   2   3   >