Jira (PUP-7102) Insufficient logging when encountering 'permission denied' on environmentpath

2017-02-22 Thread Josh Cooper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper commented on  PUP-7102 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Insufficient logging when encountering 'permission denied' on environmentpath  
 
 
 
 
 
 
 
 
 
 
One thing I noticed is that if the permissions are incorrect on one of the ancestor directories then puppetserver will fail to start: 
 
 
 
 
 
 
06:01:52 Feb 21 06:01:21 rbjkogu91d1gagw systemd[1]: Starting puppetserver Service... 
 
 
 
 
06:01:52 Feb 21 06:01:21 rbjkogu91d1gagw puppetserver[13389]: OpenJDK 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0 
 
 
 
 
06:01:52 Feb 21 06:01:50 rbjkogu91d1gagw puppetserver[13389]: Errno::EACCES: Permission denied - /tmp/lookup_test_dir.hZDf2k 
 
 
 
 
06:01:52 Feb 21 06:01:50 rbjkogu91d1gagw puppetserver[13389]: valid_directory? at /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/environments.rb:242
 
 
 
 
 
 
 
This is different than the compilation will fail with HTTP 500 during catalog compilation. I'm not sure if that was because the test created a temp codedir directory owned by root:root and mode 700 (as opposed to a directory at a lower level, like $codedir/environments/). If the behavior is expected (for puppetserver to fail to start), then we should make sure to release note it. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


Jira (PUP-7243) acceptance: utf8-in-function-args test environment not found

2017-02-22 Thread Josh Cooper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7243 
 
 
 
  acceptance: utf8-in-function-args test environment not found  
 
 
 
 
 
 
 
 
 

Change By:
 
 Josh Cooper 
 
 
 

Fix Version/s:
 
 PUP 5.0.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

2017-02-22 Thread Geoff Nichols (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7247 
 
 
 
  Unparsed line in puppetdb.conf  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Nichols 
 
 
 

Fix Version/s:
 
 PUP 4.9.2 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-1199) Puppet should be able to manage files that are set to immutable

2017-02-22 Thread Sunny (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sunny commented on  PUP-1199 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Puppet should be able to manage files that are set to immutable  
 
 
 
 
 
 
 
 
 
 
Hello! 
I would like to reopen this one up for discussion if possible... 
While I agree that puppet shouldn't be able to change files that are already immutable, I'd think there would be still a use case for puppet to be able to simply make a file immutable initially. 
I have a use case that I want to spin up one or more nodes where I want puppet to create a new file in /path/to/newfile and make it immutable immediately afterward. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

2017-02-22 Thread Jeremy Barlow (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jeremy Barlow updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7247 
 
 
 
  Unparsed line in puppetdb.conf  
 
 
 
 
 
 
 
 
 

Change By:
 
 Jeremy Barlow 
 
 
 

Attachment:
 
 routes.yaml 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

2017-02-22 Thread Jeremy Barlow (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jeremy Barlow commented on  PUP-7247 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Unparsed line in puppetdb.conf  
 
 
 
 
 
 
 
 
 
 
I was unable to reproduce this using the attached puppetdb.conf file when running Puppet 4.9.2, PuppetDB 4.3.0, and Puppet Server 2.7.2 from source. The server came up with no problem and I was able to do an agent run, using Puppet 4.9.2 on the agent, against the server. The report was successfully delivered to Puppet SERVEr with no problem. 
I wonder if there may be a problem in the formatting of the puppetdb.conf file that the yaml parser isn't handling correctly for some reason. Could you upload the exact content of the file so we can see if this is the case? 
Ryan Senior or Henrik Lindberg - does this issue sound familiar to you? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

2017-02-22 Thread Jeremy Barlow (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jeremy Barlow updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7247 
 
 
 
  Unparsed line in puppetdb.conf  
 
 
 
 
 
 
 
 
 

Change By:
 
 Jeremy Barlow 
 
 
 

Attachment:
 
 puppetdb.conf 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-7249) Automatic coercion of String to SemVer/SemVerRange

2017-02-22 Thread Jeremy Barlow (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jeremy Barlow updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7249 
 
 
 
  Automatic coercion of String to SemVer/SemVerRange  
 
 
 
 
 
 
 
 
 

Change By:
 
 Jeremy Barlow 
 
 
 

Component/s:
 
 Puppet Server 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-7243) acceptance: utf8-in-function-args test environment not found

2017-02-22 Thread Sean Griffin (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sean Griffin commented on  PUP-7243 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: acceptance: utf8-in-function-args test environment not found  
 
 
 
 
 
 
 
 
 
 
Eric Thompson I created a PR to fix this by changing the permission to 777 on the temp working directory. Could you please review? Josh C. wonders: (1) should this be checked into stable instead?, and (2) why is it passing stable? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-7204) Add support for mapped paths in hiera.yaml version 5

2017-02-22 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg assigned an issue to Thomas Hallgren 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7204 
 
 
 
  Add support for mapped paths in hiera.yaml version 5  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Assignee:
 
 Thomas Hallgren 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-7204) Add support for mapped paths in hiera.yaml version 5

2017-02-22 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7204 
 
 
 
  Add support for mapped paths in hiera.yaml version 5  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 
 
 
 
 
 
 
 The feature of being able to map an array variable to multiple paths in the hierarchy  has been on the wish list for quite some time. This was originally requested in HI-257 (then rejected, because there was no easy way of supporting this in the old hiera 3 format).Now in hiera.yaml version 5, this is doable.Proposed design:As yet an alternative to the existing {{path}}, {{paths}} etc. we add a {{mapped_paths}} that operates on a fact that is a collection, and maps that into an array of paths. {code}mapped_paths:  -   -   - {code}As an example, a fact named {{$services}} contains the array {{\["a", "b", "c"]}}, then this configuration:{code}- name: Example  mapped_paths: [services, tmp, "service/%{tmp}/common.yaml"]{code}has the same results as if paths had been specified to be {{\[service/a/common.yaml, service/b/common.yaml, service/c/common.yaml]}}.The operation is basically a call to {{map}} with the following rules:* The collection is mapped and each entry is assigned in turn to the given variable name* The given (temporary) variable name is only available locally in the specific {{mapped_paths}}.*  If  the given variable may shadow an outer variable* If the collection is a hash, each iteration produces a key , -  value tuple and assigns it to the named variable* If the referenced collection is not a collection is is turned into a one element array before mapping. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
  

Jira (PUP-7204) Add support for mapped paths in hiera.yaml version 5

2017-02-22 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7204 
 
 
 
  Add support for mapped paths in hiera.yaml version 5  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Component/s:
 
 DOCS 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

2017-02-22 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-513 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Validate type references at runtime.  
 
 
 
 
 
 
 
 
 
 
Closing this as we validate everything that can be validated. Also not that references to non existing thing are ok, it is only when they are used that they must exist. Using a reference as a reference only does not constitute use that require existence.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

2017-02-22 Thread Josh Cooper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper assigned an issue to Josh Cooper 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7246 
 
 
 
  Plan PSON to JSON work  
 
 
 
 
 
 
 
 
 

Change By:
 
 Josh Cooper 
 
 
 

Assignee:
 
 Josh Cooper 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-7243) acceptance: utf8-in-function-args test environment not found

2017-02-22 Thread Sean Griffin (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sean Griffin commented on  PUP-7243 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: acceptance: utf8-in-function-args test environment not found  
 
 
 
 
 
 
 
 
 
 
Eric Thompson I made a pull request for a fix for this test. I changed the directory permissions to 777 for my test directory. Could you please review and pull of you approve? Thanks. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-7130) Ruby 2.4 unifies Fixnum and Bignum into Integer. That breaks the compiler.

2017-02-22 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg assigned an issue to Thomas Hallgren 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7130 
 
 
 
  Ruby 2.4 unifies Fixnum and Bignum into Integer. That breaks the compiler.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Assignee:
 
 Thomas Hallgren 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-7136) Enable the tracing of lookup calls on a per-node basis

