Jira (PUP-9972) Improve comments / documentation about which section a Puppet environment should be set within the puppet.conf file

2019-08-21 Thread Joel Weierman (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Joel Weierman commented on  PUP-9972  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Improve comments / documentation about which section a Puppet environment should be set within the puppet.conf file   
 

  
 
 
 
 

 
 CC Reid Vandewiele as we were talking about this earlier today.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.321797.1566422615000.67774.1566426840242%40Atlassian.JIRA.


Jira (PUP-9972) Improve comments / documentation about which section a Puppet environment should be set within the puppet.conf file

2019-08-21 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper commented on  PUP-9972  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Improve comments / documentation about which section a Puppet environment should be set within the puppet.conf file   
 

  
 
 
 
 

 
 I think we should remove environment from puppet.conf in the default case. AFAIK the only time setting the environment in puppet.conf makes sense is when using agent-specified environments. In that case, it should be set in the [agent] section, which won't require that the environment directory exist locally.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.321797.1566422615000.67763.1566426660386%40Atlassian.JIRA.


Jira (PUP-9972) Improve comments / documentation about which section a Puppet environment should be set within the puppet.conf file

2019-08-21 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper assigned an issue to Jean Bond  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9972  
 
 
  Improve comments / documentation about which section a Puppet environment should be set within the puppet.conf file   
 

  
 
 
 
 

 
Change By: 
 Josh Cooper  
 
 
Assignee: 
 Jean Bond  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.321797.1566422615000.67770.1566426660412%40Atlassian.JIRA.


Jira (PUP-9972) Improve comments / documentation about which section a Puppet environment should be set within the puppet.conf file

2019-08-21 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9972  
 
 
  Improve comments / documentation about which section a Puppet environment should be set within the puppet.conf file   
 

  
 
 
 
 

 
Change By: 
 Josh Cooper  
 
 
Component/s: 
 Docs  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.321797.1566422615000.67766.1566426660397%40Atlassian.JIRA.


Jira (PUP-9972) Improve comments / documentation about which section a Puppet environment should be set within the puppet.conf file

2019-08-21 Thread Joel Weierman (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Joel Weierman created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9972  
 
 
  Improve comments / documentation about which section a Puppet environment should be set within the puppet.conf file   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2019/08/21 2:23 PM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Joel Weierman  
 

  
 
 
 
 

 
 Puppet Version: 4.x and above Puppet Server Version: NA OS Name/Version: NA There is some confusion around the proper place to set a Puppet environment in the puppet.conf file. An older (now fixed) bug (PUP-6739) highlighted problems with placing the environment in the [user] or [agent] section of the puppet.conf. Some documentation (e.g. https://puppet.com/docs/puppet/5.3/config_file_main.html#example-agent-config) shows an example of setting the environment in main, while the defaults.rb file under environment states to not set this globally. Desired Behavior: Documentation about where to set the Puppet environment in the puppet.conf should be consistent with the code base and what is recommended as well as other existing documentation.  ** Actual Behavior: Defaults.rb has this in the comments under environment: "Given that the context and effects vary depending on the [config section](https://puppet.com/docs/puppet/latest/config_file_main.html#config-sections) in which the `environment` setting is defined, do not set it globally."      
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 
  

Jira (PDB-4486) Update to clj-parent 4.0.4

2019-08-21 Thread gepetto-bot (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 gepetto-bot created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4486  
 
 
  Update to clj-parent 4.0.4   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2019/08/21 2:18 PM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 gepetto-bot  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.321795.1566422302000.67512.156642

Jira (PUP-9970) Regression in Docker Images - puppetdb.conf permission denied

2019-08-21 Thread Morgan Rhodes (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Morgan Rhodes updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9970  
 
 
  Regression in Docker Images - puppetdb.conf permission denied   
 

  
 
 
 
 

 
Change By: 
 Morgan Rhodes  
 
 
Team: 
 Release Engineering  
 
 
Sprint: 
 Release Engineering Kanban  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.321545.1566315167000.67153.1566414540232%40Atlassian.JIRA.


Jira (PUP-9970) Regression in Docker Images - puppetdb.conf permission denied

2019-08-21 Thread Morgan Rhodes (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Morgan Rhodes assigned an issue to Morgan Rhodes  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9970  
 
 
  Regression in Docker Images - puppetdb.conf permission denied   
 

  
 
 
 
 

 
Change By: 
 Morgan Rhodes  
 
 
Assignee: 
 Morgan Rhodes  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.321545.1566315167000.67150.1566414480253%40Atlassian.JIRA.


Jira (PUP-8662) puppet plugin download doesn't re-use HTTP connections

2019-08-21 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper commented on  PUP-8662  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: puppet plugin download doesn't re-use HTTP connections   
 

  
 
 
 
 

 
 Passed master CI in a581f0ebb6  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.245716.1523666018000.67129.1566414181222%40Atlassian.JIRA.


Jira (PUP-8662) puppet plugin download doesn't re-use HTTP connections

2019-08-21 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8662  
 
 
  puppet plugin download doesn't re-use HTTP connections   
 

  
 
 
 
 

 
Change By: 
 Josh Cooper  
 
 
Release Notes Summary: 
 puppet plugin download will reuse HTTPS connections significantly speeding up the download process.  
 
 
Release Notes: 
 Bug Fix  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.245716.1523666018000.67136.1566414181253%40Atlassian.JIRA.


Jira (PUP-9971) Add ETag support to the source attribute of the file resource type for http

2019-08-21 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9971  
 
 
  Add ETag support to the source attribute of the file resource type for http   
 

  
 
 
 
 

 
Change By: 
 Josh Cooper  
 
 
Team: 
 Coremunity  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.321721.1566385045000.66620.1566409860342%40Atlassian.JIRA.


Jira (PUP-9949) Prepare release announcement (Puppet Platform 6.8.0)

2019-08-21 Thread Jean Bond (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jean Bond commented on  PUP-9949  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Prepare release announcement (Puppet Platform 6.8.0)   
 

  
 
 
 
 

 
 lgtm!  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.320255.1565301453000.66240.1566404820279%40Atlassian.JIRA.


Jira (FACT-1919) blank/negative facter cache due to timed out EC2 metadata

2019-08-21 Thread Gustavo Randich (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Gustavo Randich commented on  FACT-1919  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: blank/negative facter cache due to timed out EC2 metadata   
 

  
 
 
 
 

 
 That would be fine then. Thank you  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.307267.1556898834000.65824.1566393300166%40Atlassian.JIRA.


Jira (FACT-1919) blank/negative facter cache due to timed out EC2 metadata

2019-08-21 Thread Gabriel Nagy (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Gabriel Nagy commented on  FACT-1919  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: blank/negative facter cache due to timed out EC2 metadata   
 

  
 
 
 
 

 
 Due to the way resolvers are handled in facter, we can't have caching granularity for single facts, just cache groups (which in this case is EC2, containing both user and metadata). So if either the user-data or meta-data fact does not resolve, neither will be cached. We can provide a configurable parameter just for the HTTP request timeout (which is only used inside the ec2_resolver so it wouldn't affect other facts).  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.307267.1556898834000.65758.1566390180138%40Atlassian.JIRA.


Jira (PUP-9971) Add ETag support to the source attribute of the file resource type for http

2019-08-21 Thread beliys (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 beliys updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9971  
 
 
  Add ETag support to the source attribute of the file resource type for http   
 

  
 
 
 
 

 
Change By: 
 beliys  
 

  
 
 
 
 

 
 Now according to the documentation  (https : //puppet.com/docs/puppet/6.7/types/file.html#file-attribute-source): {code:java}  The http source uses the server Content-MD5 header as a checksum to determine if the remote file has changed. If the server response does not include that header, Puppet defaults to using the Last-Modified header.{code}But github does not use any of these headers, and it would be nice to check the ETag header for efficient file downloads from there.An example of the current headers for a file with github:{code:java}  curl -I https://raw.githubusercontent.com/major/MySQLTuner-perl/master/mysqltuner.plHTTP/1.1 200 OKContent-Security-Policy: default-src 'none'; style-src 'unsafe-inline'; sandboxStrict-Transport-Security: max-age=31536000X-Content-Type-Options: nosniffX-Frame-Options: denyX-XSS-Protection: 1; mode=blockETag: "fe63f5cd29814a03d94e68e5f503e2b0b6d65bfe"Content-Type: text/plain; charset=utf-8Cache-Control: max-age=300X-Geo-Block-List:X-GitHub-Request-Id: E292:4560:96247:C7C3E:5D5D220CContent-Length: 221615Accept-Ranges: bytesDate: Wed, 21 Aug 2019 10:54:49 GMTVia: 1.1 varnishConnection: keep-aliveX-Served-By: cache-ams21025-AMSX-Cache: HITX-Cache-Hits: 1X-Timer: S1566384890.584825,VS0,VE1Vary: Authorization,Accept-EncodingAccess-Control-Allow-Origin: *X-Fastly-Request-ID: 837bdb865032ad409e8685b36f6ccfa87832832eExpires: Wed, 21 Aug 2019 10:59:49 GMTSource-Age: 236{code}  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 


Jira (PUP-9971) Add ETag support to the source attribute of the file resource type for http

2019-08-21 Thread beliys (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 beliys created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9971  
 
 
  Add ETag support to the source attribute of the file resource type for http   
 

  
 
 
 
 

 
Issue Type: 
  New Feature  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2019/08/21 3:57 AM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 beliys  
 

  
 
 
 
 

 
 Now according to the documentation:  
 
 
 
 
 The http source uses the server Content-MD5 header as a checksum to determine if the remote file has changed. If the server response does not include that header, Puppet defaults to using the Last-Modified header.  
 
 
 
  But github does not use any of these headers, and it would be nice to check the ETag header for efficient file downloads from there. An example of the current headers for a file with github:  
 
 
 
 
 curl -I https://raw.githubusercontent.com/major/MySQLTuner-perl/master/mysqltuner.pl  
 
 
 HTTP/1.1 200 OK  
 
 
 Content-Security-Policy: default-src 'none'; style-src 'unsafe-inline'; san

Jira (PUP-9963) The 'value' field of 'selboolean' should accept Booleans

2019-08-21 Thread Henrik Lindberg (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Henrik Lindberg commented on  PUP-9963  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: The 'value' field of 'selboolean' should accept Booleans   
 

  
 
 
 
 

 
 It would be reasonable to fix this by allowing `Boolean` to be constructed from "on", and "off" (since it already supports variations of true/false, yes/no strings). Then, this can be implemented so that the selbolean accepts `Init[Boolean]` and calls `Boolean(val)` to create an actual boolean value.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.320668.1565704234000.65633.1566384000156%40Atlassian.JIRA.


Jira (PUP-9963) The 'value' field of 'selboolean' should accept Booleans

2019-08-21 Thread Gheorghe Popescu (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Gheorghe Popescu updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9963  
 
 
  The 'value' field of 'selboolean' should accept Booleans   
 

  
 
 
 
 

 
Change By: 
 Gheorghe Popescu  
 
 
Story Points: 
 3  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.320668.1565704234000.65600.1566381240630%40Atlassian.JIRA.


Jira (PUP-9962) stdlib : When ensure_resource() is used, it should correctly report duplicate resource declaration issues with more correct file and line numbers

2019-08-21 Thread Henrik Lindberg (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Henrik Lindberg commented on  PUP-9962  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: stdlib : When ensure_resource() is used, it should correctly report duplicate resource declaration issues with more correct file and line numbers   
 

  
 
 
 
 

 
 Seems like `ensure_resource` should set file/line information - it does not do that now so the created resources simply lack location information. Could be fixed by reimplementing the function as a 4x function (while not strictly required though) and using the `PuppetStack` to get the calling file/line (caller of `ensure_resource`) and propagating that information onwards should ensure that the conflicting resources have this information. Have not actually tested if that would fix this, but I think it is a good bet.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.319159.1564655694000.65598.1566381240619%40Atlassian.JIRA.


Jira (PUP-9969) Update Public-facing Puppet docs to remove Ubuntu 14.04

2019-08-21 Thread Gheorghe Popescu (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Gheorghe Popescu updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9969  
 
 
  Update Public-facing Puppet docs to remove Ubuntu 14.04   
 

  
 
 
 
 

 
Change By: 
 Gheorghe Popescu  
 
 
Sprint: 
 PR NW  -  Triage  2019-09-03  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.321530.1566311767000.6.1566380520821%40Atlassian.JIRA.


Jira (PUP-9955) Update Public-facing Puppet docs to include winfips-2012r2-x64

2019-08-21 Thread Gheorghe Popescu (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Gheorghe Popescu updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9955  
 
 
  Update Public-facing Puppet docs to include winfips-2012r2-x64   
 

  
 
 
 
 

 
Change By: 
 Gheorghe Popescu  
 
 
Sprint: 
 PR NW  -  Triage  2019-09-03  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.320402.1565371341000.65543.1566380461298%40Atlassian.JIRA.


Jira (PUP-9955) Update Public-facing Puppet docs to include winfips-2012r2-x64

2019-08-21 Thread Gheorghe Popescu (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Gheorghe Popescu updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9955  
 
 
  Update Public-facing Puppet docs to include winfips-2012r2-x64   
 

  
 
 
 
 

 
Change By: 
 Gheorghe Popescu  
 
 
Story Points: 
 1  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.320402.1565371341000.65513.1566380280274%40Atlassian.JIRA.


Jira (PUP-9465) group resource type misunderstands/misuses libuser

2019-08-21 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9465  
 
 
  group resource type misunderstands/misuses libuser   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Sprint: 
 NW - 2019-08-21 , NW - 2019-09-03  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.293306.1548368109000.65445.1566379024163%40Atlassian.JIRA.


Jira (PUP-9041) AIX nim provider can't be used on a NIM master

2019-08-21 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9041  
 
 
  AIX nim provider can't be used on a NIM master   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Sprint: 
 NW - 2019-08-07, NW - 2019-08-21 , NW - 2019-09-03  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.267945.153332494.65417.1566379024044%40Atlassian.JIRA.


Jira (PUP-9605) Type package (provider yum) fails when handling kernel packages

2019-08-21 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9605  
 
 
  Type package (provider yum) fails when handling kernel packages   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Sprint: 
 PR - 2019-06-25, PR - 2019-07-10, PR - 2019-07-23, NW - 2019-08-07, NW - 2019-08-21 , NW - 2019-09-03  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.303636.1554712703000.65392.1566379023936%40Atlassian.JIRA.


Jira (FACT-1967) Unable to compile libwhereami 0.2.2 on latest Archlinux

2019-08-21 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-1967  
 
 
  Unable to compile libwhereami 0.2.2 on latest Archlinux   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Sprint: 
 NW - 2019-08-21 , NW - 2019-09-03  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.318292.1564323614000.65453.1566379024195%40Atlassian.JIRA.


Jira (PUP-6134) Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows

2019-08-21 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-6134  
 
 
  Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Sprint: 
 NW - 2019-08-21 , NW - 2019-09-03  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.125405.1459986358000.65441.1566379024144%40Atlassian.JIRA.


Jira (PUP-9754) Log resident configuration upon daemon launch

2019-08-21 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9754  
 
 
  Log resident configuration upon daemon launch   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Sprint: 
 PR - 2019-07-23, NW - 2019-08-07, NW - 2019-08-21 , NW - 2019-09-03  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.312512.1560543853000.65401.1566379023972%40Atlassian.JIRA.


Jira (FACT-1919) blank/negative facter cache due to timed out EC2 metadata

2019-08-21 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-1919  
 
 
  blank/negative facter cache due to timed out EC2 metadata   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Sprint: 
 PR - 2019-07-23, NW - 2019-08-07, NW - 2019-08-21 , NW - 2019-09-03  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.307267.1556898834000.65396.1566379023952%40Atlassian.JIRA.


Jira (PUP-9719) Cannot run Puppet Agent as Administrator if first PA run is done as System

2019-08-21 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9719  
 
 
  Cannot run Puppet Agent as Administrator if first PA run is done as System   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Sprint: 
 PR - 2019-06-25, PR - 2019-07-10, PR - 2019-07-23, NW - 2019-08-07, NW - 2019-08-21 , NW - 2019-09-03  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.310162.1558726819000.65389.1566379023921%40Atlassian.JIRA.


Jira (PUP-9959) Plugin sync to get latest fact set when running puppet facts upload

2019-08-21 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9959  
 
 
  Plugin sync to get latest fact set when running puppet facts upload   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Sprint: 
 NW - 2019-08-07, NW - 2019-08-21 , NW - 2019-09-03  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.317346.1563668147000.65408.1566379024005%40Atlassian.JIRA.


Jira (PUP-9962) stdlib : When ensure_resource() is used, it should correctly report duplicate resource declaration issues with more correct file and line numbers

2019-08-21 Thread Norman Heaney (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Norman Heaney commented on  PUP-9962  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: stdlib : When ensure_resource() is used, it should correctly report duplicate resource declaration issues with more correct file and line numbers   
 

  
 
 
 
 

 
 Hi Gareth Just following up on this issue, any other comments? As Florin has verified the root causes is not within the stdlib module.  I'm not sure which team is best placed to close out on this ticket thanks norman ]  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.319159.1564655694000.65237.1566371880180%40Atlassian.JIRA.