Jira (PUP-5983) Environment Data Provider has different from Hiera alias interpolation behavior

2016-02-26 Thread Andrey Galkin (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andrey Galkin created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5983 
 
 
 
  Environment Data Provider has different from Hiera alias interpolation behavior  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 PUP 4.3.2 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 Puppet Server 
 
 
 

Created:
 

 2016/02/26 8:58 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Andrey Galkin 
 
 
 
 
 
 
 
 
 
 
I haven't found duplicate reports of this. 


YAML Sample:
 
 
 
 
 
 
 
--- 
 
 
 
 
somevar: 
 
 

Jira (PUP-3985) With `storeconfigs = false` there are no warnings or errors about exported resources

2016-02-26 Thread Zee Alexander (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Zee Alexander commented on  PUP-3985 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: With `storeconfigs = false` there are no warnings or errors about exported resources  
 
 
 
 
 
 
 
 
 
 
I'm not certain. I'm not going to have a chance to validate any time soon though, I'm afraid. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-5844) Add the Object type to the Puppet Type system

2016-02-26 Thread Thomas Hallgren (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Hallgren commented on  PUP-5844 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Add the Object type to the Puppet Type system  
 
 
 
 
 
 
 
 
 
 
Just for the record Henrik Lindberg, we didn't decide. You did, after concluding that matters of taste was not worth discussing further. I'm fine with that because we have to move on, but in my view, turning this: 
 
 
 
 
 
 
Object[{ 
 
 
 
 
  parent => ParentType, 
 
 
 
 
  attributes =>  {  
 
 
 
 
a => String,  
 
 
 
 
b => Undef[String], 
 
 
 
 
c => String, 
 
 
 
 
d => Undef[String] 
 
 
 
 
 } 
 
 
 
 
}]
 
 
 
 
 
 
 
into this: 
 
 
 
 
 

Jira (FACT-1348) Remove usage of win32-security gem in Facter 2.x

2016-02-26 Thread Ethan Brown (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ethan Brown assigned an issue to qa 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1348 
 
 
 
  Remove usage of win32-security gem in Facter 2.x  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ethan Brown 
 
 
 

Status:
 
 Ready for  CI  Test 
 
 
 

Assignee:
 
 Ethan Brown qa 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-5025) Package resource showing notice when ensure attribute contains Epoch tag

2016-02-26 Thread William Hopper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 William Hopper updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5025 
 
 
 
  Package resource showing notice when ensure attribute contains Epoch tag  
 
 
 
 
 
 
 
 
 

Change By:
 
 William Hopper 
 
 
 

Fix Version/s:
 
 PUP 4.3.0 
 
 
 

Fix Version/s:
 
 PUP 4.4.1 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-5025) Package resource showing notice when ensure attribute contains Epoch tag

2016-02-26 Thread William Hopper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 William Hopper commented on  PUP-5025 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Package resource showing notice when ensure attribute contains Epoch tag  
 
 
 
 
 
 
 
 
 
 
Since the fix for this was reverted, we're still in a state where epoch handling in DNF is broken, as it has always been for Yum. The fix for PUP-5802 is a step which we will want to take in addition to fixing the issues detailed in this reverted fix for the RPM provider. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-5802) Yum provider incorrectly computes epoch for RPM package versions

2016-02-26 Thread William Hopper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 William Hopper commented on  PUP-5802 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Yum provider incorrectly computes epoch for RPM package versions  
 
 
 
 
 
 
 
 
 
 
Last note: this fix is definitely the right thing, and we will need to come back to it when we are ready to fix the other issues surrounding it. The (reverted) fix for 

PUP-5025
 is probably another piece that needs to be solved at the same time. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-5981) Make DNF package provider the default for Fedora 23

2016-02-26 Thread William Hopper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 William Hopper updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5981 
 
 
 
  Make DNF package provider the default for Fedora 23  
 
 
 
 
 
 
 
 
 

Change By:
 
 William Hopper 
 
 
 

Scope Change Category:
 
 Found 
 
 
 

Scope Change Reason:
 
 Realized fedora 23 (newly supported) required this is function properly 
 
 
 

Story Points:
 
 1 
 
 
 

Sprint:
 
 Client 2016-03-09 (Burn CF) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-5714) Add a 'git' checksum type for file resource sources

2016-02-26 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5714 
 
 
 
  Add a 'git' checksum type for file resource sources  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Scrum Team:
 
 Client Platform 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-5938) windows, user to groupassign to local administrators failed

2016-02-26 Thread Ethan Brown (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ethan Brown commented on  PUP-5938 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: windows, user to groupassign to local administrators failed  
 
 
 
 
 
 
 
 
 
 
Alexander Wendland thanks for the report. We've recently made a number of changes  
 

Do you have any problem creating users that are not part of the local administrators group?
 

Is the behavior the same when you place that code in a manifest instead of executing inline with -e?
 

Can you rerun the first example with --trace --debug --verbose and post the complete output?
 
 
Thanks! 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-5844) Add the Object type to the Puppet Type system