2017-02-22 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-7136 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Enable the tracing of lookup calls on a per-node basis  
 
 
 
 
 
 
 
 
 
 
Charlie Sharpsteen I suspect that the explains will be quite costly and that they will indeed skew the result as parameters getting their value from APL will show up as being a lot more expensive than those that do not. Maybe we should add a new option to the HTTP request for "--explain" behaviour? Currently we only have explanations of lookups, but I can imagine additional things being explained over time. 
If we do that, --explain would be changed to be a setting (it is currently speicific to the lookup CLI), and then handled akin to the --profile setting in the indirector/http to make it relay from agent to server. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-7250) Acceptance: Switch to new SPARC hardware

2017-02-22 Thread Stan Duffy (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Stan Duffy created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7250 
 
 
 
  Acceptance: Switch to new SPARC hardware  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Task 
 
 
 

Assignee:
 
 Stan Duffy 
 
 
 

Created:
 

 2017/02/22 3:17 PM 
 
 
 

Environment:
 
 
Puppet Agent CI pipeline 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Stan Duffy 
 
 
 
 
 
 
 
 
 
 
We have new SPARC hardware in place and ready to use. We need to update all of the repos (puppet, facter, hiera & pxp-agent) to use the new LDoms. Initially, we will simply update the existing node config files to point to one of the LDoms on the new controller (opdx-a0-sun2.ops.puppetlabs.net). Once we get some kind of API in place, we will switch to that. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 

Jira (FACT-1576) Acceptance: Switch to new SPARC hardware

2017-02-22 Thread Stan Duffy (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Stan Duffy created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1576 
 
 
 
  Acceptance: Switch to new SPARC hardware  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Task 
 
 
 

Assignee:
 
 Stan Duffy 
 
 
 

Created:
 

 2017/02/22 3:15 PM 
 
 
 

Environment:
 
 
Puppet Agent CI pipeline 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Stan Duffy 
 
 
 
 
 
 
 
 
 
 
We have new SPARC hardware in place and ready to use. We need to update all of the repos (puppet, facter, hiera & pxp-agent) to use the new LDoms. Initially, we will simply update the existing node config files to point to one of the LDoms on the new controller (opdx-a0-sun2.ops.puppetlabs.net). Once we get some kind of API in place, we will switch to that. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 

Jira (HI-556) Acceptance: Switch to new SPARC hardware

2017-02-22 Thread Stan Duffy (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Stan Duffy updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Hiera /  HI-556 
 
 
 
  Acceptance: Switch to new SPARC hardware  
 
 
 
 
 
 
 
 
 

Change By:
 
 Stan Duffy 
 
 
 

Acceptance Criteria:
 
 Acceptance tests all use the new Solaris LDoms 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (HI-556) Acceptance: Switch to new SPARC hardware

2017-02-22 Thread Stan Duffy (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Stan Duffy created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Hiera /  HI-556 
 
 
 
  Acceptance: Switch to new SPARC hardware  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Task 
 
 
 

Assignee:
 
 Stan Duffy 
 
 
 

Created:
 

 2017/02/22 3:13 PM 
 
 
 

Environment:
 
 
Puppet Agent CI pipeline 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Stan Duffy 
 
 
 
 
 
 
 
 
 
 
We have new SPARC hardware in place and ready to use. We need to update all of the repos (puppet, facter, hiera & pxp-agent) to use the new LDoms. Initially, we will simply update the existing node config files to point to one of the LDoms on the new controller (opdx-a0-sun2.ops.puppetlabs.net). Once we get some kind of API in place, we will switch to that. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 

Jira (FACT-1471) Ensure the Collection has enough information about Ruby facts to cache their output

2017-02-22 Thread Maggie Dreyer (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Maggie Dreyer commented on  FACT-1471 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Ensure the Collection has enough information about Ruby facts to cache their output  
 
 
 
 
 
 
 
 
 
 
Created FACT-1575 to track the implementation work. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-1575) Add the ability to cache and block the output of custom facts

2017-02-22 Thread Maggie Dreyer (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Maggie Dreyer created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1575 
 
 
 
  Add the ability to cache and block the output of custom facts  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  New Feature 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2017/02/22 3:06 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Maggie Dreyer 
 
 
 
 
 
 
 
 
 
 
In the first round of Configurable Facter work, we added the ability to cache and block built-in facts via settings in the config file. There is also demand to be able to cache and block custom Ruby facts. Blocking should be straightforward, but to implement caching, some updates to the methods dealing with the fact cache are needed, since they currently assume resolvers are the source of all the fact data.  
In addition, the output of the `-

list-block-groups` and `
-list-cache-groups` command line options need to be updated to also report custom facts available for caching and blocking. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 
   

Jira (FACT-1471) Ensure the Collection has enough information about Ruby facts to cache their output

2017-02-22 Thread Maggie Dreyer (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Maggie Dreyer commented on  FACT-1471 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Ensure the Collection has enough information about Ruby facts to cache their output  
 
 
 
 
 
 
 
 
 
 
It appears to be entirely possible to block and cache custom Ruby facts based on their names. Blocking should be very straightforward, while caching has a few more complexities: 1) If we don't need to cache the weight of custom facts, we may be able to use the exisiting JSON serialization and deserialization approach. But if the weight is referred to later on, we would need to special-case the serialization to handle the weight. Is a custom fact's weight used for any purpose besides resolution ordering (which is irrelevant if we are caching)? 2) Some methods may be added to the collection to provide an external API for caching to be called from the Ruby classes, but the bulk of the refactoring will most likely affect the caching functions themselves, which currently all assume a resolver as the source of the fact data. Some of these really do need to do something different to handle data from Ruby facts, but others may be able to be refactored to support both cases. However, these caching functions are not part of the public API, so updates to method signatures shouldn't cause any issues. 3) Some refactoring of the method which actually resolves Ruby facts may also be needed, to make initializing and refreshing the cache easier. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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 (PDOC-163) failed to generate all docs when there are subfolders inside the manifest dir

2017-02-22 Thread William Hopper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 William Hopper commented on  PDOC-163 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: failed to generate all docs when there are subfolders inside the manifest dir  
 
 
 
 
 
 
 
 
 
 
Ah, good to hear!  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-6494) exec resources leak the command string when execution fails

2017-02-22 Thread John Duarte (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Duarte updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6494 
 
 
 
  exec resources leak the command string when execution fails  
 
 
 
 
 
 
 
 
 

Change By:
 
 John Duarte 
 
 
 

Release Notes Summary:
 
 Added support for sensitive commands in the Exec resource type:command parameters that are specified as Sensitive.new(...) are nowproperly redacted when the command fails. This supports using data from lookup and hiera. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-6494) exec resources leak the command string when execution fails

2017-02-22 Thread John Duarte (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Duarte updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6494 
 
 
 
  exec resources leak the command string when execution fails  
 
 
 
 
 
 
 
 
 

Change By:
 
 John Duarte 
 
 
 

Release Notes:
 
 New Feature 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-6494) exec resources leak the command string when execution fails

2017-02-22 Thread John Duarte (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Duarte updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6494 
 
 
 
  exec resources leak the command string when execution fails  
 
 
 
 
 
 
 
 
 

Change By:
 
 John Duarte 
 
 
 

QA Risk Assessment:
 
 Manual 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-6494) exec resources leak the command string when execution fails

2017-02-22 Thread John Duarte (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Duarte updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6494 
 
 
 
  exec resources leak the command string when execution fails  
 
 
 
 
 
 
 
 
 

Change By:
 
 John Duarte 
 
 
 

QA Contact:
 
 John Duarte 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-3297) Only look for arrays to coerce in columns that might have array values

2017-02-22 Thread Rob Browning (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Browning assigned an issue to Rob Browning 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-3297 
 
 
 
  Only look for arrays to coerce in columns that might have array values  
 
 
 
 
 
 
 
 
 

Change By:
 
 Rob Browning 
 
 
 

Assignee:
 
 Rob Browning 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-6494) exec resources leak the command string when execution fails

2017-02-22 Thread John Duarte (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Duarte commented on  PUP-6494 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: exec resources leak the command string when execution fails  
 
 
 
 
 
 
 
 
 
 
This passes on Ubuntu 16.04 amd64 using puppet-agent at sha 4a671ea6829e987be83ab0934389940ce68724a1 containing puppet at sha ad6df55a248a9fdf19afdce42a00eea7adeeae45. 
An exec resource that has been defined as Sensitive will be redacted from the catalog execution output if it fails. 
Output: 
 
 
 
 
 
 
root@p7l7p03h0rd5gwr:~# cat sensitive_exec.pp 
 
 
 
 
exec { 'sensitive_false': 
 
 
 
 
  command => Sensitive.new("/bin/false TOPSECRET"), 
 
 
 
 
} 
 
 
 
 
exec { 'sensitive_true': 
 
 
 
 
  command => Sensitive.new("/bin/true TOPSECRET"), 
 
 
 
 
} 
 
 
 
 
root@p7l7p03h0rd5gwr:~# puppet apply sensitive_exec.pp 
 
 
 
 
Notice: Compiled catalog for p7l7p03h0rd5gwr.delivery.puppetlabs.net in environment production in 0.13 seconds 
 
 
 
 

Jira (PUP-6612) Scope effort for i18n string externalization

2017-02-22 Thread Eric Delaney (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Delaney updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6612 
 
 
 
  Scope effort for i18n string externalization  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Delaney 
 
 
 

QA Risk Assessment:
 
 No Action 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-1471) Ensure the Collection has enough information about Ruby facts to cache their output

2017-02-22 Thread Eric Delaney (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Delaney updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1471 
 
 
 
  Ensure the Collection has enough information about Ruby facts to cache their output  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Delaney 
 
 
 

QA Risk Assessment Reason:
 
 We should automate this feature 
 
 
 

QA Risk Assessment:
 
 Automate 
 
 
 

QA Contact:
 
 Eric Delaney 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-1574) Add acceptance tests for supported agent fact directories

2017-02-22 Thread Eric Delaney (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Delaney updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1574 
 
 
 
  Add acceptance tests for supported agent fact directories  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Delaney 
 
 
 

QA Risk Assessment Reason:
 
 this is adding acceptance tests 
 
 
 

QA Risk Assessment:
 
 Needs Assessment Automate 
 
 
 

QA Contact:
 
 Eric Delaney 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-3283) Test coverage for conflicts during initial sync

2017-02-22 Thread Russell Mull (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Russell Mull commented on  PDB-3283 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Test coverage for conflicts during initial sync  
 
 
 
 
 
 
 
 
 
 
Testing this is a big pain. It should be easier once we get the new integration-test-in-clojure work committed, as we'll have a decent way to start / restart PDBs without clearing the database.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-6612) Scope effort for i18n string externalization

2017-02-22 Thread Eric Delaney (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Delaney updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6612 
 
 
 
  Scope effort for i18n string externalization  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Delaney 
 
 
 

QA Risk Assessment Reason:
 
 nothing to do 
 
 
 

QA Contact:
 
 Eric Delaney 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-7214) PUP-6663 causes a regression of PUP-535

2017-02-22 Thread Eric Delaney (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Delaney updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7214 
 
 
 
  PUP-6663 causes a regression of PUP-535  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Delaney 
 
 
 

QA Risk Assessment Reason:
 
 Regression we need a test for this 
 
 
 

QA Risk Assessment:
 
 Needs Assessment Automate 
 
 
 

QA Contact:
 
 Eric Delaney 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

2017-02-22 Thread Eric Delaney (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Delaney updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7245 
 
 
 
  fix configuration_interpolation test  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Delaney 
 
 
 

QA Risk Assessment Reason:
 
 this is a test update 
 
 
 

QA Risk Assessment:
 
 Needs Assessment No Action 
 
 
 

QA Contact:
 
 Eric Delaney 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

2017-02-22 Thread Eric Delaney (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Delaney updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7246 
 
 
 
  Plan PSON to JSON work  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Delaney 
 
 
 

QA Risk Assessment Reason:
 
 Planning ticket 
 
 
 

QA Risk Assessment:
 
 Needs Assessment No Action 
 
 
 

QA Contact:
 
 Eric Delaney 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-7152) AIX user provider should specify passwd file encoding explicitly

2017-02-22 Thread Eric Delaney (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Delaney updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7152 
 
 
 
  AIX user provider should specify passwd file encoding explicitly  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Delaney 
 
 
 

QA Risk Assessment:
 
 Automate No Action 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

2017-02-22 Thread Craig Gomes (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Craig Gomes updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7237 
 
 
 
  fix puppet acceptance Rake tasks  
 
 
 
 
 
 
 
 
 

Change By:
 
 Craig Gomes 
 
 
 

Sprint:
 
 PDE 2017-02-22 , PDE 2017-03-08 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-7057) User provider shows plaintext password when it changes a managed users password

2017-02-22 Thread Josh Cooper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper commented on  PUP-7057 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: User provider shows plaintext password when it changes a managed users password  
 
 
 
 
 
 
 
 
 
 
So if I'm reading this right, we can close this? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-7205) Backport Hiera 5 eyaml support to Puppet 4.9.x

2017-02-22 Thread Craig Gomes (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Craig Gomes updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7205 
 
 
 
  Backport Hiera 5 eyaml support to Puppet 4.9.x  
 
 
 
 
 
 
 
 
 

Change By:
 
 Craig Gomes 
 
 
 

Sprint:
 
 PDE 2017-02-22 , PDE 2017-03-08 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-7222) Add a RubyMethod annotation to the Pcore type system

2017-02-22 Thread Craig Gomes (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Craig Gomes updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7222 
 
 
 
  Add a RubyMethod annotation to the Pcore type system  
 
 
 
 
 
 
 
 
 

Change By:
 
 Craig Gomes 
 
 
 

Sprint:
 
 PDE 2017-02-22 , PDE 2017-03-08 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

2017-02-22 Thread Craig Gomes (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Craig Gomes updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5908 
 
 
 
  Implement a PCore MsgPack Serializer  
 
 
 
 
 
 
 
 
 

Change By:
 
 Craig Gomes 
 
 
 

Sprint:
 
 Language 2016-06-29, PDS 2016-11-02, PDS 2016-11-16, PDS 2016-11-30, PDE 2016-12-14, PDE 2017-01-11, PDE 2017-01-25, PDE 2017-02-08, PDE 2017-02-22 , PDE 2017-03-08 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-7227) Add "reference" kind to the Pcore Object Attribute

2017-02-22 Thread Craig Gomes (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Craig Gomes updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7227 
 
 
 
  Add "reference" kind to the Pcore Object Attribute  
 
 
 
 
 
 
 
 
 

Change By:
 
 Craig Gomes 
 
 
 

Sprint:
 
 PDE 2017-02-22 , PDE 2017-03-08 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-7215) Problem with puppet-agent 1.9.x and hiera eyaml backend

2017-02-22 Thread Craig Gomes (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Craig Gomes updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7215 
 
 
 
  Problem with puppet-agent 1.9.x and hiera eyaml backend  
 
 
 
 
 
 
 
 
 

Change By:
 
 Craig Gomes 
 
 
 

Sprint:
 
 PDE 2017-02-22 , PDE 2017-03-08 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-7224) Replace the Rgen AST model with one generated from a Pcore model

2017-02-22 Thread Craig Gomes (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Craig Gomes updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7224 
 
 
 
  Replace the Rgen AST model with one generated from a Pcore model  
 
 
 
 
 
 
 
 
 

Change By:
 
 Craig Gomes 
 
 
 

Sprint:
 
 PDE 2017-02-22 , PDE 2017-03-08 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

2017-02-22 Thread Craig Gomes (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Craig Gomes updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7212 
 
 
 
  Implement Pcore Object annotation pattern  
 
 
 
 
 
 
 
 
 

Change By:
 
 Craig Gomes 
 
 
 

Sprint:
 
 PDE 2017-02-22 , PDE 2017-03-08 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-6373) SemanticPuppet::VersionRange incorrectly assumes that it can rely on ruby Range semantics

2017-02-22 Thread Craig Gomes (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Craig Gomes updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6373 
 
 
 
  SemanticPuppet::VersionRange incorrectly assumes that it can rely on ruby Range semantics  
 
 
 
 
 
 
 
 
 

Change By:
 
 Craig Gomes 
 
 
 

Sprint:
 
 PDE 2017-02-08, PDE 2017-02-22 , PDE 2017-03-08 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

2017-02-22 Thread Craig Gomes (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Craig Gomes updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7226 
 
 
 
  Remove vendored Rgen gem  
 
 
 
 
 
 
 
 
 

Change By:
 
 Craig Gomes 
 
 
 

Sprint:
 
 PDE 2017-02-22 , PDE 2017-03-08 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-7130) Ruby 2.4 unifies Fixnum and Bignum into Integer. That breaks the compiler.

2017-02-22 Thread Craig Gomes (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Craig Gomes updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7130 
 
 
 
  Ruby 2.4 unifies Fixnum and Bignum into Integer. That breaks the compiler.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Craig Gomes 
 
 
 

Sprint:
 
 PDE 2017-02-08, PDE 2017-02-22 , PDE 2017-03-08 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-7102) Insufficient logging when encountering 'permission denied' on environmentpath

2017-02-22 Thread Craig Gomes (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Craig Gomes updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7102 
 
 
 
  Insufficient logging when encountering 'permission denied' on environmentpath  
 
 
 
 
 
 
 
 
 

Change By:
 
 Craig Gomes 
 
 
 

Sprint:
 
 PDE 2017-02-08, PDE 2017-02-22 , PDE 2017-03-08 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-7232) puppet prints deprecation warnings for SemVer even though they can't be fixed

2017-02-22 Thread Craig Gomes (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Craig Gomes updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7232 
 
 
 
  puppet prints deprecation warnings for SemVer even though they can't be fixed  
 
 
 
 
 
 
 
 
 

Change By:
 
 Craig Gomes 
 
 
 

Sprint:
 
 PDE 2017-02-22 , PDE 2017-03-08 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-7168) PCore object default equality not working

2017-02-22 Thread Craig Gomes (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Craig Gomes updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7168 
 
 
 
  PCore object default equality not working  
 
 
 
 
 
 
 
 
 

Change By:
 
 Craig Gomes 
 
 
 

Sprint:
 
 PDE 2017-02-08, PDE 2017-02-22 , PDE 2017-03-08 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

2017-02-22 Thread Craig Gomes (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Craig Gomes updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7225 
 
 
 
  Remove the Puppet Binder  
 
 
 
 
 
 
 
 
 

Change By:
 
 Craig Gomes 
 
 
 

Sprint:
 
 PDE 2017-02-22 , PDE 2017-03-08 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-5659) Puppet master does not fail catalog on unexisting resource in resource parameter

2017-02-22 Thread Craig Gomes (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Craig Gomes updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5659 
 
 
 
  Puppet master does not fail catalog on unexisting resource in resource parameter  
 
 
 
 
 
 
 
 
 

Change By:
 
 Craig Gomes 
 
 
 

Sprint:
 
 PDE 2017-02-08, PDE 2017-02-22 , PDE 2017-03-08 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-7142) Make autoloader recognize types declared in TypeSets.

2017-02-22 Thread Craig Gomes (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Craig Gomes updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7142 
 
 
 
  Make autoloader recognize types declared in TypeSets.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Craig Gomes 
 
 
 

Sprint:
 
 PDE 2017-02-08, PDE 2017-02-22 , PDE 2017-03-08 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-7216) hiera_hash doesn't use deeper merge

2017-02-22 Thread Craig Gomes (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Craig Gomes updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7216 
 
 
 
  hiera_hash doesn't use deeper merge  
 
 
 
 
 
 
 
 
 

Change By:
 
 Craig Gomes 
 
 
 

Sprint:
 
 PDE 2017-02-22 , PDE 2017-03-08 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-7235) glob/globs in hiera 5 does not work (no implicit conversion of String into Integer)

2017-02-22 Thread Craig Gomes (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Craig Gomes updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7235 
 
 
 
  glob/globs in hiera 5 does not work (no implicit conversion of String into Integer)  
 
 
 
 
 
 
 
 
 

Change By:
 
 Craig Gomes 
 
 
 

Sprint:
 
 PDE 2017-02-22 , PDE 2017-03-08 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-7249) Automatic coercion of String to SemVer/SemVerRange

2017-02-22 Thread Rune Juhl Jacobsen (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rune Juhl Jacobsen created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7249 
 
 
 
  Automatic coercion of String to SemVer/SemVerRange  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  New Feature 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 Language, Puppet Server 
 
 
 

Created:
 

 2017/02/22 12:49 PM 
 
 
 

Labels:
 

 typesystem parameter 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Rune Juhl Jacobsen 
 
 
 
 
 
 
 
 
 
 
I'd love to see automatic coercion of Strings to SemVer/SemVerRange. E.g. I'd have a hiera YAML file looking like this: 
 
 
 
 
 
 
--- 
 
 
 
 
test::software::db_version: 3.2.4 
 
 
 
   

Jira (PUP-6494) exec resources leak the command string when execution fails

2017-02-22 Thread Geoff Nichols (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols assigned an issue to John Duarte 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6494 
 
 
 
  exec resources leak the command string when execution fails  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Nichols 
 
 
 

Assignee:
 
 qa John Duarte 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-3306) Remove the vestigial clojure version of the PuppetDB CLI

2017-02-22 Thread Russell Mull (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Russell Mull created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-3306 
 
 
 
  Remove the vestigial clojure version of the PuppetDB CLI  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  New Feature 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2017/02/22 11:43 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Russell Mull 
 
 
 
 
 
 
 
 
 
 
https://github.com/puppetlabs/puppetdb-cli should be able to completely replace it, at this point.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
   

Jira (PDB-3306) Remove the vestigial clojure version of the PuppetDB CLI

2017-02-22 Thread Russell Mull (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Russell Mull updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-3306 
 
 
 
  Remove the vestigial clojure version of the PuppetDB CLI  
 
 
 
 
 
 
 
 
 

Change By:
 
 Russell Mull 
 
 
 

Fix Version/s:
 
 PDB 5.0.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-1574) Add acceptance tests for supported agent fact directories

2017-02-22 Thread Eric Delaney (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Delaney assigned an issue to Eric Delaney 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1574 
 
 
 
  Add acceptance tests for supported agent fact directories  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Delaney 
 
 
 

Assignee:
 
 Eric Delaney 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-1574) Add acceptance tests for supported agent fact directories

2017-02-22 Thread Eric Delaney (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Delaney created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1574 
 
 
 
  Add acceptance tests for supported agent fact directories  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 FACT 3.6.1 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2017/02/22 11:14 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Eric Delaney 
 
 
 
 
 
 
 
 
 
 
Add a test the locations of facts supported by the agent 
https://testrail.ops.puppetlabs.net/index.php?/cases/view/59201&group_by=cases:section_id&group_order=asc&group_id=20770 
Verify that facter uses the new AIO default path for external facts, /opt/puppetlabs/agent/facts.d  also for non-root. non-root case might be its own.. case 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 
   

Jira (PDB-2950) Bump required postgres to 9.6

2017-02-22 Thread Russell Mull (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Russell Mull updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2950 
 
 
 
  Bump required postgres to 9.6  
 
 
 
 
 
 
 
 
 

Change By:
 
 Russell Mull 
 
 
 

Summary:
 
 Bump required postgres to 9. 5 6 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-6986) Service provider fails when hasstatus => false and the output of 'ps -ef' happens to contains non-ASCII chars

2017-02-22 Thread Geoff Nichols (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6986 
 
 
 
  Service provider fails when hasstatus => false and the output of 'ps -ef' happens to contains non-ASCII chars   
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Nichols 
 
 
 

Sprint:
 
 AP 2017-01-11, AP  Ready for Engineering  2017-03-08 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-7214) PUP-6663 causes a regression of PUP-535

2017-02-22 Thread Geoff Nichols (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7214 
 
 
 
  PUP-6663 causes a regression of PUP-535  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Nichols 
 
 
 

Sprint:
 
 AP 2017-03-08 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-7214) PUP-6663 causes a regression of PUP-535

2017-02-22 Thread Geoff Nichols (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7214 
 
 
 
  PUP-6663 causes a regression of PUP-535  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Nichols 
 
 
 

Story Points:
 
 1 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

2017-02-22 Thread Maggie Dreyer (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Maggie Dreyer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7043 
 
 
 
  Mark debug messages for externalization  
 
 
 
 
 
 
 
 
 

Change By:
 
 Maggie Dreyer 
 
 
 

Sprint:
 
 AP 2017-03-22 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-5626) Missing the dependencies key in metadata.json breaks puppet module tool

2017-02-22 Thread Nick Walker (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Nick Walker updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5626 
 
 
 
  Missing the dependencies key in metadata.json breaks puppet module tool  
 
 
 
 
 
 
 
 
 

Change By:
 
 Nick Walker 
 
 
 

Team:
 
 Puppet Developer Experience Workflow Connections 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-5626) Missing the dependencies key in metadata.json breaks puppet module tool

2017-02-22 Thread Nick Walker (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Nick Walker updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5626 
 
 
 
  Missing the dependencies key in metadata.json breaks puppet module tool  
 
 
 
 
 
 
 
 
 

Change By:
 
 Nick Walker 
 
 
 

Team:
 
 Workflow Connections Puppet Developer Experience 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-7248) Convert initial CA cert (and CRL) fetching operation to state machine

2017-02-22 Thread Adrien Thebo (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Adrien Thebo created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7248 
 
 
 
  Convert initial CA cert (and CRL) fetching operation to state machine  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2017/02/22 10:41 AM 
 
 
 

Labels:
 

 ssl 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Adrien Thebo 
 
 
 
 
 
 
 
 
 
 
We should extract a state machine for checking for/conditionally downloading the CA certificate when initializing the agent SSL state. Ideally we should do the same thing for downloading the CRL, though this might be a touch tricky due to the default authorization rules for the puppet CA CRL endpoint. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 

Jira (PUP-5626) Missing the dependencies key in metadata.json breaks puppet module tool

2017-02-22 Thread Ben Ford (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ben Ford updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5626 
 
 
 
  Missing the dependencies key in metadata.json breaks puppet module tool  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ben Ford 
 
 
 
 
 
 
 
 
 
 h1.  The Problem If the {{metadata.json}} file is missing a {{dependencies}} key it renders the puppet module tool inoperable. By extension any spec tests that use forge modules also break.{code}root@master:~ # puppet module listError: No dependencies module metadata provided for pe_inifileError: No dependencies module metadata provided for pe_inifileError: Try 'puppet help module list' for usage{code}h1.  The workaroundAdding {{"dependencies": []}} to { { metadata.json}} will make it work.h1.  The Suggested SolutionPMT should handle the case where the dependencies key is missing better.   
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-5626) Missing the dependencies key in metadata.json breaks puppet module tool

2017-02-22 Thread Nick Walker (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Nick Walker updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5626 
 
 
 
  Missing the dependencies key in metadata.json breaks puppet module tool  
 
 
 
 
 
 
 
 
 

Change By:
 
 Nick Walker 
 
 
 

Summary:
 
 missing Missing  the dependencies key in metadata.json breaks puppet module  tool 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-5626) missing the dependencies key in metadata.json breaks puppet module

2017-02-22 Thread Nick Walker (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Nick Walker updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5626 
 
 
 
  missing the dependencies key in metadata.json breaks puppet module  
 
 
 
 
 
 
 
 
 

Change By:
 
 Nick Walker 
 
 
 

Sprint:
 
 Int 2017-04-05 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-5626) missing the dependencies key in metadata.json breaks puppet module

2017-02-22 Thread Nick Walker (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Nick Walker updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5626 
 
 
 
  missing the dependencies key in metadata.json breaks puppet module  
 
 
 
 
 
 
 
 
 

Change By:
 
 Nick Walker 
 
 
 

Team:
 
 Organizational Scale Puppet Developer Experience 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-5626) missing the dependencies key in metadata.json breaks puppet module

2017-02-22 Thread Nick Walker (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Nick Walker updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5626 
 
 
 
  missing the dependencies key in metadata.json breaks puppet module  
 
 
 
 
 
 
 
 
 

Change By:
 
 Nick Walker 
 
 
 
 
 
 
 
 
 
 h1. The  Problem If the  {{metadata.json}} file  in {{pe_inifile}} was  is  missing a {{dependencies}} key . This rendered  it renders the  puppet module tool inoperable. By extension any spec tests that use forge modules also break.{code}root@master:~ # puppet module listError: No dependencies module metadata provided for pe_inifileError: No dependencies module metadata provided for pe_inifileError: Try 'puppet help module list' for usage{code} h1.  The workaround Adding {{"dependencies": []}} to { {pe_inifile/ metadata.json}}  made  will make  it work. UPDATE: h1.  The  module has now been corrected, but  Suggested Solution  PMT should handle  that  the  case  where the dependencies key is missing  better.    
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-5626) missing the dependencies key in metadata.json breaks puppet module

2017-02-22 Thread Nick Walker (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Nick Walker updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5626 
 
 
 
  missing the dependencies key in metadata.json breaks puppet module  
 
 
 
 
 
 
 
 
 

Change By:
 
 Nick Walker 
 
 
 

Sub-team:
 
 integration 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

2017-02-22 Thread Geoff Nichols (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7246 
 
 
 
  Plan PSON to JSON work  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Nichols 
 
 
 

Acceptance Criteria:
 
 - Work needed for Puppet 5 ticketed and estimated- Plan broadcast to puppet-dev 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

2017-02-22 Thread Geoff Nichols (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7246 
 
 
 
  Plan PSON to JSON work  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Nichols 
 
 
 

Sprint:
 
 AP  Ready for Engineering  2017-03-08 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-6828) Agent PKI initialization is too complicated

2017-02-22 Thread Adrien Thebo (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Adrien Thebo updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6828 
 
 
 
  Agent PKI initialization is too complicated  
 
 
 
 
 
 
 
 
 

Change By:
 
 Adrien Thebo 
 
 
 

Team:
 
 Systems Engineering 
 
 
 

Team/s:
 
 Systems Engineering 
 
 
 

Epic Status:
 
 In Progress 
 
 
 

Epic Name:
 
 Simplify agent SSL initialization 
 
 
 

Status:
 
 Needs Information Developing 
 
 
 

Workflow:
 
 Scrum Team Engineering Epic  Workflow 
 
 
 

Issue Type:
 
 Bug Epic 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

  

Jira (PUP-7245) fix configuration_interpolation test

2017-02-22 Thread Geoff Nichols (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7245 
 
 
 
  fix configuration_interpolation test  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Nichols 
 
 
 

Story Points:
 
 1 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

2017-02-22 Thread Karen Van der Veer (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Karen Van der Veer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-3305 
 
 
 
  Upgrade to i18n 0.7.0  
 
 
 
 
 
 
 
 
 

Change By:
 
 Karen Van der Veer 
 
 
 

Sprint:
 
 SE 2017-03- 08 22 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-7192) Add state machines for complex logic in Puppet

2017-02-22 Thread Adrien Thebo (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Adrien Thebo updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7192 
 
 
 
  Add state machines for complex logic in Puppet  
 
 
 
 
 
 
 
 
 

Change By:
 
 Adrien Thebo 
 
 
 

Team:
 
 Systems Engineering 
 
 
 

Team/s:
 
 Systems Engineering 
 
 
 

Epic Status:
 
 In Progress 
 
 
 

Epic Name:
 
 Simplify agent SSL initialization 
 
 
 

Status:
 
 Ready for Merge Developing 
 
 
 

Workflow:
 
 Scrum Team Engineering Epic  Workflow 
 
 
 

Issue Type:
 
 New Feature Epic 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 
  

Jira (PUP-7192) Add state machines for complex logic in Puppet

2017-02-22 Thread Adrien Thebo (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Adrien Thebo updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7192 
 
 
 
  Add state machines for complex logic in Puppet  
 
 
 
 
 
 
 
 
 

Change By:
 
 Adrien Thebo 
 
 
 

Team:
 
 Systems Engineering 
 
 
 

Team/s:
 
 Systems Engineering 
 
 
 

Epic Status:
 
 In Progress 
 
 
 

Epic Name:
 
 Simplify agent SSL initialization 
 
 
 

Status:
 
 Developing Ready for Merge 
 
 
 

Workflow:
 
 Engineering Epic Scrum Team  Workflow 
 
 
 

Issue Type:
 
 Epic New Feature 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 
  

Jira (PUP-7144) Review error string marking and externalization

2017-02-22 Thread Geoff Nichols (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7144 
 
 
 
  Review error string marking and externalization  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Nichols 
 
 
 

Sprint:
 
 Puppet Triage,  AP 2017-02-22 , AP 2017-03-08 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

2017-02-22 Thread Geoff Nichols (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7245 
 
 
 
  fix configuration_interpolation test  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Nichols 
 
 
 

Sprint:
 
 Puppet Triage,  AP 2017-02-22 , AP 2017-03-08 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-3041) Implement a priority queue with a deadline for command processing

2017-02-22 Thread Karen Van der Veer (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Karen Van der Veer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-3041 
 
 
 
  Implement a priority queue with a deadline for command processing  
 
 
 
 
 
 
 
 
 

Change By:
 
 Karen Van der Veer 
 
 
 

Sprint:
 
 SE 2017-01-25, SE 2017-02-08, SE 2017-03- 08 22 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-1471) Ensure the Collection has enough information about Ruby facts to cache their output

2017-02-22 Thread Geoff Nichols (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1471 
 
 
 
  Ensure the Collection has enough information about Ruby facts to cache their output  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Nichols 
 
 
 

Sprint:
 
 Puppet Triage,  AP 2017-02-22 , AP 2017-03-08 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

2017-02-22 Thread Rob Browning (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Browning updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-3305 
 
 
 
  Upgrade to i18n 0.7.0  
 
 
 
 
 
 
 
 
 

Change By:
 
 Rob Browning 
 
 
 

Summary:
 
 Upgrde Upgrade  to i18n 0.7.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-7021) Prevent incompatible encodings reaching Puppet::Parameter#format from ruby Etc module

2017-02-22 Thread Geoff Nichols (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7021 
 
 
 
  Prevent incompatible encodings reaching Puppet::Parameter#format from ruby Etc module  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Nichols 
 
 
 

Sprint:
 
 Puppet Triage,  AP 2017-01-25, AP 2017-02-08, AP 2017-02-22 , AP 2017-03-08 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-5626) missing the dependencies key in metadata.json breaks puppet module

2017-02-22 Thread Arafat Mohamed (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Arafat Mohamed commented on  PUP-5626 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: missing the dependencies key in metadata.json breaks puppet module  
 
 
 
 
 
 
 
 
 
 
Nick Walker will work with Ben Ford to update description. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-5626) missing the dependencies key in metadata.json breaks puppet module

2017-02-22 Thread Arafat Mohamed (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Arafat Mohamed updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5626 
 
 
 
  missing the dependencies key in metadata.json breaks puppet module  
 
 
 
 
 
 
 
 
 

Change By:
 
 Arafat Mohamed 
 
 
 

Sprint:
 
 Int 2017- 03 04 - 08 05 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-6828) Agent PKI initialization is too complicated

2017-02-22 Thread Adrien Thebo (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Adrien Thebo updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6828 
 
 
 
  Agent PKI initialization is too complicated  
 
 
 
 
 
 
 
 
 

Change By:
 
 Adrien Thebo 
 
 
 

Sprint:
 
 SE 2017-01-11, SE 2017-02-08, SE 2017-02-22 , SE 2017-03-08 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-2958) Rapid-fire puppet runs cause race condition with SSL data

2017-02-22 Thread Karen Van der Veer (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Karen Van der Veer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-2958 
 
 
 
  Rapid-fire puppet runs cause race condition with SSL data  
 
 
 
 
 
 
 
 
 

Change By:
 
 Karen Van der Veer 
 
 
 

Sprint:
 
 SE Triage 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

2017-02-22 Thread Geoff Nichols (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7144 
 
 
 
  Review error string marking and externalization  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Nichols 
 
 
 

Sprint:
 
 Puppet Triage, AP 2017-02-22 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

2017-02-22 Thread Geoff Nichols (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7245 
 
 
 
  fix configuration_interpolation test  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Nichols 
 
 
 

Sprint:
 
 Puppet Triage, AP 2017-02-22 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-7021) Prevent incompatible encodings reaching Puppet::Parameter#format from ruby Etc module

2017-02-22 Thread Geoff Nichols (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7021 
 
 
 
  Prevent incompatible encodings reaching Puppet::Parameter#format from ruby Etc module  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Nichols 
 
 
 

Sprint:
 
 Puppet Triage, AP 2017-01-25, AP 2017-02-08, AP 2017-02-22 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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