Jira (PUP-1780) Issue warning when undefined variables are accessed

2016-02-09 Thread Thomas Hallgren (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Hallgren assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-1780 
 
 
 
  Issue warning when undefined variables are accessed  
 
 
 
 
 
 
 
 
 

Change By:
 
 Thomas Hallgren 
 
 
 

Assignee:
 
 Thomas Hallgren 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-1780) Issue warning when undefined variables are accessed

2016-02-09 Thread Thomas Hallgren (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Hallgren commented on  PUP-1780 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Issue warning when undefined variables are accessed  
 
 
 
 
 
 
 
 
 
 
Merge do master at 6dd80b2 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


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

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

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

Change By:
 
 Thomas Hallgren 
 
 
 

Assignee:
 
 Thomas Hallgren Henrik Lindberg 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-5839) Potential regressions in relationship validation

2016-02-09 Thread Julien Pivotto (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Julien Pivotto commented on  PUP-5839 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Potential regressions in relationship validation  
 
 
 
 
 
 
 
 
 
 
IMO we need to be backward compatible about the aliases, because it makes sense (maybe some people use them to stub 3rd party classes or resources) 
For the file resource, we need to look further because some custom types and providers might behave in the same way. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-5742) Add ability to create Aliases for Puppet Types in PL

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

 
 
 
 
 
 
 
 Puppet /  PUP-5742 
 
 
 
  Add ability to create Aliases for Puppet Types in PL  
 
 
 
 
 
 
 
 
 

Change By:
 
 Thomas Hallgren 
 
 
 

Assignee:
 
 Thomas Hallgren Henrik Lindberg 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-5818) regular expression character class/sets interpreted incorrectly

2016-02-09 Thread Daniel Lupescu (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Lupescu commented on  PUP-5818 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: regular _expression_ character class/sets interpreted incorrectly  
 
 
 
 
 
 
 
 
 
 
Hello, 
1) Yes, I ran the tests in a .pp file - and as I mentioned in the previous update, the issue was first encountered in a Puppet Server environment - so running in command line mode is not the cause. 
2) Puppet match expressions are not affected. The below snippet behaves as expected - lb12.test.local does not match lb[12].test.local 
 
 
 
 
 
 
node /^lb\d+$/ { 
 
 
 
 
if 'lb12.test.local' =~ /lb[12].test.local/ { 
 
 
 
 
notify { "match": } 
 
 
 
 
} 
 
 
 
 
}
 
 
 
 
 
 
 
3) so far only node definitions using regular expressions seem to be affected. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 

Jira (PUP-5841) Environment string matching in the parser seems broken