2016-02-26 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5844 
 
 
 
  Add the Object type to the Puppet Type system  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 
 
 
 
 
 
 
 In the Puppet Core Type Model (PCore) that will be used to describe all serialization using the Puppet Type System it is essential to have an {{Object\[T]}} type that matches instances of user defined type {{T}}. We also need the run time abstract {{Object}} from which the concrete instances of user defined data types are derived.This work is also required to enable the full user defined type definition using the syntax:{code:puppet}type TypeName inherits SuperTypeName {  # attribute definitions }{code}Which will be added in a separate ticket.UpdateWe have decided (after many rounds of proposals) to use the following syntax for the Object type:{code:puppet} type T = Object[{ parent => < parent-type >,  attributes => {  }.  functions => {  },  equality => [  ],  order_by => [  ],}]{code}Those are the basic features that the Object will have. Additional features can be expected later (separate tickets) to handle invariants.ATTRIBUTESThe attributes feature is a map from name to Type for attributes that do not require a default value, or other special settings. For attributes where more than a type is required a hash is used.{code:puppet}attributes => {  name => Type,  name => {'type' => Type,  # the type of the valuedefault => 'default value literal',  }}{code}This shows one short form, and one long form attribute. Expect there to be additional properties that can be set on an attribute. The ability to define a {{derived}} (i.e. computed) attribute, and possibly to make at attribute be a constant (read-only). Separate tickets will be added for those.FUNCTIONSThe function feature has fewer properties. Basically this is a name to type map. {code:puppet}functions {  name => Callable[ ... ],  name => Callable[ ... ],}{code}If a long form is needed it is defined the same way as for attributes.EQUALITYEquality can be specified by giving a list of attributes that must be equal for two instances of the object to be considered equal. If not given. Equality s base on all regular fields (i.e. excluding derived/computed and constant value attributes).{code:puppet}equality => | 'a', 'b', 'c' ]{code}ORDER BYThe order of instances of the Object can be specified. If order is not stated instances are not comparable (they lack magnitude). To specify the natural order of object of this kind, an array of tuples {{\[, ]}} where  is the name of an attribute, and direction is {{Enum\[ascending, descending]}}.{code:puppet}order_by => [ ['name' 'ascending''], ['gold-handicap', 'descending' ]{code} IMPLEMENTATIONObject type's not bound to an implementation can be used (a dynamic/generic implementation), but the operations are then not available. For operations to be available there must be a binding beween an implementation type, and the Object type. Such a binding can be achieved in different ways.* via a special type alias that binds the object type to a Runtime type* via syntax to be added in a separate ticket that makes it possible to implement an object type in puppet.{code:puppet}type T = Object[{ ... } ]  # defines the Object type (the interface)type T = Runtime['ruby'', SomeModule::Somewhere::MyImplOfT 

Jira (PUP-5844) Add the Object type to the Puppet Type system

2016-02-26 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5844 
 
 
 
  Add the Object type to the Puppet Type system  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 
 
 
 
 
 
 
 In the Puppet Core Type Model (PCore) that will be used to describe all serialization using the Puppet Type System it is essential to have an {{Object\[T]}} type that matches instances of user defined type {{T}}. We also need the run time abstract {{Object}} from which the concrete instances of user defined data types are derived.This work is also required to enable the full user defined type definition using the syntax:{code:puppet}type TypeName inherits SuperTypeName {  # attribute definitions }{code}Which will be added in a separate ticket.UpdateWe have decided (after many rounds of proposals) to use the following syntax for the Object type:{code:puppet} type T = Object[{ parent => < parent-type >,  attributes => {  }.  functions => {  },  equality => [  ],  order_by => [  ],}]{code} Those are the basic features that the Object will have. Additional features can be expected later (separate tickets) to handle invariants.ATTRIBUTESThe attributes feature is a map from name to Type for attributes that do not require a default value, or other special settings. For attributes where more than a type is required a hash is used.{code:puppet}attributes => {  name => Type,  name => {'type' => Type,  # the type of the valuedefault => 'default value literal',  }}{code}This shows one short form, and one long form attribute. Expect there to be additional properties that can be set on an attribute. The ability to define a {{derived}} (i.e. computed) attribute, and possibly to make at attribute be a constant (read-only). Separate tickets will be added for those.FUNCTIONSThe function feature has fewer properties. Basically this is a name to type map. {code:puppet}functions {  name => Callable[ ... ],  name => Callable[ ... ],}{code}If a long form is needed it is defined the same way as for attributes.EQUALITYEquality can be specified by giving a list of attributes that must be equal for two instances of the object to be considered equal. If not given. Equality s base on all regular fields (i.e. excluding derived/computed and constant value attributes).{code:puppet}equality => | 'a', 'b', 'c' ]{code}ORDER BYThe order of instances of the Object can be specified. If order is not stated instances are not comparable (they lack magnitude). To specify the natural order of object of this kind, an array of tuples {{\[, ]}} where  is the name of an attribute, and direction is {{Enum\[ascending, descending]}}.{code:puppet}order_by => [ ['name' 'acending''], ['gold-handicap', 'descending' ]{code} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 

Jira (FACT-1341) Facter Throws Unhandled Exception when Run Under Unicode User

2016-02-26 Thread Michael Smith (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Smith commented on  FACT-1341 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Facter Throws Unhandled Exception when Run Under Unicode User  
 
 
 
 
 
 
 
 
 
 
We should add a unit test based on the fix in Leatherman 0.4.0. We won't be able to merge until Leatherman 0.4.0 goes into puppet-agent. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-5844) Add the Object type to the Puppet Type system

2016-02-26 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5844 
 
 
 
  Add the Object type to the Puppet Type system  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 
 
 
 
 
 
 
 In the Puppet Core Type Model (PCore) that will be used to describe all serialization using the Puppet Type System it is essential to have an {{Object\[T]}} type that matches instances of user defined type {{T}}. We also need the run time abstract {{Object}} from which the concrete instances of user defined data types are derived.This work is also required to enable the full user defined type definition using the syntax:{code:puppet}type TypeName inherits SuperTypeName {  # attribute definitions }{code}Which will be added in a separate ticket.UpdateWe have decided (after many rounds of proposals) to use the following syntax for the Object type:{code:puppet} type T = Object[{ parent => < parent-type >,  attributes => {  }.  functions => {  },  equality => [  ],  order_by => [  ],}]{code}Those are the basic features that the Object will have. Additional features can be expected later (separate tickets) to handle invariants.ATTRIBUTESThe attributes feature is a map from name to Type for attributes that do not require a default value, or other special settings. For attributes where more than a type is required a hash is used.{code:puppet}attributes => {  name => Type,  name => {'type' => Type,  # the type of the valuedefault => 'default value literal',  }}{code}This shows one short form, and one long form attribute. Expect there to be additional properties that can be set on an attribute. The ability to define a {{derived}} (i.e. computed) attribute, and possibly to make at attribute be a constant (read-only). Separate tickets will be added for those.FUNCTIONSThe function feature has fewer properties. Basically this is a name to type map. {code:puppet}functions {  name => Callable[ ... ],  name => Callable[ ... ],}{code}If a long form is needed it is defined the same way as for attributes.EQUALITYEquality can be specified by giving a list of attributes that must be equal for two instances of the object to be considered equal. If not given. Equality s base on all regular fields (i.e. excluding derived/computed and constant value attributes).{code:puppet}equality => | 'a', 'b', 'c' ]{code}ORDER BYThe order of instances of the Object can be specified. If order is not stated instances are not comparable (they lack magnitude). To specify the natural order of object of this kind, an array of tuples {{\[, ]}} where  is the name of an attribute, and direction is {{Enum\[ascending, descending]}}.{code:puppet}order_by => [ ['name' ' acending ascending ''], ['gold-handicap', 'descending' ]{code} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 

Jira (PUP-5981) Make DNF package provider the default for Fedora 23

2016-02-26 Thread William Hopper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 William Hopper updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5981 
 
 
 
  Make DNF package provider the default for Fedora 23  
 
 
 
 
 
 
 
 
 

Change By:
 
 William Hopper 
 
 
 

Fix Version/s:
 
 PUP 4.4.1 
 
 
 

Fix Version/s:
 
 PUP 4.4.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-5802) Yum provider incorrectly computes epoch for RPM package versions

2016-02-26 Thread William Hopper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 William Hopper commented on  PUP-5802 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Yum provider incorrectly computes epoch for RPM package versions  
 
 
 
 
 
 
 
 
 
 
Issues on DNF: we successfully install the package (with the epoch) and then immediately compare the provided ensure value against an RPM query, where we don't inject the epoch, 
 
 
 
 
 
 
bundle exec puppet apply -e "package { 'tomcat': ensure => '1:7.0.59-4.fc22' }" --trace 
 
 
 
 
  
 
 
 
 
Error: Could not update: Failed to update to version 1:7.0.59-4.fc22, got version 7.0.59-4.fc22 instead 
 
 
 
 
/root/puppet/lib/puppet/provider/package/yum.rb:178:in `install' 
 
 
 
 
/root/puppet/lib/puppet/type/package.rb:126:in `block (3 levels) in ' 
 
 
 
 
/root/puppet/lib/puppet/property.rb:439:in `instance_eval' 
 
 
 
 
/root/puppet/lib/puppet/property.rb:439:in `set' 
 
 
 
 
/root/puppet/lib/puppet/property.rb:501:in `sync' 
 
 
 
 
... 
 
 
 
 
  

Jira (PUP-5844) Add the Object type to the Puppet Type system

2016-02-26 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5844 
 
 
 
  Add the Object type to the Puppet Type system  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 
 
 
 
 
 
 
 In the Puppet Core Type Model (PCore) that will be used to describe all serialization using the Puppet Type System it is essential to have an {{Object\[T]}} type that matches instances of user defined type {{T}}. We also need the run time abstract {{Object}} from which the concrete instances of user defined data types are derived.This work is also required to enable the full user defined type definition using the syntax:{code:puppet}type TypeName inherits SuperTypeName {  # attribute definitions }{code}Which will be added in a separate ticket.UpdateWe have decided (after many rounds of proposals) to use the following syntax for the Object type:{code:puppet}type T = Object[{ parent => < parent-type >,  attributes => {  }.  functions => {  },  equality => [  ],  order_by => [  ],}]{code} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-5844) Add the Object type to the Puppet Type system

2016-02-26 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5844 
 
 
 
  Add the Object type to the Puppet Type system  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 
 
 
 
 
 
 
 In the Puppet Core Type Model (PCore) that will be used to describe all serialization using the Puppet Type System it is essential to have an {{Object\[T]}} type that matches instances of user defined type {{T}}. We also need the run time abstract {{Object}} from which the concrete instances of user defined data types are derived.This work is also required to enable the full user defined type definition using the syntax:{code:puppet}type TypeName inherits SuperTypeName {  # attribute definitions }{code}Which will be added in a separate ticket.UpdateWe have decided (after many rounds of proposals) to use the following syntax for the Object type:{code:puppet}type T = Object[{  parent => < parent-type >,   attributes => {  } .   functions => {  } ,   equality => [  ] ,   order_by => [  ] , }]{code} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-5844) Add the Object type to the Puppet Type system

2016-02-26 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5844 
 
 
 
  Add the Object type to the Puppet Type system  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 
 
 
 
 
 
 
 In the Puppet Core Type Model (PCore) that will be used to describe all serialization using the Puppet Type System it is essential to have an {{Object\[T]}} type that matches instances of user defined type {{T}}. We also need the run time abstract {{Object}} from which the concrete instances of user defined data types are derived.This work is also required to enable the full user defined type definition using the syntax:{code:puppet}type TypeName inherits SuperTypeName {  # attribute definitions }{code}Which will be added in a separate ticket. UpdateWe have decided (after many rounds of proposals) to use the following syntax for the Object type:{code:puppet}type T = Object[{  attributes => {  }  functions => {  }  equality => [  ]  order_by => [  ]}]{code} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PDB-2474) PQL: explicit subqueries using fact 'value' doesn't join all types

2016-02-26 Thread Rob Browning (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Browning assigned an issue to Rob Browning 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2474 
 
 
 
  PQL: explicit subqueries using fact 'value' doesn't join all types  
 
 
 
 
 
 
 
 
 

Change By:
 
 Rob Browning 
 
 
 

Assignee:
 
 Rob Browning 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PDB-2381) Write a script to collect enough stats from customer DBs to define 'representative data'

2016-02-26 Thread Wyatt Alt (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wyatt Alt commented on  PDB-2381 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Write a script to collect enough stats from customer DBs to define 'representative data'  
 
 
 
 
 
 
 
 
 
 
moving to blocked on feedback from ops for now. I've got the application on github here: https://github.com/puppetlabs/pdb-data-server 
I created OPS-8226 to get feedback on what they'll need to deploy, then after that we can get coordinated with support. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-5911) Define the content of an .xpp file

2016-02-26 Thread Thomas Hallgren (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Hallgren commented on  PUP-5911 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Define the content of an .xpp file  
 
 
 
 
 
 
 
 
 
 
Using \n\n sounds like a good idea. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-5802) Yum provider incorrectly computes epoch for RPM package versions

2016-02-26 Thread William Hopper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 William Hopper updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5802 
 
 
 
  Yum provider incorrectly computes epoch for RPM package versions  
 
 
 
 
 
 
 
 
 

Change By:
 
 William Hopper 
 
 
 

Comment:
 
 We should probably revert this until we can figure out how to solve the underlying problem here. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-5981) Make DNF package provider the default for Fedora 23

2016-02-26 Thread William Hopper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 William Hopper updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5981 
 
 
 
  Make DNF package provider the default for Fedora 23  
 
 
 
 
 
 
 
 
 

Change By:
 
 William Hopper 
 
 
 

Summary:
 
 Make DNF  package  provider the default for Fedora 23 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PDB-2415) PuppetDB Should Reduce Use of Cascading Deletes and Updates In PostgreSQL

2016-02-26 Thread Ryan Senior (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ryan Senior assigned an issue to Ryan Senior 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2415 
 
 
 
  PuppetDB Should Reduce Use of Cascading Deletes and Updates In PostgreSQL  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ryan Senior 
 
 
 

Assignee:
 
 Ryan Senior 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-5981) Make DNF provider the default for Fedora 23

2016-02-26 Thread Michael Stahnke (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Stahnke commented on  PUP-5981 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Make DNF provider the default for Fedora 23  
 
 
 
 
 
 
 
 
 
 
It should be done for F23.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-5963) Recurse tidy resources totally fail

2016-02-26 Thread John Duarte (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Duarte commented on  PUP-5963 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Recurse tidy resources totally fail  
 
 
 
 
 
 
 
 
 
 
Validated using puppet-agent at e4f14a5 containing puppet at 6a1b004 on Debian 8 amd64. 
 
 
 
 
 
 
root@upwmn6959aegibe:~# mkdir -p /tmp/tidy/foo/bar/baz 
 
 
 
 
root@upwmn6959aegibe:~# puppet apply -e 'tidy { "/tmp/tidy/foo": matches => "*", recurse => true, rmdirs => true}' 
 
 
 
 
Notice: Compiled catalog for upwmn6959aegibe.delivery.puppetlabs.net in environment production in 0.05 seconds 
 
 
 
 
Notice: /Stage[main]/Main/Tidy[/tmp/tidy/foo]: Tidying 3 files 
 
 
 
 
Notice: /Stage[main]/Main/File[/tmp/tidy/foo/bar/baz]/ensure: removed 
 
 
 
 
Notice: /Stage[main]/Main/File[/tmp/tidy/foo/bar]/ensure: removed 
 
 
 
 
Notice: /Stage[main]/Main/File[/tmp/tidy/foo]/ensure: removed 
 
 
 
 
Notice: Applied catalog in 0.02 seconds 
 
 
 
 
root@upwmn6959aegibe:~# tree /tmp/tidy 
 
 
 
 
  

Jira (PUP-4748) Allow resources to be purged even when they have dependency relationships

2016-02-26 Thread John Duarte (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Duarte assigned an issue to John Duarte 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-4748 
 
 
 
  Allow resources to be purged even when they have dependency relationships  
 
 
 
 
 
 
 
 
 

Change By:
 
 John Duarte 
 
 
 

Assignee:
 
 qa John Duarte 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-5982) Acceptance: add test case for 'parser validate'

2016-02-26 Thread John Duarte (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Duarte created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5982 
 
 
 
  Acceptance: add test case for 'parser validate'  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Task 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/02/26 12:15 PM 
 
 
 

Fix Versions:
 

 PUP 4.4.1 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 John Duarte 
 
 
 
 
 
 
 
 
 
 
Currently there is no acceptance test for the 'parser validate' test that validates its functionality. 
The only acceptance test that uses this face at all is the validation that --parseonly returns a deprecation message. https://github.com/puppetlabs/puppet/blob/master/acceptance/tests/ticket_6928_puppet_master_parse_fails.rb 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 

Jira (PUP-5895) puppet parser validate fails for functions

2016-02-26 Thread John Duarte (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Duarte assigned an issue to John Duarte 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5895 
 
 
 
  puppet parser validate fails for functions  
 
 
 
 
 
 
 
 
 

Change By:
 
 John Duarte 
 
 
 

Assignee:
 
 qa John Duarte 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-5802) Yum provider incorrectly computes epoch for RPM package versions

2016-02-26 Thread William Hopper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 William Hopper commented on  PUP-5802 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Yum provider incorrectly computes epoch for RPM package versions  
 
 
 
 
 
 
 
 
 
 
Functional Review: 
Behavior on platforms with Yum as the default package provider seems to be unchanged. The spec test is fixed but as far as I can tell we still don't have the ability to deal with Epochs: 
 
 
 
 
 
 
[root@xelpsyph12ufrmd puppet]# bundle exec puppet apply -e "package {'logstash': ensure => '1:2.2.2-1' }" 
 
 
 
 
Notice: Compiled catalog for xelpsyph12ufrmd.delivery.puppetlabs.net in environment production in 0.51 seconds 
 
 
 
 
Error: Could not update: Execution of '/usr/bin/yum -d 0 -e 0 -y install logstash-1:2.2.2-1' returned 1: Error: Nothing to do 
 
 
 
 
Error: /Stage[main]/Main/Package[logstash]/ensure: change from purged to 1:2.2.2-1 failed: Could not update: Execution of '/usr/bin/yum -d 0 -e 0 -y install logstash-1:2.2.2-1' returned 1: Error: Nothing to do 
 
 
 
 
  
 
 
 
 
[root@xelpsyph12ufrmd puppet]# bundle exec puppet apply -e "package {'logstash': ensure => '2.2.2-1' }" 
 
 
 
 
Notice: Compiled catalog for xelpsyph12ufrmd.delivery.puppetlabs.net in environment production in 0.49 seconds 
 
 
 
 
Notice: /Stage[main]/Main/Package[logstash]/ensure: created
 
 
 
  

Jira (PUP-5802) Yum provider incorrectly computes epoch for RPM package versions

2016-02-26 Thread William Hopper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 William Hopper commented on  PUP-5802 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Yum provider incorrectly computes epoch for RPM package versions  
 
 
 
 
 
 
 
 
 
 
We should probably revert this until we can figure out how to solve the underlying problem here. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-5970) Add catalog_format to the catalog

2016-02-26 Thread Sean Griffin (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sean Griffin assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5970 
 
 
 
  Add catalog_format to the catalog  
 
 
 
 
 
 
 
 
 

Change By:
 
 Sean Griffin 
 
 
 

Assignee:
 
 Sean Griffin 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-5712) TypeParser cannot handle negative numbers

2016-02-26 Thread Josh Cooper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5712 
 
 
 
  TypeParser cannot handle negative numbers  
 
 
 
 
 
 
 
 
 

Change By:
 
 Josh Cooper 
 
 
 

Fix Version/s:
 
 PUP 4.3.3 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-5735) Remove usage of win32-security gem

2016-02-26 Thread Josh Cooper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5735 
 
 
 
  Remove usage of win32-security gem  
 
 
 
 
 
 
 
 
 

Change By:
 
 Josh Cooper 
 
 
 

Fix Version/s:
 
 PUP 4.3.3 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-4818) PUP-121 (relative namespacing) was never fully resolved in 3.x future parser

2016-02-26 Thread Josh Cooper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-4818 
 
 
 
  PUP-121 (relative namespacing) was never fully resolved in 3.x future parser  
 
 
 
 
 
 
 
 
 

Change By:
 
 Josh Cooper 
 
 
 

Fix Version/s:
 
 PUP 4.3.3 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-5571) Missing API docs for /puppet/v3/environment endpoint

2016-02-26 Thread Ryan Coleman (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ryan Coleman commented on  PUP-5571 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Missing API docs for /puppet/v3/environment endpoint  
 
 
 
 
 
 
 
 
 
 
Nicholas Fagerlund, sorry my comment was a bit of a drive-by.  
Realizing this is about release notes, I agree we do not want to publish release notes for a release going out to the door now. One of the next major focusses for the orchestration team is building out our own documentation, example content, and guides in prep for FOSS tooling. I'll include release notes for this endpoint as part of our work there.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-5472) Acceptance tests for lookup command

2016-02-26 Thread Josh Cooper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5472 
 
 
 
  Acceptance tests for lookup command  
 
 
 
 
 
 
 
 
 

Change By:
 
 Josh Cooper 
 
 
 

Fix Version/s:
 
 PUP 4.3.3 
 
 
 

Fix Version/s:
 
 PUP 4.4.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-5981) Make DNF provider the default for Fedora 23

2016-02-26 Thread William Hopper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 William Hopper created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5981 
 
 
 
  Make DNF provider the default for Fedora 23  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/02/26 11:50 AM 
 
 
 

Fix Versions:
 

 PUP 4.4.1 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 William Hopper 
 
 
 
 
 
 
 
 
 
 
We've added support for Fedora 23 but have not updated the DNF provider to make it the default. 
/cc Michael Stahnke Kenn Hussey 
If this needs to be done for 4.4.0 we'll need to know ASAP to get it in. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
  

Jira (PUP-5713) ClassInformationService.classes_per_environment errantly evaluates parameter default expression

2016-02-26 Thread Josh Cooper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5713 
 
 
 
  ClassInformationService.classes_per_environment errantly evaluates parameter default _expression_  
 
 
 
 
 
 
 
 
 

Change By:
 
 Josh Cooper 
 
 
 

Fix Version/s:
 
 PUP 4.3.3 
 
 
 

Fix Version/s:
 
 PUP 4.4.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-5571) Missing API docs for /puppet/v3/environment endpoint

2016-02-26 Thread David Lutterkort (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 David Lutterkort commented on  PUP-5571 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Missing API docs for /puppet/v3/environment endpoint  
 
 
 
 
 
 
 
 
 
 
We are still in the first situation, i.e., want to keep it under the radar for now. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-5963) Recurse tidy resources totally fail

2016-02-26 Thread John Duarte (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Duarte updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5963 
 
 
 
  Recurse tidy resources totally fail  
 
 
 
 
 
 
 
 
 

Change By:
 
 John Duarte 
 
 
 

QA Risk Assessment:
 
 Low 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-5963) Recurse tidy resources totally fail

2016-02-26 Thread John Duarte (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Duarte updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5963 
 
 
 
  Recurse tidy resources totally fail  
 
 
 
 
 
 
 
 
 

Change By:
 
 John Duarte 
 
 
 

QA Status:
 
 Reviewed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-5571) Missing API docs for /puppet/v3/environment endpoint

2016-02-26 Thread Nicholas Fagerlund (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Nicholas Fagerlund commented on  PUP-5571 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Missing API docs for /puppet/v3/environment endpoint  
 
 
 
 
 
 
 
 
 
 
 

If we want this endpoint to remain under the radar, and do not want people developing against it: then we don't need release notes around it.
 

If we want to encourage people developing against this endpoint: then we do need release notes.
 
 
Ryan Coleman I can't tell from your comment which of these situations we are in.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-5962) Restore monkey patch to Symbol

2016-02-26 Thread John Duarte (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Duarte updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5962 
 
 
 
  Restore monkey patch to Symbol  
 
 
 
 
 
 
 
 
 

Change By:
 
 John Duarte 
 
 
 

QA Risk Assessment Reason:
 
 Should be covered by unit tests 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-5962) Restore monkey patch to Symbol

2016-02-26 Thread John Duarte (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Duarte updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5962 
 
 
 
  Restore monkey patch to Symbol  
 
 
 
 
 
 
 
 
 

Change By:
 
 John Duarte 
 
 
 

QA Risk Assessment:
 
 Medium Low 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-5724) Backport PUP-5693 (benchmark function loading) to stable 4.3.3

2016-02-26 Thread Josh Cooper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper commented on  PUP-5724 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Backport PUP-5693 (benchmark function loading) to stable 4.3.3  
 
 
 
 
 
 
 
 
 
 
This one is a little different. We backported a fix to stable (for 4.3.3), but we are skipping that version and going to 4.4.0, which already contains the fix that we backported. However, since the merge to stable produced a unique commit, the backport is technically will be released in 4.4.0, so setting that as the fix version. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-5571) Missing API docs for /puppet/v3/environment endpoint

2016-02-26 Thread Ryan Coleman (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ryan Coleman commented on  PUP-5571 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Missing API docs for /puppet/v3/environment endpoint  
 
 
 
 
 
 
 
 
 
 
It's private now, but the goal is for would-be platform tool-builders to have a document for the environment catalog and the puppet-server endpoint for retrieving it. Don't know how to resolve that goal against this ticket though.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-5714) Add a 'git' checksum type for file resource sources

2016-02-26 Thread David Lutterkort (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 David Lutterkort commented on  PUP-5714 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Add a 'git' checksum type for file resource sources  
 
 
 
 
 
 
 
 
 
 
A middleground for avoiding redundant checksum computations would be to cache checksums server-side, and invalidate that cache everytime new code is pushed. The cache could either be populated lazily (i.e., only when the checksum for a certain file is actually needed) or eagerly (e.g., as part of updating code) This would incur one checksum calculation per file and code_id, rather than none, but would not require introducing a new checksum type into the agent. The cache could also be keyed off checksum type so that we can cache different kinds of checksums, e.g. md5 and mtime 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-5724) Backport PUP-5693 (benchmark function loading) to stable 4.3.3

2016-02-26 Thread Josh Cooper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5724 
 
 
 
  Backport PUP-5693 (benchmark function loading) to stable 4.3.3  
 
 
 
 
 
 
 
 
 

Change By:
 
 Josh Cooper 
 
 
 

Fix Version/s:
 
 PUP 4.3.3 
 
 
 

Fix Version/s:
 
 PUP 4.4.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-5726) Non-English values for USERNAME and USERPROFILE causes multiple home directories to be created

2016-02-26 Thread Josh Cooper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5726 
 
 
 
  Non-English values for USERNAME and USERPROFILE causes multiple home directories to be created  
 
 
 
 
 
 
 
 
 

Change By:
 
 Josh Cooper 
 
 
 

Fix Version/s:
 
 PUP 4.3.3 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-5736) Investigate use of win32-process gem with unicode paths

2016-02-26 Thread Josh Cooper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5736 
 
 
 
  Investigate use of win32-process gem with unicode paths  
 
 
 
 
 
 
 
 
 

Change By:
 
 Josh Cooper 
 
 
 

Fix Version/s:
 
 PUP 4.3.3 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-5728) Change default parsing of manifest files to UTF-8

2016-02-26 Thread Josh Cooper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5728 
 
 
 
  Change default parsing of manifest files to UTF-8  
 
 
 
 
 
 
 
 
 

Change By:
 
 Josh Cooper 
 
 
 

Fix Version/s:
 
 PUP 4.3.3 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-5752) Replace win32-process calls with internal API implementations that are wide-string compatible

2016-02-26 Thread Josh Cooper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5752 
 
 
 
  Replace win32-process calls with internal API implementations that are wide-string compatible  
 
 
 
 
 
 
 
 
 

Change By:
 
 Josh Cooper 
 
 
 

Fix Version/s:
 
 PUP 4.3.3 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-5752) Replace win32-process calls with internal API implementations that are wide-string compatible

2016-02-26 Thread Josh Cooper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5752 
 
 
 
  Replace win32-process calls with internal API implementations that are wide-string compatible  
 
 
 
 
 
 
 
 
 

Change By:
 
 Josh Cooper 
 
 
 

Fix Version/s:
 
 PUP 4.4.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-5761) when puppet module-level data provider function defines an unqualified key, puppet lookup returns nothing

2016-02-26 Thread Josh Cooper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5761 
 
 
 
  when puppet module-level data provider function defines an unqualified key, puppet lookup returns nothing  
 
 
 
 
 
 
 
 
 

Change By:
 
 Josh Cooper 
 
 
 

Fix Version/s:
 
 PUP 4.3.3 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-5744) Remove non-JSON safe default_literal objects from classes_per_environment response

2016-02-26 Thread Josh Cooper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5744 
 
 
 
  Remove non-JSON safe default_literal objects from classes_per_environment response  
 
 
 
 
 
 
 
 
 

Change By:
 
 Josh Cooper 
 
 
 

Fix Version/s:
 
 PUP 4.3.3 
 
 
 

Fix Version/s:
 
 PUP 4.4.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-5813) Fix memory-leaks caused by global variables holding on to environments

2016-02-26 Thread Josh Cooper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5813 
 
 
 
  Fix memory-leaks caused by global variables holding on to environments  
 
 
 
 
 
 
 
 
 

Change By:
 
 Josh Cooper 
 
 
 

Fix Version/s:
 
 PUP 4.3.3 
 
 
 

Fix Version/s:
 
 PUP 4.4.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-5824) Interpolation of an empty variable %{} or %{::} should yield an empty string

2016-02-26 Thread Josh Cooper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5824 
 
 
 
  Interpolation of an empty variable %{} or %{::} should yield an empty string  
 
 
 
 
 
 
 
 
 

Change By:
 
 Josh Cooper 
 
 
 

Fix Version/s:
 
 PUP 4.3.3 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-5741) Confusing error message for invalid types for comparison operations

2016-02-26 Thread Josh Cooper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5741 
 
 
 
  Confusing error message for invalid types for comparison operations  
 
 
 
 
 
 
 
 
 

Change By:
 
 Josh Cooper 
 
 
 

Fix Version/s:
 
 PUP 4.3.3 
 
 
 

Fix Version/s:
 
 PUP 4.4.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-5925) Optional data type and data binding with undef as default value

2016-02-26 Thread Josh Cooper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5925 
 
 
 
  Optional data type and data binding with undef as default value  
 
 
 
 
 
 
 
 
 

Change By:
 
 Josh Cooper 
 
 
 

Fix Version/s:
 
 PUP 4.3.3 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-5898) Data types seems to be messed up on hash parameters

2016-02-26 Thread Josh Cooper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5898 
 
 
 
  Data types seems to be messed up on hash parameters  
 
 
 
 
 
 
 
 
 

Change By:
 
 Josh Cooper 
 
 
 

Fix Version/s:
 
 PUP 4.3.3 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-5980) Fix "Puppet agent fails to write the graph if puppet agent has never run" issue for other faces

2016-02-26 Thread Brandon High (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Brandon High created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5980 
 
 
 
  Fix "Puppet agent fails to write the graph if puppet agent has never run" issue for other faces  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/02/26 11:35 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Brandon High 
 
 
 
 
 
 
 
 
 
 


PUP-2638
 fixed an issue where puppet apply failed to run when no puppet agent run had initially run after a puppet agent upgrade. This issue also needs to be fixed for the other puppet faces, such as resource. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 

Jira (PUP-5936) a given undef should set undef and not require a default expression of = undef

2016-02-26 Thread Josh Cooper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5936 
 
 
 
  a given undef should set undef and not require a default _expression_ of = undef  
 
 
 
 
 
 
 
 
 

Change By:
 
 Josh Cooper 
 
 
 

Fix Version/s:
 
 PUP 4.3.3 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-5835) Symbol in scope; puppet apply -e 'notify { $environment: }' raises an exception

2016-02-26 Thread Josh Cooper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5835 
 
 
 
  Symbol in scope; puppet apply -e 'notify { $environment: }' raises an exception  
 
 
 
 
 
 
 
 
 

Change By:
 
 Josh Cooper 
 
 
 

Fix Version/s:
 
 PUP 4.3.3 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-5970) Add catalog_format to the catalog

2016-02-26 Thread Sean Griffin (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sean Griffin updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5970 
 
 
 
  Add catalog_format to the catalog  
 
 
 
 
 
 
 
 
 

Change By:
 
 Sean Griffin 
 
 
 

QA Status:
 
 Reviewed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-5571) Missing API docs for /puppet/v3/environment endpoint

2016-02-26 Thread Josh Cooper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5571 
 
 
 
  Missing API docs for /puppet/v3/environment endpoint  
 
 
 
 
 
 
 
 
 
 
Marking this as not needing release notes, since this is a mostly a private interface? David Lutterkort Nicholas Fagerlund please update if that's incorrect. 
 
 
 
 
 
 
 
 
 

Change By:
 
 Josh Cooper 
 
 
 

Release Notes:
 
 Not Needed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-5390) Audit acceptance skips

2016-02-26 Thread Josh Cooper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5390 
 
 
 
  Audit acceptance skips  
 
 
 
 
 
 
 
 
 

Change By:
 
 Josh Cooper 
 
 
 

Release Notes:
 
 Not Needed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-2909) Incorporate linting and static verification with rubocop

2016-02-26 Thread Josh Cooper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-2909 
 
 
 
  Incorporate linting and static verification with rubocop  
 
 
 
 
 
 
 
 
 

Change By:
 
 Josh Cooper 
 
 
 

Release Notes:
 
 Not Needed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-2909) Incorporate linting and static verification with rubocop

2016-02-26 Thread Josh Cooper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-2909 
 
 
 
  Incorporate linting and static verification with rubocop  
 
 
 
 
 
 
 
 
 

Change By:
 
 Josh Cooper 
 
 
 

Scrum Team:
 
 Client Platform 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-5670) Tag the release and create packages (PUP 3.8.5)

2016-02-26 Thread Josh Cooper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5670 
 
 
 
  Tag the release and create packages (PUP 3.8.5)  
 
 
 
 
 
 
 
 
 

Change By:
 
 Josh Cooper 
 
 
 

Release Notes:
 
 Not Needed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-5390) Audit acceptance skips

2016-02-26 Thread Josh Cooper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5390 
 
 
 
  Audit acceptance skips  
 
 
 
 
 
 
 
 
 

Change By:
 
 Josh Cooper 
 
 
 

Fix Version/s:
 
 PUP 4.4.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-5496) Reenable PMT tests on some non-Windows platforms

2016-02-26 Thread Josh Cooper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5496 
 
 
 
  Reenable PMT tests on some non-Windows platforms  
 
 
 
 
 
 
 
 
 

Change By:
 
 Josh Cooper 
 
 
 

Fix Version/s:
 
 PUP 4.4.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-5571) Missing API docs for /puppet/v3/environment endpoint

2016-02-26 Thread Josh Cooper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5571 
 
 
 
  Missing API docs for /puppet/v3/environment endpoint  
 
 
 
 
 
 
 
 
 

Change By:
 
 Josh Cooper 
 
 
 

Fix Version/s:
 
 PUP 4.4.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-5569) acceptance: to ensure Resource Collectors can use resource references in search expressions

2016-02-26 Thread Josh Cooper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5569 
 
 
 
  acceptance: to ensure Resource Collectors can use resource references in search expressions  
 
 
 
 
 
 
 
 
 

Change By:
 
 Josh Cooper 
 
 
 

Fix Version/s:
 
 PUP 4.4.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-5819) Lexer should raise a better error when loading manifest files containing a UTF-8 BOM (Byte Order Mark)

2016-02-26 Thread Josh Cooper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5819 
 
 
 
  Lexer should raise a better error when loading manifest files containing a UTF-8 BOM (Byte Order Mark)  
 
 
 
 
 
 
 
 
 

Change By:
 
 Josh Cooper 
 
 
 

Fix Version/s:
 
 PUP 4.4.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-5897) Support Ubuntu 16.04 in systemd provider

2016-02-26 Thread Josh Cooper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5897 
 
 
 
  Support Ubuntu 16.04 in systemd provider  
 
 
 
 
 
 
 
 
 

Change By:
 
 Josh Cooper 
 
 
 

Fix Version/s:
 
 PUP 4.4.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-5911) Define the content of an .xpp file

2016-02-26 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-5911 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Define the content of an .xpp file  
 
 
 
 
 
 
 
 
 
 
ok, I can buy that, there is enough power there to describe the variations. Do you agree to the \n\n delimiter (one blank line) to ensure we have headroom should the need arise? (It is horribly difficult to add later, and the cost is one byte). 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-5962) Restore monkey patch to Symbol

2016-02-26 Thread John Duarte (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Duarte updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5962 
 
 
 
  Restore monkey patch to Symbol  
 
 
 
 
 
 
 
 
 

Change By:
 
 John Duarte 
 
 
 

QA Risk Assessment:
 
 Medium 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-5962) Restore monkey patch to Symbol

2016-02-26 Thread John Duarte (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Duarte updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5962 
 
 
 
  Restore monkey patch to Symbol  
 
 
 
 
 
 
 
 
 

Change By:
 
 John Duarte 
 
 
 

QA Status:
 
 Reviewed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-5962) Restore monkey patch to Symbol

2016-02-26 Thread John Duarte (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Duarte assigned an issue to John Duarte 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5962 
 
 
 
  Restore monkey patch to Symbol  
 
 
 
 
 
 
 
 
 

Change By:
 
 John Duarte 
 
 
 

Assignee:
 
 qa John Duarte 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-5802) Yum provider incorrectly computes epoch for RPM package versions

2016-02-26 Thread William Hopper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 William Hopper assigned an issue to William Hopper 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5802 
 
 
 
  Yum provider incorrectly computes epoch for RPM package versions  
 
 
 
 
 
 
 
 
 

Change By:
 
 William Hopper 
 
 
 

Assignee:
 
 qa William Hopper 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-5802) Yum provider incorrectly computes epoch for RPM package versions

2016-02-26 Thread John Duarte (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Duarte updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5802 
 
 
 
  Yum provider incorrectly computes epoch for RPM package versions  
 
 
 
 
 
 
 
 
 

Change By:
 
 John Duarte 
 
 
 

QA Risk Assessment:
 
 Medium 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-5802) Yum provider incorrectly computes epoch for RPM package versions

2016-02-26 Thread John Duarte (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Duarte updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5802 
 
 
 
  Yum provider incorrectly computes epoch for RPM package versions  
 
 
 
 
 
 
 
 
 

Change By:
 
 John Duarte 
 
 
 

QA Status:
 
 Reviewed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-5962) Restore monkey patch to Symbol

2016-02-26 Thread Josh Cooper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5962 
 
 
 
  Restore monkey patch to Symbol  
 
 
 
 
 
 
 
 
 

Change By:
 
 Josh Cooper 
 
 
 

Release Notes Summary:
 
 This restores the existing behavior in 4.3.x, so there is no change from end user perspective. 
 
 
 

Release Notes:
 
 Not Needed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-5970) Add catalog_format to the catalog

2016-02-26 Thread Josh Cooper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5970 
 
 
 
  Add catalog_format to the catalog  
 
 
 
 
 
 
 
 
 

Change By:
 
 Josh Cooper 
 
 
 

Release Notes Summary:
 
 Adds a "catalog_format" version field to the catalog identifying its schema. Newly compiled catalogs will have version 1. In the future, the version will be bumped if changes are made to the catalog format. This makes it possible to read a catalog in the future and know what data to expect. 
 
 
 

Release Notes:
 
 New Feature 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PDB-2252) PuppetDB should not be slurping all request bodies to a string

2016-02-26 Thread Russell Mull (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Russell Mull updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2252 
 
 
 
  PuppetDB should not be slurping all request bodies to a string  
 
 
 
 
 
 
 
 
 

Change By:
 
 Russell Mull 
 
 
 

Fix Version/s:
 
 PDB 3.2.4 
 
 
 

Fix Version/s:
 
 PDB 4.0.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-1606) Virtual classes are always realized

2016-02-26 Thread Eric Sorenson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Sorenson commented on  PUP-1606 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Virtual classes are always realized  
 
 
 
 
 
 
 
 
 
 
So I don't understand what it means (from a semantic/intent standpoint) for a class to be virtual/realized but I've been opposed to virtual resources since 0.25 so I'm probably not the best person to decide this. So Adam T Backer can i come back to your original problem statement? 
 
 I have a class that I wish to apply with a default set of parameters to all hosts, and a different set of parameters on a handful of management hosts (agents on all nodes, management bits on management nodes) and was hoping to provide it with the same class using virtualized class resources. [...] I will not entertain the idea of releasing my Nagios module in this state.
 
I just wouldn't look to virtual resources to solve this problem; this pattern is super common and data lookups via hiera is the first-class solution, especially for published modules. If you're still involved in this issue at all, do you still think the approach you were trying should be made to work? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (FACT-1352) Use Leatherman 0.4.0

2016-02-26 Thread Michael Smith (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Smith commented on  FACT-1352 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Use Leatherman 0.4.0  
 
 
 
 
 
 
 
 
 
 
Blocked on Facter release 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-5911) Define the content of an .xpp file

2016-02-26 Thread Thomas Hallgren (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Hallgren commented on  PUP-5911 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Define the content of an .xpp file  
 
 
 
 
 
 
 
 
 
 
I think that is overly verbose. The MIME type stats that it's JSON and pcore. What's left is the protocol used and a version. The latter should reside inside of the actual content (i.e. not an xpp file concern). 
 
 
 
 
 
 
#!/bin/viewpcore application/json+pcore
 
 
 
 
 
 
 
and, if there are several variants of json/pcore 
 
 
 
 
 
 
#!/bin/viewpcore application/json+pcore;debug=true
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to 

Jira (FACT-1352) Use Leatherman 0.4.0

2016-02-26 Thread Michael Smith (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Smith assigned an issue to Michael Smith 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1352 
 
 
 
  Use Leatherman 0.4.0  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Smith 
 
 
 

Assignee:
 
 Michael Smith 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (FACT-1352) Use Leatherman 0.4.0

2016-02-26 Thread Michael Smith (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Smith created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1352 
 
 
 
  Use Leatherman 0.4.0  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Task 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/02/26 9:47 AM 
 
 
 

Fix Versions:
 

 FACT 3.1.6 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Michael Smith 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to 

Jira (PUP-5844) Add the Object type to the Puppet Type system

2016-02-26 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-5844 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Add the Object type to the Puppet Type system  
 
 
 
 
 
 
 
 
 
 
I am fine with both statements (forbid derived attributes in equality, and always specify 'ascending'/'descending' as tuples). 
Do we have something outstanding regarding "uniquenes" or is that what I referred to as "equality" ? With that question answered I think I can update the description of this ticket to document what we decided. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-5970) Add catalog_format to the catalog

2016-02-26 Thread Sean Griffin (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sean Griffin assigned an issue to Sean Griffin 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5970 
 
 
 
  Add catalog_format to the catalog  
 
 
 
 
 
 
 
 
 

Change By:
 
 Sean Griffin 
 
 
 

Assignee:
 
 qa Sean Griffin 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-5911) Define the content of an .xpp file

2016-02-26 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-5911 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Define the content of an .xpp file  
 
 
 
 
 
 
 
 
 
 
If we use say application/json+pcore (which i like) then the protocol URI which defines which PCore model and serializer details that were used/should be used) needs to be in the Pcore serialization that follows. The "pcore" addition to the mime type does not include everything that needs to be known. We could keep it on the same line, or use multiple lines (as suggested above) to set additional properties. I.e. we could have 
 
 
 
 
 
 
#!/bin/viewpcore application/json+pcore 
 
 
 
 
protocol=http://puppet.com/pcore/serializer/readable_json_1_0.pcore 
 
 
 
 
  
 
 
 
 

 
 
 
 
 
 
 
where  indicates binary bytes or textual bytes 
Compare that against: 
 
 
 
 
 
 
#!/bin/viewpcore application/json+pcore 
 
 
 
 
protocol=http://puppet.com/pcore/serializer/machine_2_machine_json_1_0.pcore 
 
 
 
 
  
 
 
 
 

 
   

Jira (PUP-5768) Fix problematic usage of ENV for Windows

2016-02-26 Thread Glenn Sarti (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Glenn Sarti commented on  PUP-5768 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Fix problematic usage of ENV for Windows  
 
 
 
 
 
 
 
 
 
 
Created specs for testing the bad behavior 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-5844) Add the Object type to the Puppet Type system

2016-02-26 Thread Thomas Hallgren (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Hallgren commented on  PUP-5844 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Add the Object type to the Puppet Type system  
 
 
 
 
 
 
 
 
 
 
Yes, I agree. Equality is based on non-derived all attributes if nothing is specified, else on a list of attributes. It's illegal to include a derived attribute in that list. I think sort order should be kept as simple as possible. My preference would be a list of two element tuples (name and direction) with no exception. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-5970) Add catalog_format to the catalog

2016-02-26 Thread William Hopper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 William Hopper assigned an issue to qa 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5970 
 
 
 
  Add catalog_format to the catalog  
 
 
 
 
 
 
 
 
 

Change By:
 
 William Hopper 
 
 
 

Status:
 
 Ready for  CI  Test 
 
 
 

Assignee:
 
 qa 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-5844) Add the Object type to the Puppet Type system

2016-02-26 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-5844 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Add the Object type to the Puppet Type system  
 
 
 
 
 
 
 
 
 
 
ok, I am fine with modeling both equality and magnitude / sort order. I agree that the way Ecore support those concepts is not great. 
Do you agree that equality is based on the values of all attributes (with all computed/derived attributes skipped) if nothing is stated? Is it enough with a list of attribute names otherwise? 
For sort order, did you have something in mind? I can imagine a list of names and some marker that indicates if it is ascending or descending. e.g. 
 
 
 
 
 
 
order_by => [ 'name', 'age']  # all ascending 
 
 
 
 
order_by => [ ['name', 'ascending'], 'age', [''golf-handicap', 'descending']] # a tuple defines ascending/descending
 
 
 
 
 
 
 
Does that work for you? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to 

Jira (PUP-5911) Define the content of an .xpp file

2016-02-26 Thread Thomas Hallgren (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Hallgren commented on  PUP-5911 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Define the content of an .xpp file  
 
 
 
 
 
 
 
 
 
 
I'm in favor of using a shebang line with two arguments, the executable and the MIME encoding. It must end according to MIME standard so application/json+pcore is better than splitting it into application/json pcore  
The serializer propotype is already capable of serializing the AST with both Locator and source code included. 
My preference when it comes to warnings/errors would be to use issue objects (symbolic issue codes + parameters), not pre-formatted strings. Although symbols are more expensive, they also tabulate very efficiently and I don't think we don't need to bump the protocol when we add new issues. Only thing needed is an issue reporter that understands that it should report unrecognized issues in a decent way (i.e. output the symbol and the parameter values). 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


  1   2   >