Jira (PUP-6532) Document Sensitive data type (language specification)

2016-07-22 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6532 
 
 
 
  Document Sensitive data type (language specification)  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Story Points:
 
 1 
 
 
 

Summary:
 
 Document Sensitive data type  (language specification) 
 
 
 

Sprint:
 
 Language Triage 
 
 
 

Scrum Team:
 
 Language 
 
 
 

Release Notes:
 
 Not Needed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-6530) create_resources() doesn't include the file or line reference in resources it creates

2016-07-22 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-6530 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: create_resources() doesn't include the file or line reference in resources it creates  
 
 
 
 
 
 
 
 
 
 
Thanks, this is a known problem. There is work in progress on another ticket that adds the file and line numbers for create_reources (PUP-5949) where we have made a major refactoring of how resources are created.  
The test case shown here is great to have to verify that the solution in PUP-5949 works as it should. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-6530) create_resources() doesn't include the file or line reference in resources it creates

2016-07-22 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6530 
 
 
 
  create_resources() doesn't include the file or line reference in resources it creates  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Story Points:
 
 1 
 
 
 

Release Notes Summary:
 
 When creating resources using `create_resources` function there were no file and line information included in the resulting catalog. This is now fixed and this will improve downstream tooling that requires such information. 
 
 
 

Sprint:
 
 Language 2016-08-10 (3rd 1.6.0 
 
 
 

Scrum Team:
 
 Language 
 
 
 

Release Notes:
 
 Bug Fix 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 

Jira (PUP-6530) create_resources() doesn't include the file or line reference in resources it creates

2016-07-22 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-6530 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: create_resources() doesn't include the file or line reference in resources it creates  
 
 
 
 
 
 
 
 
 
 
work on this ticket should be minimal - perhaps add tests that file/line is indeed included (it should be since code now passes through the same logic irrespective of how the resource was created (PUP-5949); from the language, or create_resources. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


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

2016-07-22 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

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

Change By:
 
 Henrik Lindberg 
 
 
 

Scope Change Category:
 
 Adopted 
 
 
 

Scope Change Reason:
 
 Ran out of immediately actionable work 
 
 
 

Acceptance Criteria:
 
 That an _expression_ in parentheses first on a line will not act as a continuation of the last _expression_ on the preceding line as if it was a function/method name that is being called.The following example should not fail.{code:puppet}$a = []($a).each |$x| { }{code} 
 
 
 

Labels:
 
 DSL 
 
 
 

Story Points:
 
 1 
 
 
 

Release Notes Summary:
 
 When starting a new line with a '(' this would be interpreted as an attempt to continue the last _expression_ on the preceding line as if it was the name of a function to call. This is now changed so that for a '(' to be recognized as a parenthesis opening an argument list it must be placed on the same line as the name of the function. Otherwise it will be taken as the end of the previous _expression_ and starting a new parenthesized/grouping _expression_. 
 
 
 

Sprint:
 
 Language 2016-07-27 
 
 
 

Release Notes:
 
 Bug Fix 
 
 
 
 
 
 
 
 

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

2016-07-22 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

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

Change By:
 
 Henrik Lindberg 
 
 
 

Fix Version/s:
 
 PUP 4.6.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-5949) Update loaders to load pcore in place of ruby resource types when compiling

2016-07-22 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg assigned an issue to Henrik Lindberg 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5949 
 
 
 
  Update loaders to load pcore in place of ruby resource types when compiling  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Assignee:
 
 Henrik Lindberg 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-5948) write tool to transform ruby resource type to pcore resource type

2016-07-22 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg assigned an issue to Henrik Lindberg 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5948 
 
 
 
  write tool to transform ruby resource type to pcore resource type  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Assignee:
 
 Henrik Lindberg 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


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

2016-07-22 Thread Thomas Hallgren (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Hallgren commented on  PUP-5849 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Newline is not sufficient to avoid parsing as a function call  
 
 
 
 
 
 
 
 
 
 
Merged to master at 7c0226b 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-6536) Puppet agent does not start properly with systemd the first time