2016-02-09 Thread Chris Spence (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Chris Spence created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5841 
 
 
 
  Environment string matching in the parser seems broken  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 PUP 4.3.2 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/02/09 4:26 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Chris Spence 
 
 
 
 
 
 
 
 
 
 
Using the following puppet code in puppet 4.3.2 the expectation that with the default environment of 'production' the conditional should match is not met, and the first notice doesn't happen. The second notice where environment is coerced to a string via interpolation does: 
 
 
 
 
 
 
notice("double colon environment ${::environment}") 
 
 
 
 
notice("environment ${environment}") 
 
 
 
 
$foo = inline_template("<%= @environment.inspect %>") 
  

Jira (PDB-2407) PQL: Inequality on dates fails

2016-02-09 Thread Ryan Senior (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ryan Senior created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2407 
 
 
 
  PQL: Inequality on dates fails  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/02/09 4:54 AM 
 
 
 

Fix Versions:
 

 PDB 4.0.0 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Ryan Senior 
 
 
 
 
 
 
 
 
 
 
Looks like currently inequality operators require that the value be a number, which fails on timestamps: 
 
 
 
 
 
 
reports { certname = 'wordpress' 
 
 
 
 
and start_time < '2016-02-07T00:00:00.000Z'}
 
 
 
 
 
 
 
results in 
 
 
 
 
 

Jira (PUP-5839) Potential regressions in relationship validation

2016-02-09 Thread Kenneth Barber (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kenneth Barber commented on  PUP-5839 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Potential regressions in relationship validation  
 
 
 
 
 
 
 
 
 
 
Thanks for looking into this Julien Pivotto & Henrik Lindberg ... seems you've understood the essence of these problems. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


Jira (PDB-2406) (maint) use 'puppetdb-terminus' on redhat with version 3+

2016-02-09 Thread Wyatt Alt (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wyatt Alt updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2406 
 
 
 
  (maint) use 'puppetdb-terminus' on redhat with version 3+  
 
 
 
 
 
 
 
 
 

Change By:
 
 Wyatt Alt 
 
 
 

Scope Change Category:
 
 Found 
 
 
 

Scope Change Reason:
 
 this is required to get our builds green 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


Jira (PDB-2397) (maint) maybe fix upgrade tests

2016-02-09 Thread Wyatt Alt (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wyatt Alt updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2397 
 
 
 
  (maint) maybe fix upgrade tests  
 
 
 
 
 
 
 
 
 

Change By:
 
 Wyatt Alt 
 
 
 

Scope Change Category:
 
 Found 
 
 
 

Scope Change Reason:
 
 this may be needed to get our builds green 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-5842) Node Definitions - RegEx issue

2016-02-09 Thread Benson Anand Arokiadoss (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Benson Anand Arokiadoss created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5842 
 
 
 
  Node Definitions - RegEx issue  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/02/09 8:17 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Benson Anand Arokiadoss 
 
 
 
 
 
 
 
 
 
 
Site.pp node /stub/  { include testclass }  nodename: clftst001stub01   It cant identify. Reason is puppet ignores because it finds a first match as st so it cant find the second match.   Is it a buy with Puppet or something am i missing. Could the reviewer help me out.   I tried different option like below and it worked. But my concerns is why it cant identify in the first method? I was able to replicate the issue couple of times  node /s\w\wb/ { include testclass } 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by 

Jira (PDB-2408) Clarify extended class name in PuppetDB params doc note

2016-02-09 Thread Michelle Fredette (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michelle Fredette moved an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2408 
 
 
 
  Clarify extended class name in PuppetDB params doc note  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michelle Fredette 
 
 
 

Workflow:
 
 Documentation Scrum Team  Workflow 
 
 
 

Key:
 
 DOC PDB - 2512 2408 
 
 
 

Project:
 
 Documentation [Internal] PuppetDB 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


Jira (PDB-2408) Clarify extended class name in PuppetDB params doc note

2016-02-09 Thread Michelle Fredette (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michelle Fredette commented on  PDB-2408 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Clarify extended class name in PuppetDB params doc note  
 
 
 
 
 
 
 
 
 
 
Hi PDB - this ticket impacts the PDB docs. Is it appropriate to send it your way? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-5462) small improvements to module generator

2016-02-09 Thread Kenn Hussey (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kenn Hussey commented on  PUP-5462 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: small improvements to module generator  
 
 
 
 
 
 
 
 
 
 
Michael Smith I assume this issue has made it through CI by now? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


Jira (PDB-2366) PQL: Create command line examples in docs for PQL

2016-02-09 Thread Ryan Senior (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ryan Senior updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2366 
 
 
 
  PQL: Create command line examples in docs for PQL  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ryan Senior 
 
 
 

Sprint:
 
 PuppetDB 2016- 02 03 - 24 09 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


Jira (PDB-2320) PQL: Produce a blog post about PQL

2016-02-09 Thread Ryan Senior (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ryan Senior updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2320 
 
 
 
  PQL: Produce a blog post about PQL  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ryan Senior 
 
 
 

Sprint:
 
 PuppetDB 2016- 02 03 - 24 09 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


Jira (FACT-1340) Update Facter Acceptance tests for cisco-5

2016-02-09 Thread Kenn Hussey (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kenn Hussey commented on  FACT-1340 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Update Facter Acceptance tests for cisco-5  
 
 
 
 
 
 
 
 
 
 
Kylo Ginsberg is this something your team can help get merged? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-5804) Update Puppet Acceptance tests for cisco-5

2016-02-09 Thread Kenn Hussey (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kenn Hussey commented on  PUP-5804 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Update Puppet Acceptance tests for cisco-5  
 
 
 
 
 
 
 
 
 
 
Kylo Ginsberg is this something your team can help get merged? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


Jira (PDB-1906) Docs: Create an "ERD" style diagram to show the relationships between entities

2016-02-09 Thread Kenneth Barber (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kenneth Barber updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-1906 
 
 
 
  Docs: Create an "ERD" style diagram to show the relationships between entities  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kenneth Barber 
 
 
 

Sprint:
 
 PuppetDB 2015-09-23, PuppetDB 2015-10-07, PuppetDB 2015-10-21 , PuppetDB 2016-02-24 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-5839) Potential regressions in relationship validation

2016-02-09 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-5839 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Potential regressions in relationship validation  
 
 
 
 
 
 
 
 
 
 
To be 100% backwards compatible we basically cannot do any validation at all, and the fix should be reverted and moved to Puppet 5.0.0. This because we have no way of statically knowing if a resource type RT will equate two different titles and what the logic for that is without actually creating those instances and testing. That may even involve running on the agent as such equality may be based on the physical traits of the resources (calls to the system are used to resolved if they are equal; e.g. we cannot know server side if two files is the same file because they are symlinked). 
Ping @kylo - I think (unfortunately) that we have to defer this fix to 5.0.0 unless we accept that there will be potential breakage. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-5820) Acceptance test for symlink behavior

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

 
 
 
 
 
 
 
 Puppet /  PUP-5820 
 
 
 
  Acceptance test for symlink behavior  
 
 
 
 
 
 
 
 
 

Change By:
 
 William Hopper 
 
 
 

Scope Change Category:
 
 Found 
 
 
 

Scope Change Reason:
 
 Discovered symlink behavior wasn't well tested when working on metadata inlining for static catalog 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-5818) regular expression character class/sets interpreted incorrectly

2016-02-09 Thread Daniel Lupescu (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Lupescu assigned an issue to Henrik Lindberg 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5818 
 
 
 
  regular _expression_ character class/sets interpreted incorrectly  
 
 
 
 
 
 
 
 
 

Change By:
 
 Daniel Lupescu 
 
 
 

Assignee:
 
 Daniel Lupescu Henrik Lindberg 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


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

2016-02-09 Thread Thomas Hallgren (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Hallgren assigned an issue to Thomas Hallgren 
 
 
 
 
 
 
 
 
 
 

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

Change By:
 
 Thomas Hallgren 
 
 
 

Assignee:
 
 Henrik Lindberg Thomas Hallgren 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


Jira (HI-496) Hiera subkeys lookup should be configurable

2016-02-09 Thread Andreas Ntaflos (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Ntaflos commented on  HI-496 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Hiera subkeys lookup should be configurable  
 
 
 
 
 
 
 
 
 
 
To add a related perspective: this also hits those who use the hiera-file. We don't have dots in any of our normal Hiera lookup keys but the content of files in the hiera-file backend is looked up using the file name as key, and that will almost invariably and naturally contain at least one dot. For example: 
 
 
 
 
 
 
ssldata/projects.d/www.example.com.crt.pem 
 
 
 
 
ssldata/mcollective.d/mcollective-servers.crt.pem 
 
 
 
 
ssldata/mcollective.d/mcollective-servers.key.pem
 
 
 
 
 
 
 
Looking up mcollective-servers.crt.pem with Hiera returns the contents of the file ssldata/mcollective.d/mcollective-servers.crt.pem which we then pass to content of a File resource that manages that certificate on the target systems. 
To make this work with Hiera 2/3 we have to rename all files so something like this: 
 
 
 
 
 
 
ssldata/projects.d/www_example_com_crt_pem 
 
 
 
 
ssldata/mcollective.d/mcollective-servers_crt_pem 
 
 
 
 
ssldata/mcollective.d/mcollective-servers_key_pem
 
 
 
 
 
 
 
Not exactly a showstopper but a PITA and somewhat unnatural for files. 
 
  

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

2016-02-09 Thread Thomas Hallgren (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Hallgren assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 

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

Change By:
 
 Thomas Hallgren 
 
 
 

Assignee:
 
 Thomas Hallgren 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


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

2016-02-09 Thread Thomas Hallgren (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Hallgren commented on  PUP-5819 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Lexer should raise a better error when loading manifest files containing a UTF-8 BOM (Byte Order Mark)  
 
 
 
 
 
 
 
 
 
 
Merge to master at 234810e 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


Jira (PDB-2409) Use native ActiveMQ command retry

2016-02-09 Thread Russell Mull (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Russell Mull created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2409 
 
 
 
  Use native ActiveMQ command retry  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/02/09 9:20 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Russell Mull 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

Jira (PDB-2409) Use native ActiveMQ command retry

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

 
 
 
 
 
 
 
 PuppetDB /  PDB-2409 
 
 
 
  Use native ActiveMQ command retry  
 
 
 
 
 
 
 
 
 

Change By:
 
 Russell Mull 
 
 
 

Sprint:
 
 PuppetDB 2016-02-24 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


Jira (FACT-1340) Update Facter Acceptance tests for cisco-5

2016-02-09 Thread Kylo Ginsberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kylo Ginsberg commented on  FACT-1340 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Update Facter Acceptance tests for cisco-5  
 
 
 
 
 
 
 
 
 
 
Stan Duffy has a meeting Friday to talk about this class of changes, so I was assuming the PR was blocked on that discussion. That said, this is mostly a question for Stan and John Duarte so I'm fine with this being merged on any timetable. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-5804) Update Puppet Acceptance tests for cisco-5

2016-02-09 Thread Kylo Ginsberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kylo Ginsberg commented on  PUP-5804 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Update Puppet Acceptance tests for cisco-5  
 
 
 
 
 
 
 
 
 
 
Stan Duffy has a meeting Friday to talk about this class of changes, so I was assuming the PR was blocked on that discussion. That said, this is mostly a question for Stan and John Duarte so I'm fine with this being merged on any timetable. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-5843) Optimize resolution of TypeReference for known Resource types

2016-02-09 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5843 
 
 
 
  Optimize resolution of TypeReference for known Resource types  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/02/09 9:25 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Henrik Lindberg 
 
 
 
 
 
 
 
 
 
 
PUP-5742 introduces type aliases. This means that scope is required to resolve a type reference. Since there are several use cases where scope is not available (static analysis, class information production, documentation production, etc.) the only choice is to produce an unresolved type reference instead of a resolved type. 
We do this because of the rule, any type that is not a defined type is a subtype of Resource. 
In practice, this means that static analysis and documentation will produce more errors/warnings. This problem can be reduced by reducing the number of unresolved references. This is possible since many of the Resource types are in Puppet core. 
What we can do is to use the static loader since it will always reflect the state of the specific Puppet runtime. The things loaded there also have higher precedence than all of the other loaders so its positive answers are authoritative. 
The work consists of: 
 

making it easy to get to the static state. It may be possible to share it across all environments (which will reduce environment initialization cost as well).
 

Adding all known types to the static loader. This can be done statically by just enumerating them in explicit code. We very rarely add or remove such types from the runtime, and it would be a performance hit to

Jira (PDB-2225) Create status subcommand

2016-02-09 Thread Ryan Senior (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ryan Senior updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2225 
 
 
 
  Create status subcommand  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ryan Senior 
 
 
 

Story Points:
 
 1 
 
 
 

Sprint:
 
 PuppetDB 2016-02-24 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-5122) Acceptance tests for direct puppet running from cache

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

 
 
 
 
 
 
 
 Puppet /  PUP-5122 
 
 
 
  Acceptance tests for direct puppet running from cache  
 
 
 
 
 
 
 
 
 

Change By:
 
 William Hopper 
 
 
 

Assignee:
 
 Sean Griffin William Hopper 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-5742) Add ability to create Aliases for Puppet Types in PL

2016-02-09 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-5742 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Add ability to create Aliases for Puppet Types in PL  
 
 
 
 
 
 
 
 
 
 
Merged to master at dffbdc4 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


Jira (PDB-2361) Harmonize destination of output

2016-02-09 Thread Ryan Senior (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ryan Senior updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2361 
 
 
 
  Harmonize destination of output  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ryan Senior 
 
 
 

Sprint:
 
 PuppetDB 2016-03-09 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


Jira (PDB-2339) POST queries to PuppetDB

2016-02-09 Thread Ryan Senior (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ryan Senior updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2339 
 
 
 
  POST queries to PuppetDB  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ryan Senior 
 
 
 

Sprint:
 
 PuppetDB 2016-02-24 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


Jira (PDB-2363) Possibly tighten up CLI argument parsing

2016-02-09 Thread Ryan Senior (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ryan Senior updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2363 
 
 
 
  Possibly tighten up CLI argument parsing  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ryan Senior 
 
 
 

Sprint:
 
 PuppetDB 2016- 02 03 - 24 09 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


Jira (PDB-2350) Consider more discriminating exception handling in CLI

2016-02-09 Thread Ryan Senior (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ryan Senior updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2350 
 
 
 
  Consider more discriminating exception handling in CLI  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ryan Senior 
 
 
 

Sprint:
 
 PuppetDB 2016- 02 03 - 24 09 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


Jira (PDB-2363) Possibly tighten up CLI argument parsing

2016-02-09 Thread Ryan Senior (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ryan Senior updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2363 
 
 
 
  Possibly tighten up CLI argument parsing  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ryan Senior 
 
 
 

Sprint:
 
 PuppetDB 2016-02-24 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


Jira (FACT-1340) Update Facter Acceptance tests for cisco-5

2016-02-09 Thread Stan Duffy (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Stan Duffy commented on  FACT-1340 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Update Facter Acceptance tests for cisco-5  
 
 
 
 
 
 
 
 
 
 
Kylo Ginsberg & Kenn Hussey, This PR really needs the next beaker release to come out before it's merged. That's supposed to happen tomorrow. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


Jira (PDB-2350) Consider more discriminating exception handling in CLI

2016-02-09 Thread Ryan Senior (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ryan Senior updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2350 
 
 
 
  Consider more discriminating exception handling in CLI  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ryan Senior 
 
 
 

Sprint:
 
 PuppetDB 2016-02-24 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


Jira (PDB-2311) Change command names to use `_` instead of `" "` or `-`

2016-02-09 Thread Ryan Senior (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ryan Senior updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2311 
 
 
 
  Change command names to use `_` instead of `" "` or `-`  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ryan Senior 
 
 
 

Story Points:
 
 2 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


Jira (PDB-1531) Upgrade to tk-metrics

2016-02-09 Thread Ryan Senior (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ryan Senior updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-1531 
 
 
 
  Upgrade to tk-metrics  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ryan Senior 
 
 
 

Sprint:
 
 PuppetDB 2016- 02 03 - 24 09 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-5742) Add ability to create Aliases for Puppet Types in PL

2016-02-09 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-5742 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Add ability to create Aliases for Puppet Types in PL  
 
 
 
 
 
 
 
 
 
 
For FR - the following use cases can be tested: 
 

Explicit type alias in a manifest (can be done on the command line with an apply) e.g 
 
 
 
 
 
 
bundle exec puppet apply -e 'type MyInteger = Integer; notice 42 =~ MyInteger'
 
 
 
 
 
 

 

Auto loading Environment::MyInteger from a .pp file in the environment (file /types/myinteger.pp) 
 
 
 
 
 
 
bundle exec puppet apply -e 'notice 42 =~ Environment::MyInteger'
 
 
 
 
 
 

 

Auto loading MyModule::MyInteger from a -pp file in a module (file /types/myinteger.pp) 
 
 
 
 
 
 
bundle exec puppet apply -e 'notice 42 =~ MyModule::MyInteger'
 
 
 
 
 
 

 

Auto loading MyModule::Somewhere::MyInteger from a -pp file in a module (file /types/somewhere/myinteger.pp) 
 
 
   

Jira (PDB-2372) Support for unchanged reports using the benchmarking tool

2016-02-09 Thread Ryan Senior (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ryan Senior updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2372 
 
 
 
  Support for unchanged reports using the benchmarking tool  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ryan Senior 
 
 
 

Story Points:
 
 5 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


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

2016-02-09 Thread Ryan Senior (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ryan Senior updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2381 
 
 
 
  Write a script to collect enough stats from customer DBs to define 'representative data'  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ryan Senior 
 
 
 

Story Points:
 
 2 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-5742) Add ability to create Aliases for Puppet Types in PL

2016-02-09 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5742 
 
 
 
  Add ability to create Aliases for Puppet Types in PL  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Assignee:
 
 Henrik Lindberg 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


Jira (PDB-2409) Use native ActiveMQ command retry

2016-02-09 Thread Ryan Senior (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ryan Senior updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2409 
 
 
 
  Use native ActiveMQ command retry  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ryan Senior 
 
 
 

Sprint:
 
 PuppetDB 2016- 03 02 - 09 24 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-5462) small improvements to module generator

2016-02-09 Thread Kenn Hussey (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kenn Hussey commented on  PUP-5462 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: small improvements to module generator  
 
 
 
 
 
 
 
 
 
 
Alexander Johnson can you please help verify whether this is fixed? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


Jira (PDB-2409) Use native ActiveMQ command retry

2016-02-09 Thread Ryan Senior (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ryan Senior updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2409 
 
 
 
  Use native ActiveMQ command retry  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ryan Senior 
 
 
 

Sprint:
 
 PuppetDB 2016- 02 03 - 24 09 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


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

2016-02-09 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg created an issue 
 
 
 
 
 
 
 
 
 
 

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

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/02/09 10:05 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Henrik Lindberg 
 
 
 
 
 
 
 
 
 
 
In the Puppet Core Type Model (PCore) that will be used to describe all serialization using the Puppet Type System it is essential to have an Object[T] type that matches instances of user defined type T. We also need the run time abstract Object from which the concrete instances of user defined data types are derived. 
This work is also required to enable the full user defined type definition using the syntax: 
 
 
 
 
 
 
type TypeName inhirts SuperTypeName { 
 
 
 
 
  # attribute definitions  
 
 
 
 
}
 
 
 
 
 
 
  

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

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

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

Change By:
 
 Henrik Lindberg 
 
 
 

Fix Version/s:
 
 PUP 4.4.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-5843) Optimize resolution of TypeReference for known Resource types

2016-02-09 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-5843 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Optimize resolution of TypeReference for known Resource types  
 
 
 
 
 
 
 
 
 
 
Ping Thomas Hallgren Peter Huene - thoughts ? 
Yeah, it is bad that statically "any undefined type is a Resource". That cannot be fixed until resource types (and classes) are forced to use module name space unless defied in puppet core. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-5616) puppet device convergence impossibility, and improved error output

2016-02-09 Thread Branan Riley (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Branan Riley assigned an issue to Stan Duffy 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Hey Stan: 
Per Michael Smith's comment on the PR for this, would you mind trying to give this a quick verification before we hit the merge button? Or if you think it's simple enough to not need the manual check just let us know and we can just get it merged. 
Thanks! 
 
 
 
 
 
 
 
 
 
 Puppet /  PUP-5616 
 
 
 
  puppet device convergence impossibility, and improved error output  
 
 
 
 
 
 
 
 
 

Change By:
 
 Branan Riley 
 
 
 

Assignee:
 
 Stan Duffy 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-5734) Value of the key dependencies in the metadata.json of modules isn't checked

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

 
 
 
 
 
 
 
 Puppet /  PUP-5734 
 
 
 
  Value of the key dependencies in the metadata.json of modules isn't checked  
 
 
 
 
 
 
 
 
 
 
Alexander Johnson Could you get this into a code manager sprint? It's a change to how the PMT handles modules with malformed module metadata.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Josh Cooper 
 
 
 

Scrum Team:
 
 Code Management 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-5742) Add ability to create Aliases for Puppet Types in PL

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

 
 
 
 
 
 
 
 Puppet /  PUP-5742 
 
 
 
  Add ability to create Aliases for Puppet Types in PL  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Component/s:
 
 DOCS 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


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

2016-02-09 Thread Ryan Gard (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ryan Gard commented on  PUP-5728 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Change default parsing of manifest files to UTF-8  
 
 
 
 
 
 
 
 
 
 
Functional Review 
Verified as fixed with build 6522aa18d8338b9ffdc613ea7e750a633d4ec6d5. 
Environment 
Agent: Windows Server 2012 R2 (WIN_SUT) Agent: CentOS 7 x64 (LINUX_SUT) 
Test Case 1 Reproduction Steps 
 

Install Puppet Agent on WIN_SUT.
 

Create the manifest "C:\test.pp" (UTF-8 Encoding) on the WIN_SUT with the following content: 
 
 
 
 
 
 
file { "c:\\unicode_\u5BF9\u5BFA\u5BFB\u5BFD\u5BFE\u5BFF\u5BF8": 
 
 
 
 
  ensure => file, 
 
 
 
 
  content => "\u5BF9\u5BFA\u5BFB\u5BFD\u5BFE\u5BFF\u5BF8", 
 
 
 
 
} 
 
 
 
 
file { 'c:\漕滴滸漛漣': 
 
 
 
 
  ensure => file, 
 
 
 
 
  content => '漕滴滸漛漣', 
 
 
 
   

Jira (HI-438) Add node definition for Fedora 23 (i386, x86_64) to Hiera

2016-02-09 Thread Kenn Hussey (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kenn Hussey commented on  HI-438 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Add node definition for Fedora 23 (i386, x86_64) to Hiera  
 
 
 
 
 
 
 
 
 
 
John Duarte can you please confirm that this ticket is no longer relevant and close it? Thanks! 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


Jira (FACT-1193) Add node definition for Fedora 23 (i386, x86_64) to Facter

2016-02-09 Thread Kenn Hussey (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kenn Hussey commented on  FACT-1193 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Add node definition for Fedora 23 (i386, x86_64) to Facter  
 
 
 
 
 
 
 
 
 
 
John Duarte can you please confirm that this ticket is no longer relevant and close it? Thanks! 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-5742) Add ability to create Aliases for Puppet Types in PL

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

 
 
 
 
 
 
 
 Puppet /  PUP-5742 
 
 
 
  Add ability to create Aliases for Puppet Types in PL  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Release Notes Summary:
 
 It is now possible to define aliases for data types. The aliases are auto loaded from .pp files under a modules /types/ and the filename must match that alias name. The alias is defined as in this simple example:type MyInteger = IntegerThis is used to create reusable and descriptive types. 
 
 
 

Release Notes:
 
 New Feature 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-5845) Add the function type()

2016-02-09 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5845 
 
 
 
  Add the function type()  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/02/09 10:31 AM 
 
 
 

Fix Versions:
 

 PUP 4.4.0 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Henrik Lindberg 
 
 
 
 
 
 
 
 
 
 
Add the function type that produces the type of the given argument. 
There is currently a function named type_of in stdlib. This is the same functionality but available in core as it is odd to not have this directly in core. 
This was made possible in the work done on PUP-5742 as the type keyword was changed from just being reserved for future use. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

  

Jira (PUP-5845) Add the function type()

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

 
 
 
 
 
 
 
 Puppet /  PUP-5845 
 
 
 
  Add the function type()  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 
 
 
 
 
 
 
 Add the function {{type \ (x)}} that produces the type of the given argument.There is currently a function named {{type_of}} in stdlib. This is the same functionality but available in core as it is odd to not have this directly in core.This was made possible in the work done on PUP-5742 as the {{type}} keyword was changed from just being reserved for future use. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-5472) Acceptance tests for lookup command

2016-02-09 Thread Eric Thompson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Thompson assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5472 
 
 
 
  Acceptance tests for lookup command  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Thompson 
 
 
 

Assignee:
 
 Sean Griffin 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-5462) small improvements to module generator

2016-02-09 Thread garrett honeycutt (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 garrett honeycutt commented on  PUP-5462 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: small improvements to module generator  
 
 
 
 
 
 
 
 
 
 
Merged January 19th 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


Jira (FACT-1344) Acceptance: verify_facts fails with NameError

2016-02-09 Thread Michael Smith (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Smith commented on  FACT-1344 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Acceptance: verify_facts fails with NameError  
 
 
 
 
 
 
 
 
 
 
Ah yup, that's evaluating to false. ldom_domainrole_control: false. The ldom facts are generated and we don't really know their contents, so the schema just says "string". For booleans this may be ok, and we just want to accept TrueClass and FalseClass. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-5718) Modify install.rb to install a puppet.bat file on windows

2016-02-09 Thread Eric Thompson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Thompson assigned an issue to Eric Thompson 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5718 
 
 
 
  Modify install.rb to install a puppet.bat file on windows  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Thompson 
 
 
 

Assignee:
 
 qa Eric Thompson 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-5818) regular expression character class/sets interpreted incorrectly

2016-02-09 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-5818 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: regular _expression_ character class/sets interpreted incorrectly  
 
 
 
 
 
 
 
 
 
 
Ping Christopher Price - is there a different regexp package in use in JRuby than in MRI ? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-5818) regular expression character class/sets interpreted incorrectly

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

 
 
 
 
 
 
 
 Puppet /  PUP-5818 
 
 
 
  regular _expression_ character class/sets interpreted incorrectly  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Sprint:
 
 Language Triage 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-5734) Value of the key dependencies in the metadata.json of modules isn't checked

2016-02-09 Thread Alexander Johnson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alexander Johnson updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5734 
 
 
 
  Value of the key dependencies in the metadata.json of modules isn't checked  
 
 
 
 
 
 
 
 
 

Change By:
 
 Alexander Johnson 
 
 
 

Story Points:
 
 2 
 
 
 

Sprint:
 
 CODEMGMT 2016-02-24 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-5734) Value of the key dependencies in the metadata.json of modules isn't checked

2016-02-09 Thread Alexander Johnson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alexander Johnson commented on  PUP-5734 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Value of the key dependencies in the metadata.json of modules isn't checked  
 
 
 
 
 
 
 
 
 
 
Anderson Mills fyi... I'll add this to the upcoming sprint. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


Jira (HI-496) Hiera subkeys lookup should be configurable

2016-02-09 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  HI-496 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Hiera subkeys lookup should be configurable  
 
 
 
 
 
 
 
 
 
 
Please file a ticket for hiera-file backend. It should simply use the option to receive raw keys. It is dead simple to add that. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-5818) regular expression character class/sets interpreted incorrectly

2016-02-09 Thread Christopher Price (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christopher Price commented on  PUP-5818 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: regular _expression_ character class/sets interpreted incorrectly  
 
 
 
 
 
 
 
 
 
 
Henrik Lindberg AFAIK JRuby strives for compatibility with the upstream Ruby version that it is emulating, and I'd be a little surprised if there were differences in the regex behavior, but it's not impossible. 
One point that may be relevant is that Puppet Server's current JRuby strives for compatibility with MRI Ruby 1.9.3, so if Ruby itself made any semantic changes related to regexes between 1.9.x and 2.x, those might not be reflected in Puppet Server until we upgrade to a JRuby that provides MRI 2.x compatibility. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-5846) User resources with "managehome => true" only attempt to create home directory on user creation.

2016-02-09 Thread Erik Dasher (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Erik Dasher created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5846 
 
 
 
  User resources with "managehome => true" only attempt to create home directory on user creation.  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/02/09 12:38 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Erik Dasher 
 
 
 
 
 
 
 
 
 
 
User resources with "managehome => true" only attempt to create home directory on user creation. 
STEPS TO REPRODUCE: 1. Create a manifest like this: 
 
 
 
 
 
 
user { 'git': 
 
 
 
 
ensure => present, 
 
 
 
 
home => '/home/git', 
 
 
 
 
managehome => true, 
 
 
  

Jira (PUP-5846) User resources with "managehome => true" only attempt to create home directory on user creation.

2016-02-09 Thread Erik Dasher (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Erik Dasher updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5846 
 
 
 
  User resources with "managehome => true" only attempt to create home directory on user creation.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Erik Dasher 
 
 
 
 
 
 
 
 
 
 User resources with "managehome => true" only attempt to create home directory on user creation.STEPS TO REPRODUCE:1. Create a manifest like this: {noformat}user { 'git':ensure => present,home => '/home/git',managehome => true,system => true,}{noformat}2.  puppet apply the manifest.3.  Delete the user's home directory.  'rm -rf /home/git'4.  puppet apply the manifest.EXPECTED RESULTS:The user's home directory should be recreated.ACTUAL RESULTS:The user's home directory is not recreated. puppet --version4.3.2OS = CentOS 6. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-5818) regular expression character class/sets interpreted incorrectly

2016-02-09 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-5818 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: regular _expression_ character class/sets interpreted incorrectly  
 
 
 
 
 
 
 
 
 
 
Christopher Price Ruby MRI made changes to regular expressions in 1.9. (Although I think they got back ported to 1.8.7). I am asking because the Java Regexp is quite different. Could it be that JRuby is using an older "MRI regexp" (i.e. we should then see the problem on MRI 1.8.7 perhaps). 
Also, since this seems to be related to node expressions - is there any special handling of nodes when running on Puppet Server (I am not aware of any, but thought it best to ask to eliminate that as a potential source of this problem). 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


Jira (PDB-2357) PQL: Decide on final group by syntax

2016-02-09 Thread Wyatt Alt (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wyatt Alt assigned an issue to Wyatt Alt 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2357 
 
 
 
  PQL: Decide on final group by syntax  
 
 
 
 
 
 
 
 
 

Change By:
 
 Wyatt Alt 
 
 
 

Assignee:
 
 Wyatt Alt 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


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

2016-02-09 Thread Ryan Gard (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ryan Gard commented on  PUP-5728 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Change default parsing of manifest files to UTF-8  
 
 
 
 
 
 
 
 
 
 
Functional Review 
Verified as fixed with build 6522aa18d8338b9ffdc613ea7e750a633d4ec6d5. 
Environment 
Agent: Windows Server 2012 R2 (WIN_SUT) Agent: CentOS 7 x64 (LINUX_SUT) 
Test Case 1 Reproduction Steps 
 

Install Puppet Agent on WIN_SUT.
 

Create the EPP template "C:\template.epp" (UTF-8 Encoding) on the WIN_SUT with the following content: 
 
 
 
 
 
 
尻屌屛屗尐少 
 
 
 
 
<%= $text %> 
 
 
 
 
漕滴滸漛漣
 
 
 
 
 
 

 

Change console font to "Lucidia Console". (Puppet will crash otherwise. 

PUP-5717
)
 

Change codepage: 
 
 
 
 
 
 
chcp 65001 
 
 
 
 
 

 
   

Jira (PUP-5818) regular expression character class/sets interpreted incorrectly

2016-02-09 Thread Christopher Price (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christopher Price commented on  PUP-5818 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: regular _expression_ character class/sets interpreted incorrectly  
 
 
 
 
 
 
 
 
 
 
Henrik Lindberg nope, no special handling of nodes on Puppet Server. The Java regexp vs. Ruby regexp is entirely possible, though. 
I found this: https://github.com/jruby/jruby/wiki/DifferencesBetweenMriAndJruby#regular-expressions 
But not sure how recent that is. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


Jira (PDB-2410) (maint) update release notes for 5.1.0

2016-02-09 Thread gepetto-bot (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 gepetto-bot updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2410 
 
 
 
  (maint) update release notes for 5.1.0  
 
 
 
 
 
 
 
 
 

Change By:
 
 gepetto-bot 
 
 
 

Sprint:
 
 PuppetDB 2016-02-10 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


Jira (PDB-2410) (maint) update release notes for 5.1.0

2016-02-09 Thread gepetto-bot (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 gepetto-bot created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2410 
 
 
 
  (maint) update release notes for 5.1.0  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/02/09 1:06 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 gepetto-bot 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

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

2016-02-09 Thread Ryan Gard (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ryan Gard commented on  PUP-5728 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Change default parsing of manifest files to UTF-8  
 
 
 
 
 
 
 
 
 
 
Functional Review 
Verified as fixed with build 6522aa18d8338b9ffdc613ea7e750a633d4ec6d5. 
Environment 
Agent: Windows Server 2012 R2 (WIN_SUT) Agent: CentOS 7 x64 (LINUX_SUT) 
Test Case 1 Reproduction Steps 
 

Install Puppet Agent on WIN_SUT.
 

Create the EPP template "C:\template.epp" (UTF-8 Encoding) on the WIN_SUT with the following content: 
 
 
 
 
 
 
尻屌屛屗尐少 
 
 
 
 
<%= $text %> 
 
 
 
 
漕滴滸漛漣
 
 
 
 
 
 

 

Create the manifest "C:\test.pp" (UTF-8 Encoding) on the WIN_SUT with the following content: 
 
 
 
 
 
 
$text='ᅪᅫᅇᅽᄟ' 
 
 
 
 
file { 'c:\漕滴滸漛漣': 
 
 
 
 
  ensure  => file, 
 

Jira (PUP-5818) regular expression character class/sets interpreted incorrectly

2016-02-09 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-5818 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: regular _expression_ character class/sets interpreted incorrectly  
 
 
 
 
 
 
 
 
 
 
it says "matches Onigurama's behavior" - which to me sounds like "you cannot believe it is not butter" unless they actually do link Onigurama's regexp library and use exactly the same version w.r.t bugfixes. 
Christopher Price can you do a quick manual check with the regular _expression_ we are discussing just to be sure nothing is wrong in general in the JRuby version before I dig into the mystery (I have not found anything obvious yet in node). 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


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

2016-02-09 Thread Ryan Gard (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ryan Gard commented on  PUP-5728 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Change default parsing of manifest files to UTF-8  
 
 
 
 
 
 
 
 
 
 
Functional Review 
Verified as fixed with build 6522aa18d8338b9ffdc613ea7e750a633d4ec6d5. 
Environment 
Agent: Windows Server 2012 R2 (WIN_SUT) Agent: CentOS 7 x64 (LINUX_SUT) 
Test Case 1 Reproduction Steps 
 

Install Puppet Agent on WIN_SUT.
 

Create the ERB template "C:\template.erb" (UTF-8 Encoding) on the WIN_SUT with the following content: 
 
 
 
 
 
 
尻屌屛屗尐少 
 
 
 
 
<%= @text %> 
 
 
 
 
漕滴滸漛漣
 
 
 
 
 
 

 

Create the manifest "C:\test.pp" (UTF-8 Encoding) on the WIN_SUT with the following content: 
 
 
 
 
 
 
$text='ᅪᅫᅇᅽᄟ' 
 
 
 
 
file { 'c:\漕滴滸漛漣': 
 
 
 
 
  ensure  => file, 
 

Jira (PUP-5818) regular expression character class/sets interpreted incorrectly

2016-02-09 Thread Christopher Price (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christopher Price commented on  PUP-5818 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: regular _expression_ character class/sets interpreted incorrectly  
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
╭─cprice@cosmicshame ~ ‹system› (office-workstation ✘)✹ 
 
 
 
 
╰─➤  rbenv shell 1.9.3-p5511:32:38 PM 
 
 
 
 
╭─cprice@cosmicshame ~ ‹1.9.3-p551› (office-workstation ✘)✹ 
 
 
 
 
╰─➤  irb   1:32:51 PM 
 
 
 
 
irb(main):001:0> 'lb12.test.local' =~ /lb[12].test.local/ 
 
 
 
 
=> nil 
 
 
 
 
irb(main):002:0> 'lb1.test.local' =~ /lb[12].test.local/ 
 
 
 
 
=> 0 
 
 
 
 
irb(main):003:0>  
 
 
 
 
   

Jira (HI-496) Hiera subkeys lookup should be configurable

2016-02-09 Thread Andreas Ntaflos (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Ntaflos commented on  HI-496 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Hiera subkeys lookup should be configurable  
 
 
 
 
 
 
 
 
 
 
Will do, thanks for the pointer! 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-5818) regular expression character class/sets interpreted incorrectly

2016-02-09 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-5818 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: regular _expression_ character class/sets interpreted incorrectly  
 
 
 
 
 
 
 
 
 
 
Thanks Christopher Price can you check the char group _expression_ as well - i.e. [1-2] instead of [12] 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-5847) Investigate/Develop support for Cisco xxx provider for eXR

2016-02-09 Thread Alexander Johnson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alexander Johnson created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5847 
 
 
 
  Investigate/Develop support for Cisco xxx provider for eXR  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Jonathan Tripathy 
 
 
 

Created:
 

 2016/02/09 2:22 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Alexander Johnson 
 
 
 
 
 
 
 
 
 
 
Start to develop eXR provider for DNS (simple one). See http://www.cisco.com/c/en/us/td/docs/iosxr/ncs5500/ip-addresses/60x/b-ncs5500-ip-addresses-configuration-guide-60x.pdf for additional info on eXR. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

Jira (PUP-5848) Relationship validation fails when a multi-resource reference is used inside an array

2016-02-09 Thread Nick Lewis (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Nick Lewis created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5848 
 
 
 
  Relationship validation fails when a multi-resource reference is used inside an array  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 Language 
 
 
 

Created:
 

 2016/02/09 3:05 PM 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Nick Lewis 
 
 
 
 
 
 
 
 
 
 
As of commit 676f0b7, the following code issues an error: 
 
 
 
 
 
 
notify { 'a': 
 
 
 
 
  require => [ 
 
 
 
 
Notify['b', 'c'], 
 
 
 
 
  ], 
  

Jira (PUP-5848) Relationship validation fails when a multi-resource reference is used inside an array

2016-02-09 Thread Nick Lewis (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Nick Lewis commented on  PUP-5848 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Relationship validation fails when a multi-resource reference is used inside an array  
 
 
 
 
 
 
 
 
 
 
ping Henrik Lindberg 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-5848) Relationship validation fails when a multi-resource reference is used inside an array

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

 
 
 
 
 
 
 
 Puppet /  PUP-5848 
 
 
 
  Relationship validation fails when a multi-resource reference is used inside an array  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Story Points:
 
 1 
 
 
 

Sprint:
 
 Language 2016-02-24 (Burn FF) 
 
 
 

Scrum Team:
 
 Language 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-5849) Newline is not sufficient to avoid parsing as a function call

2016-02-09 Thread Daniel Parks (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Parks created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5849 
 
 
 
  Newline is not sufficient to avoid parsing as a function call  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 PUP 4.3.2, PUP 4.2.2 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 Language 
 
 
 

Created:
 

 2016/02/09 3:28 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Daniel Parks 
 
 
 
 
 
 
 
 
 
 
It looks like starting a line with ( will cause the parser to attempt to match the last "word" of the previous line as a function name. 
(Feel free to change the title of this. I couldn't figure out how to make it clearer.)  
Broken test case 
 
 
 
 
 
 
$a = [] 
 
 
 
 
([]).each |$n| { }
 
   

Jira (PUP-5766) (Static Catalog) PE documentation for static catalogs in Burnside

2016-02-09 Thread Isaac Eldridge (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Isaac Eldridge updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5766 
 
 
 
  (Static Catalog) PE documentation for static catalogs in Burnside  
 
 
 
 
 
 
 
 
 

Change By:
 
 Isaac Eldridge 
 
 
 
 
 
 
 
 
 
 For PE documentation of static catalogs, I'm planning on covering the following:h2. Enabling static catalogs * During fresh install of PE, they're enabled globally  if you choose to enable  with  application orchestration . You can later turn static catalogs on  or  off per environment  not .  (Outside of app orchestration, we still don't know what the behavior will be.)   * During upgrades of PE, nothing happens. You must manually enable static catalogs, per environment, after upgrade.* Documentation tracking off PE-13884.h2.  Turn it offglobal setting (puppet.conf, [main]) or per-environment (environment.conf [main])h2.  Conceptual overview info* In PE Burnside, this is mostly new functionality to alleviate the issues caused by agents [running off cached catalog when participating in application orchestration services|http://docs.puppetlabs.com/pe/latest/orchestrator_install.html#prepare-your-agents-for-orchestration-services]. * Describe the concepts behind how and why to use static catalogs; i.e., if file content on master changes, agents could be using incorrect content* Static catalogs ensure agents get always get correct file content as original catalog will have unique SHA (content_uri) associated with specific versions of content* The agent with static catalog enabled will only contact the master when it knows the file contents don't match desired state* (I'm working with Joe Wagner to hopefully get UX resources to draw up graphic [~josh] created while explaining this to me)h2. Question* If you want to push new "static catalogs" to environments do you use the orchestrator and/or any regular puppet run? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

Jira (PUP-5529) (Catalog Metadata) As a puppet administrator, I want to reduce the load on my compile masters when nothing has changed on my intended system state. (CPU load reduction of 60%)

2016-02-09 Thread Erik Dasher (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Erik Dasher updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5529 
 
 
 
  (Catalog Metadata) As a puppet administrator, I want to reduce the load on my compile masters when nothing has changed on my intended system state. (CPU load reduction of 60%)  
 
 
 
 
 
 
 
 
 

Change By:
 
 Erik Dasher 
 
 
 

Priority:
 
 Normal Trivial 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-5529) (Catalog Metadata) As a puppet administrator, I want to reduce the load on my compile masters when nothing has changed on my intended system state. (CPU load reduction of 60%)

2016-02-09 Thread Erik Dasher (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Erik Dasher commented on  PUP-5529 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: (Catalog Metadata) As a puppet administrator, I want to reduce the load on my compile masters when nothing has changed on my intended system state. (CPU load reduction of 60%)  
 
 
 
 
 
 
 
 
 
 
QA may not test this; If the CPU load reduction is only 60%, for example I fully expect that we will ship. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-5766) (Static Catalog) PE documentation for static catalogs in Burnside

2016-02-09 Thread Isaac Eldridge (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Isaac Eldridge updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5766 
 
 
 
  (Static Catalog) PE documentation for static catalogs in Burnside  
 
 
 
 
 
 
 
 
 

Change By:
 
 Isaac Eldridge 
 
 
 
 
 
 
 
 
 
 For PE documentation of static catalogs, I'm planning on covering the following:h2. Enabling static catalogs * During fresh install  or upgrades  of PE, they're enabled globally with application orchestration or not.  * During upgrades of PE, nothing happens. You must manually enable static catalogs, per environment, after upgrade.  * Documentation tracking off PE-13884. h2. Turn it offglobal setting (puppet.conf, [main]) or per-environment (environment.conf [main])h2. Conceptual overview info* In PE Burnside, this is mostly new functionality to alleviate the issues caused by agents [running off cached catalog when participating in application orchestration services|http://docs.puppetlabs.com/pe/latest/orchestrator_install.html#prepare-your-agents-for-orchestration-services]. * Describe the concepts behind how and why to use static catalogs; i.e., if file content on master changes, agents could be using incorrect content* Static catalogs ensure agents get always get correct file content as original catalog will have unique SHA (content_uri) associated with specific versions of content* The agent with static catalog enabled will only contact the master when it knows the file contents don't match desired state* (I'm working with Joe Wagner to hopefully get UX resources to draw up graphic [~josh] created while explaining this to me)h2. Question* If you want to push new "static catalogs" to environments do you use the orchestrator and/or any regular puppet run? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

Jira (PUP-5848) Relationship validation fails when a multi-resource reference is used inside an array

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

 
 
 
 
 
 
 
 Puppet /  PUP-5848 
 
 
 
  Relationship validation fails when a multi-resource reference is used inside an array  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Fix Version/s:
 
 PUP 4.4.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-5848) Relationship validation fails when a multi-resource reference is used inside an array

2016-02-09 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-5848 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Relationship validation fails when a multi-resource reference is used inside an array  
 
 
 
 
 
 
 
 
 
 
Nick Lewis we just decided to revert the change that caused this problem. I think we may have the same problem when using the relationship operators, but I am not sure. So, keeping this open for a while to investigate. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-5848) Relationship validation fails when a multi-resource reference is used inside an array

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

 
 
 
 
 
 
 
 Puppet /  PUP-5848 
 
 
 
  Relationship validation fails when a multi-resource reference is used inside an array  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Affects Version/s:
 
 PUP 4.4.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-799) speedup re-parsing by serializing valid parse result

2016-02-09 Thread Kylo Ginsberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kylo Ginsberg commented on  PUP-799 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: speedup re-parsing by serializing valid parse result  
 
 
 
 
 
 
 
 
 
 
Henrik Lindberg should we organize this into an epic with the native parser work? (Or close this in favor of another epic describing the similar idea but with the native parser?) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


  1   2   3   >