2016-07-22 Thread Christophe Trefois (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christophe Trefois created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6536 
 
 
 
  Puppet agent does not start properly with systemd the first time  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 PUP 3.8.5 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/07/22 8:40 AM 
 
 
 

Environment:
 
 
Ubuntu 16.04.01 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Christophe Trefois 
 
 
 
 
 
 
 
 
 
 
Hi, 
When using Foreman to provision a VM, on first boot, the puppet agent times out with the following error in journalctl 
 
 
 
 
 
 
Jul 22 15:05:10 cfw-2-server systemd[1]: Starting Puppet agent... 
 
 
 
 
Jul 22 15:05:10 cfw-2-server systemd[1]: Starting LSB: Set the CPU Frequency Scaling governor to "ondemand"... 
 

Jira (PUP-6536) Puppet agent does not start properly with systemd the first time

2016-07-22 Thread Christophe Trefois (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christophe Trefois commented on  PUP-6536 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Puppet agent does not start properly with systemd the first time  
 
 
 
 
 
 
 
 
 
 
Here is the template that was used to built the VM using Foreman on oVirt 3.6 
 
 
 
 
 
 
apt-get update 
 
 
 
 
apt-get install -y puppet 
 
 
 
 
  
 
 
 
 
cat > /etc/puppet/puppet.conf << EOF 
 
 
 
 
  
 
 
 
 
  
 
 
 
 
[main] 
 
 
 
 
vardir = /var/lib/puppet 
 
 
 
 
logdir = /var/log/puppet 
 
 
 
 
rundir = /var/run/puppet 
 
 
 
 
ssldir = \$vardir/ssl 
 
 

Jira (PUP-6499) `puppet resource user` does not work on Windows French edition

2016-07-22 Thread Moses Mendoza (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Moses Mendoza commented on  PUP-6499 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: `puppet resource user` does not work on Windows French edition  
 
 
 
 
 
 
 
 
 
 
Confirmed w/ associated PR on German Windows: Failure repro: 
 
 
 
 
 
 
PS C:\Users\moses\development\puppet> be puppet resource user 
 
 
 
 
DL is deprecated, please use Fiddle 
 
 
 
 
Error: Could not run: incompatible character encodings: CP850 and UTF-8
 
 
 
 
 
 
 
Success: 
 
 
 
 
 
 
PS C:\Users\moses\development\puppet> be puppet resource user 
 
 
 
 
DL is deprecated, please use Fiddle 
 
 
 
 
user { 'Administrator': 
 
 
 
 
  ensure  => 'present', 
 
 
 
 
  comment => 'Vordefiniertes Konto für die Verwaltung des Computers bzw. der Domäne', 
 
 
 
 
  groups  => ['VORDEFINIERT\Administr

Jira (PUP-6499) `puppet resource user` does not work on Windows French edition

2016-07-22 Thread Glenn Sarti (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Glenn Sarti assigned an issue to Moses Mendoza 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6499 
 
 
 
  `puppet resource user` does not work on Windows French edition  
 
 
 
 
 
 
 
 
 

Change By:
 
 Glenn Sarti 
 
 
 

Assignee:
 
 Moses Mendoza 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PDB-2892) Nested implicit subqueries fail unless trivial

2016-07-22 Thread Andrew Roetker (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andrew Roetker updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2892 
 
 
 
  Nested implicit subqueries fail unless trivial  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andrew Roetker 
 
 
 

Fix Version/s:
 
 PDB 4.2.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PDB-2892) Nested implicit subqueries fail unless trivial

2016-07-22 Thread Andrew Roetker (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andrew Roetker updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2892 
 
 
 
  Nested implicit subqueries fail unless trivial  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andrew Roetker 
 
 
 

Sprint:
 
 Hopper 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PDB-2901) (maint) fix package build host to unbreak our sed in s3 transfer

2016-07-22 Thread gepetto-bot (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 gepetto-bot created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2901 
 
 
 
  (maint) fix package build host to unbreak our sed in s3 transfer  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/07/22 11:23 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 gepetto-bot 
 
 
 
 
 
 
 
 
 
 
This should fix our s3 transfer so repos are available in acceptance tests. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
   

Jira (PUP-6537) unresolvable environment catalogs are compiled

2016-07-22 Thread R.I.Pienaar (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 R.I.Pienaar created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6537 
 
 
 
  unresolvable environment catalogs are compiled  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 PUP 4.5.2 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 Puppet Server 
 
 
 

Created:
 

 2016/07/22 11:27 AM 
 
 
 

Environment:
 
 
puppetserver 2.4.0 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 R.I.Pienaar 
 
 
 
 
 
 
 
 
 
 
The following site yields a unresolvable catalog: 
 
 
 
 
 
 
site { 
 
 
 
 

Jira (PDB-2902) Strengthen warning against the embedded db

2016-07-22 Thread gepetto-bot (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 gepetto-bot created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2902 
 
 
 
  Strengthen warning against the embedded db  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/07/22 11:35 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 gepetto-bot 
 
 
 
 
 
 
 
 
 
 
PuppetDB 4.0 no longer supports the embedded database. We need to be more explicit about that. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
  

Jira (PUP-6537) unresolvable environment catalogs are compiled

2016-07-22 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6537 
 
 
 
  unresolvable environment catalogs are compiled  
 
 
 
 
 
 
 
 
 
 
Ping Nick Lewis David Lutterkort 
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Scrum Team:
 
 Application Orchestration 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-6536) Puppet agent does not start properly with systemd the first time

2016-07-22 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6536 
 
 
 
  Puppet agent does not start properly with systemd the first time  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Scrum Team:
 
 Client Platform 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-6538) deprecate hiera_xxx functions (in favour of lookup)

2016-07-22 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6538 
 
 
 
  deprecate hiera_xxx functions (in favour of lookup)  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/07/22 1:46 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Henrik Lindberg 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-6538) deprecate hiera_xxx functions (in favour of lookup)

2016-07-22 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6538 
 
 
 
  deprecate hiera_xxx functions (in favour of lookup)  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Issue Type:
 
 Bug Improvement 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-6539) add removal tickets for puppet 5.0 for hiera_xxx

2016-07-22 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6539 
 
 
 
  add removal tickets for puppet 5.0 for hiera_xxx  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/07/22 1:47 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Henrik Lindberg 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-6539) add removal tickets for puppet 5.0 for hiera_xxx

2016-07-22 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6539 
 
 
 
  add removal tickets for puppet 5.0 for hiera_xxx  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Issue Type:
 
 Bug Improvement 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-6499) `puppet resource user` does not work on Windows French edition

2016-07-22 Thread Glenn Sarti (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Glenn Sarti commented on  PUP-6499 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: `puppet resource user` does not work on Windows French edition  
 
 
 
 
 
 
 
 
 
 
Merged into stable at; https://github.com/puppetlabs/puppet/commit/f17c853601c34f0cfd05e8d8e70157a111a516d2 
Will wait for green CI run before merging up to master 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-5463) undef not usable in collector search

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

 
 
 
 
 
 
 
 Puppet /  PUP-5463 
 
 
 
  undef not usable in collector search  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Assignee:
 
 Thomas Hallgren 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-6499) `puppet resource user` does not work on Windows French edition

2016-07-22 Thread Glenn Sarti (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Glenn Sarti assigned an issue to Glenn Sarti 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6499 
 
 
 
  `puppet resource user` does not work on Windows French edition  
 
 
 
 
 
 
 
 
 

Change By:
 
 Glenn Sarti 
 
 
 

Assignee:
 
 Moses Mendoza Glenn Sarti 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PDB-2843) Exceptions when using functions

2016-07-22 Thread Wyatt Alt (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wyatt Alt assigned an issue to Wyatt Alt 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2843 
 
 
 
  Exceptions when using functions  
 
 
 
 
 
 
 
 
 

Change By:
 
 Wyatt Alt 
 
 
 

Assignee:
 
 Wyatt Alt 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-6527) hiera_include() should be ignored when compiling an environment catalog

2016-07-22 Thread Alex Dreyer (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alex Dreyer commented on  PUP-6527 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: hiera_include() should be ignored when compiling an environment catalog  
 
 
 
 
 
 
 
 
 
 
includes can also happen inside the site block. It's unclear to me what we should do with include anywhere during environment catalog compilation. But normal includes are not really causing problems unlike hiera_include so we probably don't have to decide that right now. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-6083) Use --strict option to deprecate Class[] where begins with a capital letter.

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

 
 
 
 
 
 
 
 Puppet /  PUP-6083 
 
 
 
  Use --strict option to deprecate Class[] where  begins with a capital letter.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Assignee:
 
 Thomas Hallgren 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-5949) Update loaders to load pcore in place of ruby resource types when compiling

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

 
 
 
 
 
 
 
 Puppet /  PUP-5949 
 
 
 
  Update loaders to load pcore in place of ruby resource types when compiling  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Assignee:
 
 Henrik Lindberg 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-5949) Update loaders to load pcore in place of ruby resource types when compiling

2016-07-22 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-5949 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Update loaders to load pcore in place of ruby resource types when compiling  
 
 
 
 
 
 
 
 
 
 
Merged to master at: bafca0b 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-6499) `puppet resource user` does not work on Windows French edition

2016-07-22 Thread Glenn Sarti (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Glenn Sarti commented on  PUP-6499 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: `puppet resource user` does not work on Windows French edition  
 
 
 
 
 
 
 
 
 
 
CI started for stable; https://jenkins.puppetlabs.com/view/puppet-agent/view/stable/view/puppet/job/platform_puppet_init-van-component_stable/215/ 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-6499) `puppet resource user` does not work on Windows French edition

2016-07-22 Thread Ethan Brown (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ethan Brown updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6499 
 
 
 
  `puppet resource user` does not work on Windows French edition  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ethan Brown 
 
 
 

Fix Version/s:
 
 PUP 4.5.4 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-6540) Allow Windows group resource to specify SID as title

2016-07-22 Thread Ethan Brown (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ethan Brown created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6540 
 
 
 
  Allow Windows group resource to specify SID as title  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Affects Versions:
 

 PUP 4.5.2 
 
 
 

Assignee:
 
 Kylo Ginsberg 
 
 
 

Components:
 

 Types and Providers, Windows 
 
 
 

Created:
 

 2016/07/22 2:41 PM 
 
 
 

Labels:
 

 windows i18n utf-8 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Ethan Brown 
 
 
 
 
 
 
 
 
 
 
Without being able to use a SID in the title of a group resource on Windows, it can be difficult to write a manifest that works properly on internationalized versions of Windows. Take for instance, adding a user to the Administrators group. 
In English, this works to modify the Administrators group and add user bob (presuming they already exist): 
 
 
 
 
 
 

Jira (PUP-6540) Allow Windows group resource to specify SID as title

2016-07-22 Thread Ethan Brown (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ethan Brown updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6540 
 
 
 
  Allow Windows group resource to specify SID as title  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ethan Brown 
 
 
 
 
 
 
 
 
 
 Without being able to use a SID in the title of a group resource on Windows, it can be difficult to write a manifest that works properly on internationalized versions of Windows.  Take for instance, adding a user to the {{Administrators}} group.In English, this works to modify the {{Administrators}} group and add user {{bob}} (presuming they already exist):{code}group { 'Administrators':  members => ['bob'],  auth_membership => false}{code}The same code on French Windows, will actually create a new group named {{Administrators}}, which may be surprising.  The user likely expected that the well-defined Administrators group with SID {{S-1-5-32-544}} was used, which in this case is localized to {{Administrateurs}}.  For cases where manifests are running only in one localized environment, this may already be well understood by users.However, this becomes quite painful if working across an environment with more than 1 localized set of accounts , as manifests must be special cased for each additional environment .The solution to referring to well-known accounts is typically to use the SIDs as defined at https://msdn.microsoft.com/en-us/library/windows/desktop/aa379649(v=vs.85).aspx to circumvent any localization problems.However, the group type does not support SIDs as titles, but likely could with some additional munging code. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message b

Jira (PUP-6435) Replace sensitive data marker type with resource metadata after catalog compilation

2016-07-22 Thread Adrien Thebo (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Adrien Thebo updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6435 
 
 
 
  Replace sensitive data marker type with resource metadata after catalog compilation  
 
 
 
 
 
 
 
 
 

Change By:
 
 Adrien Thebo 
 
 
 

Scope Change Category:
 
 Found 
 
 
 

Scope Change Reason:
 
 Work needs to be done by a different team. 
 
 
 

Sprint:
 
 Client 2016-07-27 facter.conf 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-6435) Replace sensitive data marker type with resource metadata after catalog compilation

2016-07-22 Thread Adrien Thebo (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Adrien Thebo updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6435 
 
 
 
  Replace sensitive data marker type with resource metadata after catalog compilation  
 
 
 
 
 
 
 
 
 

Change By:
 
 Adrien Thebo 
 
 
 

Story Points:
 
 3 
 
 
 

Scrum Team:
 
 Client Platform 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PDB-2903) (maint) Fix typo in update-checking test and reorder assertions

2016-07-22 Thread gepetto-bot (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 gepetto-bot created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2903 
 
 
 
  (maint) Fix typo in update-checking test and reorder assertions  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/07/22 3:39 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 gepetto-bot 
 
 
 
 
 
 
 
 
 
 
so that expected proceeds actual. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
   

Jira (FACT-1467) Add Windows computer_sid fact

2016-07-22 Thread Ethan Brown (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ethan Brown created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1467 
 
 
 
  Add Windows computer_sid fact  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Affects Versions:
 

 FACT 3.1.8 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 Windows 
 
 
 

Created:
 

 2016/07/22 3:44 PM 
 
 
 

Labels:
 

 windows 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Ethan Brown 
 
 
 
 
 
 
 
 
 
 
When referring to the Administrator account or Guest account on Windows, those well-known and commonly used names cannot be referred to with well-known SIDs - see https://msdn.microsoft.com/en-us/library/windows/desktop/aa379649(v=vs.85).aspx 
Because these account names may also be localized on international versions of Windows, such as French and German - it can be difficult to write a manifest that doesn't need to vary based on the current OS language. 
Administrator and Guest build on the computer's SID, which varies on an individual computer basis, like: 
 

   

Jira (PUP-6541) Acceptance: Validated sensitive data type

2016-07-22 Thread John Duarte (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Duarte created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6541 
 
 
 
  Acceptance: Validated sensitive data type  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Task 
 
 
 

Assignee:
 
 Eric Sorenson 
 
 
 

Components:
 

 QA 
 
 
 

Created:
 

 2016/07/22 3:53 PM 
 
 
 

Fix Versions:
 

 PUP 4.6.0 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 John Duarte 
 
 
 
 
 
 
 
 
 
 
Create acceptance tests to validate phase 1 of the 'Sensitive' data type. 

`Sensitive` data type that allows users to mark Puppet resource properties as sensitive. When a property is marked as sensitive, trying to log the value during compilation prints a redacted value and applying a property marked as sensitive redacts the logs and report events. Using the feature is a simple matter of creating a Puppet value with the Sensitive type, EG `Sensitive("mypassword")`.
 
 
 
 
 
 
 
 
 
 
 
 
 

   

Jira (FACT-1467) Add Windows computer_sid fact

2016-07-22 Thread Ethan Brown (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ethan Brown updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1467 
 
 
 
  Add Windows computer_sid fact  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ethan Brown 
 
 
 
 
 
 
 
 
 
 When referring to the {{Administrator}} account or {{Guest}} account on Windows, those well-known and commonly used names cannot be referred to with well-known SIDs - see https://msdn.microsoft.com/en-us/library/windows/desktop/aa379649(v=vs.85).aspxBecause these account names may also be localized on international versions of Windows, such as French and German - it can be difficult to write a manifest that doesn't need to vary based on the current OS language.{{Administrator}} and {{Guest}} build on the computer's SID, which varies on an individual computer basis, like:* {{-500}} is appended to the computer SID for the {{Administrator}} account* {{-501}} is appended to the computer SID for the {{Guest}} accountTo make it easier to refer to these accounts universally, regardless of which computer they're run on, whether the accounts have been localized or renamed, a first step would to be produce a Fact value containing the computers SID.An easy way to do this is to call the [LookupAccountName|https://msdn.microsoft.com/en-us/library/windows/desktop/aa379159(v=vs.85).aspx] Windows API, passing in the computers name.This value is also stored in the registry at {{HKLM\security\sam\domains\account}}  (particularly in the 24 byte span between 272 and 295 in the byte array) , if the user has permission to access that key  - see http://powershellers . blogspot.com/2009/06/how-to-get-computer-sid-using.html for more details 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 

Jira (PUP-6499) `puppet resource user` does not work on Windows French edition

2016-07-22 Thread Glenn Sarti (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Glenn Sarti commented on  PUP-6499 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: `puppet resource user` does not work on Windows French edition  
 
 
 
 
 
 
 
 
 
 
CI completed with success at; https://jenkins.puppetlabs.com/view/puppet-agent/view/stable/view/puppet/job/platform_puppet_pkg-van-promote_stable/162/ 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-6541) Acceptance: Validate sensitive data type

2016-07-22 Thread John Duarte (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Duarte updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6541 
 
 
 
  Acceptance: Validate sensitive data type  
 
 
 
 
 
 
 
 
 

Change By:
 
 John Duarte 
 
 
 

Summary:
 
 Acceptance:  Validated  Validate  sensitive data type 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-6499) `puppet resource user` does not work on Windows French edition

2016-07-22 Thread Glenn Sarti (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Glenn Sarti assigned an issue to qa 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6499 
 
 
 
  `puppet resource user` does not work on Windows French edition  
 
 
 
 
 
 
 
 
 

Change By:
 
 Glenn Sarti 
 
 
 

Status:
 
 Ready for  CI  Test 
 
 
 

Assignee:
 
 Glenn Sarti qa 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-6499) `puppet resource user` does not work on Windows French edition

2016-07-22 Thread Glenn Sarti (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Glenn Sarti commented on  PUP-6499 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: `puppet resource user` does not work on Windows French edition  
 
 
 
 
 
 
 
 
 
 
Merged up to master at; https://github.com/puppetlabs/puppet/commit/492518384d40a849f497f934e23ca09cd41cb120 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-6499) `puppet resource user` does not work on Windows French edition

2016-07-22 Thread Glenn Sarti (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Glenn Sarti assigned an issue to Erick Banks 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6499 
 
 
 
  `puppet resource user` does not work on Windows French edition  
 
 
 
 
 
 
 
 
 

Change By:
 
 Glenn Sarti 
 
 
 

Assignee:
 
 qa Erick Banks 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-6542) Group resource emits misleading change notification with auth_membership => false

2016-07-22 Thread Ethan Brown (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ethan Brown created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6542 
 
 
 
  Group resource emits misleading change notification with auth_membership => false  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Affects Versions:
 

 PUP 4.5.2 
 
 
 

Assignee:
 
 Kylo Ginsberg 
 
 
 

Components:
 

 Types and Providers, Windows 
 
 
 

Created:
 

 2016/07/22 6:08 PM 
 
 
 

Labels:
 

 windows 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Ethan Brown 
 
 
 
 
 
 
 
 
 
 
When Puppet is adding users to an existing group, its change report is misleading. 
Take the following manifest (from French Windows): 
 
 
 
 
 
 
group { 'Administrateurs':  
 
 
   

Jira (PUP-6531) puppet service provider recognition on Ubuntu can be improved

2016-07-22 Thread Nishanth Aravamudan (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Nishanth Aravamudan commented on  PUP-6531 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: puppet service provider recognition on Ubuntu can be improved  
 
 
 
 
 
 
 
 
 
 
The above PR now passes CI and I think is the right direction. Not sure if it could be generalized for other OSes yet or not, but I think generally the presence of /run/systemd/system is meant to indicate systemd should be used (rather than relying on any specific versions). Certainly at least for Ubuntu. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-6542) Group resource emits misleading change notification with auth_membership => false

2016-07-22 Thread Ethan Brown (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ethan Brown updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6542 
 
 
 
  Group resource emits misleading change notification with auth_membership => false  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ethan Brown 
 
 
 
 
 
 
 
 
 
 When Puppet is adding users to an existing group, its change report is misleading.Take the following manifest (from French Windows):{code}group { 'Administrateurs':  ensure => 'present',  auth_membership => false,  members => ['AUTORITE NT\\Utilisateurs authentifiés']}{code}It emits the following message{code}# $ bundle exec puppet apply utf8.pp# DL is deprecated, please use Fiddle# Notice: Compiled catalog for wbsk7zl860xwiqa.delivery.puppetlabs.net in environment production in 0.06 seconds# Notice: /Stage[main]/Main/Group[Administrateurs]/members: members changed 'WBSK7ZL860XWIQA\Administrateur,WBSK7ZL860XWIQA\tester,WBSK7ZL860XWIQA\Administrator,WBSK7ZL860XWIQA\cyg_server,WBSK7ZL860XWIQA\bla' to 'AUTORITE NT\Utilisateurs authentifiés'# Notice: Applied catalog in 0.11 seconds{code}However, the message is incorrect, given the actual group membership:{code}$ bundle exec puppet resource group AdministrateursDL is deprecated, please use Fiddlegroup { 'Administrateurs':  ensure  => 'present',  gid => 'S-1-5-32-544',  members => ['Administrateur', 'tester', 'Administrator', 'cyg_server', 'bla', 'Utilisateurs authentifiés'],}{code} Expected behavior should be like what the user resource does:{code}user { 'Invité':  ensure => 'present',  auth_membership => minimum,  groups => ['BUILTIN\\Administrateurs']}{code}Emits the following message:{code}bundle exec puppet apply .\user.ppDL is deprecated, please use FiddleNotice: Compiled catalog for wbsk7zl860xwiqa.delivery.puppetlabs.net in environment production in 0.08 secondsNotice: /Stage[main]/Main/User[Invité]/groups: groups changed 'BUILTIN\Invités' to ['BUILTIN\Administrateurs', 'BUILTIN\Invités']Notice: Applied catalog in 0.11 seconds{code}For resource{code}user { 'Invité':  ensure  => 'present',  comment => 'Compte d'utilisateur invité',  groups  => ['BUILTIN\Invités', 'BUILTIN\Administrateurs'],  uid => 'S-1-5-21-441295449-3808246871-2843121223-501',}{code} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 

Jira (PUP-6542) Group resource emits misleading change notification with auth_membership => false

2016-07-22 Thread Ethan Brown (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ethan Brown updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6542 
 
 
 
  Group resource emits misleading change notification with auth_membership => false  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ethan Brown 
 
 
 
 
 
 
 
 
 
 When Puppet is adding users to an existing group, its change report is misleading.Take the following manifest (from French Windows):{code}group { 'Administrateurs':  ensure => 'present',  auth_membership => false,  members => ['AUTORITE NT\\Utilisateurs authentifiés']}{code}It emits the following message{code}# $ bundle exec puppet apply utf8.pp# DL is deprecated, please use Fiddle# Notice: Compiled catalog for wbsk7zl860xwiqa.delivery.puppetlabs.net in environment production in 0.06 seconds# Notice: /Stage[main]/Main/Group[Administrateurs]/members: members changed 'WBSK7ZL860XWIQA\Administrateur,WBSK7ZL860XWIQA\tester,WBSK7ZL860XWIQA\Administrator,WBSK7ZL860XWIQA\cyg_server,WBSK7ZL860XWIQA\bla' to 'AUTORITE NT\Utilisateurs authentifiés'# Notice: Applied catalog in 0.11 seconds{code}However, the message is incorrect, given the actual group membership:{code}$ bundle exec puppet resource group AdministrateursDL is deprecated, please use Fiddlegroup { 'Administrateurs':  ensure  => 'present',  gid => 'S-1-5-32-544',  members => ['Administrateur', 'tester', 'Administrator', 'cyg_server', 'bla', 'Utilisateurs authentifiés'],}{code}Expected behavior should be like what the user resource does:{code}user { 'Invité':  ensure => 'present',  auth_membership => minimum,  groups => ['BUILTIN\\Administrateurs']}{code}Emits the following message:{code}bundle exec puppet apply .\user.ppDL is deprecated, please use FiddleNotice: Compiled catalog for wbsk7zl860xwiqa.delivery.puppetlabs.net in environment production in 0.08 secondsNotice: /Stage[main]/Main/User[Invité]/groups: groups changed 'BUILTIN\Invités' to ['BUILTIN\Administrateurs', 'BUILTIN\Invités']Notice: Applied catalog in 0.11 seconds{code}For resource{code} bundle exec puppet resource user user  { 'Invité':  ensure  => 'present',  comment => 'Compte d'utilisateur invité',  groups  => ['BUILTIN\Invités', 'BUILTIN\Administrateurs'],  uid => 'S-1-5-21-441295449-3808246871-2843121223-501',}{code} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment