Jira (PUP-8027) gem provider does not work behind proxy

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


 
 
 
 

 
 
 

 
   
 Josh Cooper commented on  PUP-8027  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: gem provider does not work behind proxy   
 

  
 
 
 
 

 
 Package providers like yum and apt allow proxy settings to be configured in their respective config files, such as /etc/apt/apt.conf.d/proxy.conf for apt. I'm thinking we should do the same for gems. For example. add the following to /etc/gemrc:  
 
 
 
 
 ---  
 
 
 http-proxy: http://example.com:80
  
 
 
 
  Trying to reuse install_options for things other than the gem install command is going to be problematic, as some options may not be suitable for gem list.  
 

  
 
 
 
 

 
 
 

 
 
 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 

Jira (PUP-4470) Puppet's http connection factory doesn't support authenticating proxies

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


 
 
 
 

 
 
 

 
   
 Josh Cooper updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-4470  
 
 
  Puppet's http connection factory doesn't support authenticating proxies   
 

  
 
 
 
 

 
Change By: 
 Josh Cooper  
 
 
Fix Version/s: 
 PUP 6.8.0  
 
 
Fix Version/s: 
 PUP 6.4.4  
 
 
Fix Version/s: 
 PUP 6.0.11  
 
 
Fix Version/s: 
 PUP 5.5.17  
 

  
 
 
 
 

 
 
 

 
 
 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 

Jira (PUP-4470) Puppet's http connection factory doesn't support authenticating proxies

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


 
 
 
 

 
 
 

 
   
 Josh Cooper updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-4470  
 
 
  Puppet's http connection factory doesn't support authenticating proxies   
 

  
 
 
 
 

 
Change By: 
 Josh Cooper  
 
 
Sprint: 
 Platform Core 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.77763.1430247156000.47737.1565240880247%40Atlassian.JIRA.


Jira (PUP-4470) Puppet's http connection factory doesn't support authenticating proxies

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


 
 
 
 

 
 
 

 
   
 Josh Cooper assigned an issue to Josh Cooper  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-4470  
 
 
  Puppet's http connection factory doesn't support authenticating proxies   
 

  
 
 
 
 

 
Change By: 
 Josh Cooper  
 
 
Assignee: 
 Josh Cooper  
 

  
 
 
 
 

 
 
 

 
 
 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.77763.1430247156000.47733.1565240820226%40Atlassian.JIRA.


Jira (BOLT-1286) Document YAML plan constructs that can't be converted

2019-08-07 Thread Chris Cowell (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Chris Cowell commented on  BOLT-1286  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Document YAML plan constructs that can't be converted   
 

  
 
 
 
 

 
 I added a release note for this ticket even though it's marked No Release Note Needed after consulting with Kate Lopresti.  
 

  
 
 
 
 

 
 
 

 
 
 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.307108.1556820038000.47722.1565228580371%40Atlassian.JIRA.


Jira (BOLT-1286) Document YAML plan constructs that can't be converted

2019-08-07 Thread Chris Cowell (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Chris Cowell updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1286  
 
 
  Document YAML plan constructs that can't be converted   
 

  
 
 
 
 

 
Change By: 
 Chris Cowell  
 
 
Labels: 
 docs_reviewed  
 

  
 
 
 
 

 
 
 

 
 
 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.307108.1556820038000.47726.1565228580390%40Atlassian.JIRA.


Jira (PUP-9942) no_proxy environment variable does not work

2019-08-07 Thread Kris Bosland (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kris Bosland commented on  PUP-9942  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: no_proxy environment variable does not work   
 

  
 
 
 
 

 
 Merged to master at 44cf745.  
 

  
 
 
 
 

 
 
 

 
 
 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.320046.1565215526000.47707.1565224560115%40Atlassian.JIRA.


Jira (PUP-2172) Add exceptions to http_proxy_{port,host}

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


 
 
 
 

 
 
 

 
   
 Josh Cooper updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-2172  
 
 
  Add exceptions to http_proxy_{port,host}   
 

  
 
 
 
 

 
Change By: 
 Josh Cooper  
 
 
Fix Version/s: 
 PUP 6.8.0  
 
 
Fix Version/s: 
 PUP 6.4.4  
 
 
Fix Version/s: 
 PUP 6.0.11  
 
 
Fix Version/s: 
 PUP 5.5.17  
 

  
 
 
 
 

 
 
 

 
 
 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 

Jira (PUP-2172) Add exceptions to http_proxy_{port,host}

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


 
 
 
 

 
 
 

 
   
 Josh Cooper commented on  PUP-2172  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Add exceptions to http_proxy_{port,host}   
 

  
 
 
 
 

 
 Tickets PUP-9942 and PUP-9316 allow a proxy exception list to be specified via NO_PROXY environment variable or Puppet[:no_proxy] puppet setting respectively, which I think addresses most of the concerns in this ticket. Ticket PUP-8027 covers the gem provider issue. The remaining issue is whether puppet should not use a proxy for some hosts by default. Skipping localhost is easy enough, but I don't think we should skip hosts in the same domain by default. That could be a breaking change for some, and be highly dependent on the network environment. For this ticket, I'm thinking we should just skip localhost by default.  
 

  
 
 
 
 

 
 
 

 
 
 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.31144.1396893516000.47687.1565223960305%40Atlassian.JIRA.


Jira (PUP-2172) Add exceptions to http_proxy_{port,host}

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


 
 
 
 

 
 
 

 
   
 Josh Cooper assigned an issue to Josh Cooper  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-2172  
 
 
  Add exceptions to http_proxy_{port,host}   
 

  
 
 
 
 

 
Change By: 
 Josh Cooper  
 
 
Assignee: 
 Josh Cooper  
 

  
 
 
 
 

 
 
 

 
 
 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.31144.1396893516000.47664.1565222402721%40Atlassian.JIRA.


Jira (PUP-8246) Consolidate http client connection implementations

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


 
 
 
 

 
 
 

 
   
 Josh Cooper updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8246  
 
 
  Consolidate http client connection implementations   
 

  
 
 
 
 

 
Change By: 
 Josh Cooper  
 
 
Sprint: 
 Platform Core 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.226489.1513193082000.47654.1565222401986%40Atlassian.JIRA.


Jira (PUP-2172) Add exceptions to http_proxy_{port,host}

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


 
 
 
 

 
 
 

 
   
 Josh Cooper updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-2172  
 
 
  Add exceptions to http_proxy_{port,host}   
 

  
 
 
 
 

 
Change By: 
 Josh Cooper  
 
 
Sprint: 
 Platform Core 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.31144.1396893516000.47649.1565222340705%40Atlassian.JIRA.


Jira (PUP-8246) Consolidate http client connection implementations

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


 
 
 
 

 
 
 

 
   
 Josh Cooper updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8246  
 
 
  Consolidate http client connection implementations   
 

  
 
 
 
 

 
Change By: 
 Josh Cooper  
 
 
Sprint: 
 Platform Core 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.226489.1513193082000.47639.1565222340653%40Atlassian.JIRA.


Jira (PUP-9316) implement no_proxy in puppet.conf

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


 
 
 
 

 
 
 

 
   
 Josh Cooper updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9316  
 
 
  implement no_proxy in puppet.conf   
 

  
 
 
 
 

 
Change By: 
 Josh Cooper  
 
 
Sprint: 
 Platform Core 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.285347.1542320475000.47634.1565221680396%40Atlassian.JIRA.


Jira (PUP-9316) implement no_proxy in puppet.conf

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


 
 
 
 

 
 
 

 
   
 Josh Cooper updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9316  
 
 
  implement no_proxy in puppet.conf   
 

  
 
 
 
 

 
Change By: 
 Josh Cooper  
 
 
Release Notes Summary: 
 Allows `no_proxy` to be specified as a puppet setting which is consistent with other http_proxy_* puppet settings. The NO_PROXY environment variable takes precedence over the no_proxy puppet setting.  
 
 
Release Notes: 
 Enhancement  
 

  
 
 
 
 

 
 
 

 
 
 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.285347.1542320475000.47632.1565221680388%40Atlassian.JIRA.


Jira (PUP-9316) implement no_proxy in puppet.conf

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


 
 
 
 

 
 
 

 
   
 Josh Cooper updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9316  
 
 
  implement no_proxy in puppet.conf   
 

  
 
 
 
 

 
Change By: 
 Josh Cooper  
 
 
Fix Version/s: 
 PUP 6.8.0  
 
 
Fix Version/s: 
 PUP 6.4.4  
 
 
Fix Version/s: 
 PUP 6.0.11  
 
 
Fix Version/s: 
 PUP 5.5.17  
 

  
 
 
 
 

 
 
 

 
 
 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 

Jira (PUP-9316) implement no_proxy in puppet.conf

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


 
 
 
 

 
 
 

 
   
 Josh Cooper assigned an issue to Josh Cooper  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9316  
 
 
  implement no_proxy in puppet.conf   
 

  
 
 
 
 

 
Change By: 
 Josh Cooper  
 
 
Assignee: 
 Josh Cooper  
 

  
 
 
 
 

 
 
 

 
 
 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.285347.1542320475000.47627.1565221560811%40Atlassian.JIRA.


Jira (PUP-9942) no_proxy environment variable does not work

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


 
 
 
 

 
 
 

 
   
 Josh Cooper updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9942  
 
 
  no_proxy environment variable does not work   
 

  
 
 
 
 

 
Change By: 
 Josh Cooper  
 
 
Fix Version/s: 
 PUP 6.8.0  
 
 
Fix Version/s: 
 PUP 6.4.4  
 
 
Fix Version/s: 
 PUP 6.0.11  
 

  
 
 
 
 

 
 
 

 
 
 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.320046.1565215526000.47605.1565220480148%40Atlassian.JIRA.


Jira (PUP-9942) no_proxy environment variable does not work

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


 
 
 
 

 
 
 

 
   
 Josh Cooper updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9942  
 
 
  no_proxy environment variable does not work   
 

  
 
 
 
 

 
Change By: 
 Josh Cooper  
 
 
Release Notes Summary: 
 If the agent is configured to use an HTTP proxy and it attempts to connect to a host that matches an entry in the "NO_PROXY" environment variable, then puppet will not use the proxy, and instead connect directly to the host. This feature was originally introduced in PUP-4030, but it didn't work.  
 

  
 
 
 
 

 
 
 

 
 
 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.320046.1565215526000.47603.1565220420138%40Atlassian.JIRA.


Jira (PUP-9942) no_proxy environment variable does not work

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


 
 
 
 

 
 
 

 
   
 Josh Cooper updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9942  
 
 
  no_proxy environment variable does not work   
 

  
 
 
 
 

 
Change By: 
 Josh Cooper  
 
 
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.320046.1565215526000.47604.1565220420161%40Atlassian.JIRA.


Jira (PUP-9942) no_proxy environment variable does not work

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


 
 
 
 

 
 
 

 
   
 Josh Cooper updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9942  
 
 
  no_proxy environment variable does not work   
 

  
 
 
 
 

 
Change By: 
 Josh Cooper  
 
 
Fix Version/s: 
 PUP 5.5.17  
 

  
 
 
 
 

 
 
 

 
 
 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.320046.1565215526000.47600.1565220300127%40Atlassian.JIRA.


Jira (BOLT-1505) Broken link in Bolt Hands-on workshop

2019-08-07 Thread Tom Beech (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Tom Beech assigned an issue to Tom Beech  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1505  
 
 
  Broken link in Bolt Hands-on workshop   
 

  
 
 
 
 

 
Change By: 
 Tom Beech  
 
 
Assignee: 
 Tom Beech  
 

  
 
 
 
 

 
 
 

 
 
 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.320032.1565206569000.47599.1565220180335%40Atlassian.JIRA.


Jira (BOLT-1505) Broken link in Bolt Hands-on workshop

2019-08-07 Thread Tom Beech (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Tom Beech updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1505  
 
 
  Broken link in Bolt Hands-on workshop   
 

  
 
 
 
 

 
Change By: 
 Tom Beech  
 
 
Sprint: 
 Bolt 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.320032.1565206569000.47596.1565220180320%40Atlassian.JIRA.


Jira (BOLT-1424) Vault plugin

2019-08-07 Thread Tom Beech (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Tom Beech updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1424  
 
 
  Vault plugin   
 

  
 
 
 
 

 
Change By: 
 Tom Beech  
 
 
Fix Version/s: 
 BOLT Next  
 

  
 
 
 
 

 
 
 

 
 
 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.313814.1561405465000.47573.1565219160399%40Atlassian.JIRA.


Jira (BOLT-1487) Make it easier for users to know and turn off analytics at install time

2019-08-07 Thread Tom Beech (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Tom Beech updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1487  
 
 
  Make it easier for users to know and turn off analytics at install time   
 

  
 
 
 
 

 
Change By: 
 Tom Beech  
 
 
Sprint: 
 Bolt  Ready for Grooming  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.318117.1564082501000.47564.1565218920298%40Atlassian.JIRA.


Jira (BOLT-1487) Make it easier for users to know and turn off analytics at install time

2019-08-07 Thread Tom Beech (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Tom Beech updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1487  
 
 
  Make it easier for users to know and turn off analytics at install time   
 

  
 
 
 
 

 
Change By: 
 Tom Beech  
 
 
Sprint: 
 Bolt Ready for Grooming  
 

  
 
 
 
 

 
 
 

 
 
 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.318117.1564082501000.47559.1565218860306%40Atlassian.JIRA.


Jira (BOLT-1487) Make it easier for users to know and turn off analytics at install time

2019-08-07 Thread Tom Beech (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Tom Beech updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1487  
 
 
  Make it easier for users to know and turn off analytics at install time   
 

  
 
 
 
 

 
Change By: 
 Tom Beech  
 
 
Sprint: 
 Bolt 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.318117.1564082501000.47557.1565218860275%40Atlassian.JIRA.


Jira (BOLT-1487) Make it easier for users to know and turn off analytics at install time

2019-08-07 Thread Tom Beech (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Tom Beech updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1487  
 
 
  Make it easier for users to know and turn off analytics at install time   
 

  
 
 
 
 

 
Change By: 
 Tom Beech  
 
 
Sprint: 
 Bolt 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.318117.1564082501000.47548.1565218500138%40Atlassian.JIRA.


Jira (BOLT-1511) Update homebrew-puppet (Bolt 1.28.0)

2019-08-07 Thread Cas Donoghue (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Cas Donoghue created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1511  
 
 
  Update homebrew-puppet (Bolt 1.28.0)   
 

  
 
 
 
 

 
Issue Type: 
  Sub-task  
 
 
Assignee: 
 Cas Donoghue  
 
 
Created: 
 2019/08/07 3:52 PM  
 
 
Due Date: 
2019/08/08 
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Cas Donoghue  
 

  
 
 
 
 

 
 (Initial planned release date: 2019-08-08) Until we automate this, you'll also need to update the version and SHA hashes of homebrew-puppet. To do this please 
 
Create a fork of the homebrew-puppet repo 
Create a new branch on that fork 
Run "rake 'brew:cask[puppet-bolt]'" 
Verify Casks/puppet-bolt.rb was updated to the correct version 
Put up a PR to homebrew-puppet and request review 
  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

 

Jira (BOLT-1513) Send release announcements (Bolt 1.28.0)

2019-08-07 Thread Cas Donoghue (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Cas Donoghue created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1513  
 
 
  Send release announcements (Bolt 1.28.0)   
 

  
 
 
 
 

 
Issue Type: 
  Sub-task  
 
 
Assignee: 
 Chris Cowell  
 
 
Created: 
 2019/08/07 3:52 PM  
 
 
Due Date: 
2019/08/08 
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Cas Donoghue  
 

  
 
 
 
 

 
 (Initial planned release date: 2019-08-08) When docs have finished building (check that all links resolve appropriately) - 
 
Create an e-mail announcement with the subject "Bolt  now available". 
 
In the From: field, enter the Google account Puppet Product Updates (puppet-product-upda...@puppet.com). 
In the Bcc: field, enter the following addresses: internal-puppet-product-upda...@puppet.com, puppet-us...@googlegroups.com, puppet-...@googlegroups.com, puppet-annou...@googlegroups.com 
In the body, include a summary of the release and links to the release notes and installation instructions. 
  
If this release has security implications, also send to puppet-security-annou...@googlegroups.com. 
 (Optional) Set up a canned response in Gmail so that you don't have to recreate this email every time: Subject: Bolt X.Y.Z now available Body: Greetings! We're happy to announce the release of Bolt X.Y.Z. Highlights in this release include: 
 
Gerund phrase 
Gerund phrase For more information, check out 

Jira (BOLT-1510) Update the release spreadsheet (Bolt 1.28.0)

2019-08-07 Thread Cas Donoghue (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Cas Donoghue created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1510  
 
 
  Update the release spreadsheet (Bolt 1.28.0)   
 

  
 
 
 
 

 
Issue Type: 
  Sub-task  
 
 
Assignee: 
 Cas Donoghue  
 
 
Created: 
 2019/08/07 3:52 PM  
 
 
Due Date: 
2019/08/08 
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Cas Donoghue  
 

  
 
 
 
 

 
 (Initial planned release date: 2019-08-08) Update the release google spreadsheet for Bolt 1.28.0.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

Jira (BOLT-1512) Docs for bolt release (Bolt 1.28.0)

2019-08-07 Thread Cas Donoghue (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Cas Donoghue created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1512  
 
 
  Docs for bolt release (Bolt 1.28.0)   
 

  
 
 
 
 

 
Issue Type: 
  Sub-task  
 
 
Assignee: 
 Chris Cowell  
 
 
Created: 
 2019/08/07 3:52 PM  
 
 
Due Date: 
2019/08/08 
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Cas Donoghue  
 

  
 
 
 
 

 
 (Initial planned release date: 2019-08-08) Release notes and docs changes for bolt 1.28.0  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

Jira (BOLT-1509) Publish release artifacts (Bolt 1.28.0)

2019-08-07 Thread Cas Donoghue (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Cas Donoghue created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1509  
 
 
  Publish release artifacts (Bolt 1.28.0)   
 

  
 
 
 
 

 
Issue Type: 
  Sub-task  
 
 
Assignee: 
 Cas Donoghue  
 
 
Created: 
 2019/08/07 3:51 PM  
 
 
Due Date: 
2019/08/08 
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Cas Donoghue  
 

  
 
 
 
 

 
 (Initial planned release date: 2019-08-08) Run the Bolt shipping pipeline. Set REF to 1.28.0. If you encounter any issues, ping the on-call person in the #release-new-new Slack channel.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA 

Jira (BOLT-1508) Kick off release pipeline (Bolt 1.28.0)

2019-08-07 Thread Cas Donoghue (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Cas Donoghue created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1508  
 
 
  Kick off release pipeline (Bolt 1.28.0)   
 

  
 
 
 
 

 
Issue Type: 
  Sub-task  
 
 
Assignee: 
 Cas Donoghue  
 
 
Created: 
 2019/08/07 3:51 PM  
 
 
Due Date: 
2019/08/08 
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Cas Donoghue  
 

  
 
 
 
 

 
 (Initial planned release date: 2019-08-08) With our automated builds pipeline 
 
Ensure the sha at the tip of the master branch of bolt has been promoted to bolt-vanagon 
Based on that sha ensure both the component pipeline and bolt-vanagon packaging pipeline have completed successfully 
bolt packages are staged on puppet-bolt based on sha from bolt vanagon 
Go to the release pipeline 
Click "Build with Parameters" 
Check the PUBLIC checkbox 
Enter the version in the NEW_TAG box (x.y.z format) 
Click build! 
 And make sure the pipeline is green!  
 

  
 
 
 
 

 
 
 


Jira (BOLT-1506) Bolt 1.28.0 2019-08-08 Release

2019-08-07 Thread Cas Donoghue (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Cas Donoghue created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1506  
 
 
  Bolt 1.28.0 2019-08-08 Release   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Cas Donoghue  
 
 
Created: 
 2019/08/07 3:51 PM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Cas Donoghue  
 

  
 
 
 
 

 
 Bolt 1.28.0 2019-08-08 Release  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  

Jira (BOLT-1507) Reconcile git commits, JIRA tickets, and versions (Bolt 1.28.0)

2019-08-07 Thread Cas Donoghue (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Cas Donoghue created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1507  
 
 
  Reconcile git commits, JIRA tickets, and versions (Bolt 1.28.0)   
 

  
 
 
 
 

 
Issue Type: 
  Sub-task  
 
 
Assignee: 
 Cas Donoghue  
 
 
Created: 
 2019/08/07 3:51 PM  
 
 
Due Date: 
2019/08/08 
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Cas Donoghue  
 

  
 
 
 
 

 
 (Initial planned release date: 2019-08-08) 
 
Ensure all tickets referenced in the commit log have been targeted at the release. 
Ensure all tickets targeted at the release have a corresponding commit. 
You can do this manually by inspecting the git log and comparing against 'Project=Bolt and fixVersion="Bolt x.y.z"' in JIRA. 
Ensure all tickets have release notes. 
Ensure all tickets have been resolved. 
In JIRA releases, change 'BOLT Next' to 'BOLT x.y.z' with the release date. Create a new 'BOLT Next'. 
  
 

  
 
 
 
 

 
 
 

 
 
   

Jira (BOLT-1487) Make it easier for users to know and turn off analytics at install time

2019-08-07 Thread Alex Dreyer (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Dreyer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1487  
 
 
  Make it easier for users to know and turn off analytics at install time   
 

  
 
 
 
 

 
Change By: 
 Alex Dreyer  
 
 
Release Notes Summary: 
 Print a warning for new users before sending any analytics.  
 
 
Release Notes: 
 New Feature  
 

  
 
 
 
 

 
 
 

 
 
 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.318117.1564082501000.47524.1565218320948%40Atlassian.JIRA.


Jira (BOLT-1487) Make it easier for users to know and turn off analytics at install time

2019-08-07 Thread Alex Dreyer (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Dreyer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1487  
 
 
  Make it easier for users to know and turn off analytics at install time   
 

  
 
 
 
 

 
Change By: 
 Alex Dreyer  
 
 
Fix Version/s: 
 BOLT Next  
 

  
 
 
 
 

 
 
 

 
 
 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.318117.1564082501000.47522.1565218260149%40Atlassian.JIRA.


Jira (PUP-9942) no_proxy environment variable does not work

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


 
 
 
 

 
 
 

 
   
 Josh Cooper updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9942  
 
 
  no_proxy environment variable does not work   
 

  
 
 
 
 

 
Change By: 
 Josh Cooper  
 

  
 
 
 
 

 
 Commit 90560edf0f43f5382bd539646988f7a96ea3809e for PUP-4030 added the ability to skip an http proxy if the host and port matched an entry in the {{NO_PROXY}} environment variable. However it didn't actually work because our connection factory passed the {{Site}} object instead of a String or URI.  To reproduce specify an unused http proxy port and try to not use a proxy for the puppet server:  {noformat}$ env NO_PROXY=$(bundle exec puppet config print server --section main) bundle exec puppet agent -t --http_proxy_host localhost --http_proxy_port 12345Warning: Unable to fetch my node definition, but the agent run will continue:Warning: Failed to open TCP connection to localhost:12345 (Connection refused - connect(2) for "localhost" port 12345)Info: Retrieving pluginfactsError: /File[/Users/josh/.puppetlabs/opt/puppet/cache/facts.d]: Failed to generate additional resources using 'eval_generate': Failed to open TCP connection to localhost:12345 (Connection refused - connect(2) for "localhost" port 12345)Error: /File[/Users/josh/.puppetlabs/opt/puppet/cache/facts.d]: Could not evaluate: Could not retrieve file metadata for puppet:///pluginfacts: Failed to open TCP connection to localhost:12345 (Connection refused - connect(2) for "localhost" port 12345)...{noformat}    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

Jira (PUP-9942) no_proxy environment variable does not work

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


 
 
 
 

 
 
 

 
   
 Josh Cooper updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9942  
 
 
  no_proxy environment variable does not work   
 

  
 
 
 
 

 
Change By: 
 Josh Cooper  
 

  
 
 
 
 

 
 Commit 90560edf0f43f5382bd539646988f7a96ea3809e for PUP- 4020 4030  added the ability to skip an http proxy if the host and port matched an entry in the {{NO_PROXY}} environment variable. However it didn't actually work because our connection factory passed the {{Site}} object instead of a String or URI.   
 

  
 
 
 
 

 
 
 

 
 
 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.320046.1565215526000.47483.1565215620080%40Atlassian.JIRA.


Jira (PUP-9942) no_proxy environment variable does not work

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


 
 
 
 

 
 
 

 
   
 Josh Cooper assigned an issue to Josh Cooper  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9942  
 
 
  no_proxy environment variable does not work   
 

  
 
 
 
 

 
Change By: 
 Josh Cooper  
 
 
Assignee: 
 Josh Cooper  
 

  
 
 
 
 

 
 
 

 
 
 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.320046.1565215526000.47482.1565215560459%40Atlassian.JIRA.


Jira (PUP-9942) no_proxy environment variable does not work

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


 
 
 
 

 
 
 

 
   
 Josh Cooper created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9942  
 
 
  no_proxy environment variable does not work   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2019/08/07 3:05 PM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Josh Cooper  
 

  
 
 
 
 

 
 Commit 90560edf0f43f5382bd539646988f7a96ea3809e for PUP-4020 added the ability to skip an http proxy if the host and port matched an entry in the NO_PROXY environment variable. However it didn't actually work because our connection factory passed the Site object instead of a String or URI.    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

Jira (PUP-9942) no_proxy environment variable does not work

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


 
 
 
 

 
 
 

 
   
 Josh Cooper updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9942  
 
 
  no_proxy environment variable does not work   
 

  
 
 
 
 

 
Change By: 
 Josh Cooper  
 
 
Sprint: 
 Platform Core 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.320046.1565215526000.47481.1565215560455%40Atlassian.JIRA.


Jira (BOLT-1424) Vault plugin

2019-08-07 Thread Tom Beech (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Tom Beech updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1424  
 
 
  Vault plugin   
 

  
 
 
 
 

 
Change By: 
 Tom Beech  
 
 
Release Notes Summary: 
 Adds support for populating inventory configuration fields by looking up secrets from a Vault KV engine.  
 
 
Release Notes: 
 New Feature  
 

  
 
 
 
 

 
 
 

 
 
 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.313814.1561405465000.47431.1565214240413%40Atlassian.JIRA.


Jira (BOLT-1502) Do not rely on wrapper script for run-as with stdin task input

2019-08-07 Thread Nick Lewis (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nick Lewis commented on  BOLT-1502  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Do not rely on wrapper script for run-as with stdin task input   
 

  
 
 
 
 

 
 We need to introduce a slightly more complex state machine to the SSH transport. We should now hold off on submitting stdin until we see a marker message indicating the command has started executing. We should string the command together with an echo of a randomly generated message, and our on_data handler should check for that message and then submit stdin. It should track some state indicating it's sent stdin, to prevent it from being sent multiple times. So in the case where you're using sudo with a password, the on_data handler will first notice the password prompt and send the password, then once sudo has successfully escalated, it will run the echo, and then the on_data will see the message indicating it's time to send stdin. We can either vary this behavior based on whether you're using sudo or we can always include the echo, depending on which seems more sensible in the actual implementation.  
 

  
 
 
 
 

 
 
 

 
 
 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.319291.1564682997000.47396.1565213100105%40Atlassian.JIRA.


Jira (BOLT-1505) Broken link in Bolt Hands-on workshop

2019-08-07 Thread Paul Anderson (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Paul Anderson created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1505  
 
 
  Broken link in Bolt Hands-on workshop   
 

  
 
 
 
 

 
Issue Type: 
  Story  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2019/08/07 12:36 PM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Paul Anderson  
 

  
 
 
 
 

 
 Proceeding through the Hands-on workshop, one reaches this page: https://puppetlabs.github.io/bolt/lab/04-running-scripts/ Unfortunately, the link to the bash script points to a non-existant URL:   curl -O https://puppetlabs.github.io/bolt/lessons/lesson1-10/src/bashcheck.sh And so one downloads a 404 HTML page without realizing there is an error. The rest of the exercise goes downhill quickly... $ curl -O https://puppetlabs.github.io/bolt/lessons/lesson1-10/src/bashcheck.sh % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 9339 100 9339 0 0 200k 0 -::- -::- -::- 202k $ bolt script run bashcheck.sh -n  Started on node2... Started on node3... Started on node1... Failed on node3: The command failed with exit code 2 STDERR: /tmp/aca9c3cb-84ab-4c84-ab89-d5453348913b/bashcheck.sh: line 1: syntax error near unexpected token `newline' /tmp/aca9c3cb-84ab-4c84-ab89-d5453348913b/bashcheck.sh: line 1: `' Failed on node1: The command failed with exit code 2 STDERR: /tmp/adb88758-9f69-460b-978c-10438798e4ff/bashcheck.sh: line 1: syntax error near unexpected token `newline' /tmp/adb88758-9f69-460b-978c-10438798e4ff/bashcheck.sh: line 1: `' Failed on node2: The command failed with exit code 2 STDERR: /tmp/0a0556a2-6b34-401c-8f8a-6f3be4775d3a/bashcheck.sh: line 1: syntax error near unexpected token `newline' /tmp/0a0556a2-6b34-401c-8f8a-6f3be4775d3a/bashcheck.sh: line 1: `' Failed on 3 nodes: node1, node2, node3 Ran on 3 nodes in 3.42 seconds $ {{}} {{}}  
 

  
 
 
 
 

 
 
 

Jira (BOLT-1504) Update gems and modules shipped with bolt

2019-08-07 Thread Chris Cowell (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Chris Cowell updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1504  
 
 
  Update gems and modules shipped with bolt
 

  
 
 
 
 

 
Change By: 
 Chris Cowell  
 
 
Labels: 
 docs_reviewed  
 

  
 
 
 
 

 
 
 

 
 
 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.319673.1565031563000.47113.1565201640817%40Atlassian.JIRA.


Jira (BOLT-1451) Automatically call apply_prep before `resources` step in YAML plans

2019-08-07 Thread Cas Donoghue (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Cas Donoghue updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1451  
 
 
  Automatically call apply_prep before `resources` step in YAML plans   
 

  
 
 
 
 

 
Change By: 
 Cas Donoghue  
 
 
Release Notes Summary: 
 When using a {{resources}} step in a Yaml plan, {{apply_prep}} is automatically performed on the targets for that step.   
 

  
 
 
 
 

 
 
 

 
 
 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.315003.1562084948000.47064.1565200620123%40Atlassian.JIRA.


Jira (BOLT-1423) Bolt actions hang over ssh transport when ProxyCommand is set in openssh config

2019-08-07 Thread Cas Donoghue (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Cas Donoghue updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1423  
 
 
  Bolt actions hang over ssh transport when ProxyCommand is set in openssh config   
 

  
 
 
 
 

 
Change By: 
 Cas Donoghue  
 
 
Release Notes Summary: 
 A new {{disconnect-timeout}} configuration option has been added to the ssh transport to ensure ssh connections are terminated.  
 

  
 
 
 
 

 
 
 

 
 
 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.313738.1561387259000.47060.1565200500113%40Atlassian.JIRA.


Jira (BOLT-1422) Update command reference docs

2019-08-07 Thread Cas Donoghue (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Cas Donoghue updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1422  
 
 
  Update command reference docs   
 

  
 
 
 
 

 
Change By: 
 Cas Donoghue  
 
 
Release Notes: 
 Not Needed  
 

  
 
 
 
 

 
 
 

 
 
 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.313638.1561140371000.47058.1565200440202%40Atlassian.JIRA.


Jira (PUP-5109) Puppet::Resource::Catalog::Compiler#set_server_facts always produces a warning on ipv6 only systems

2019-08-07 Thread Kris Bosland (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kris Bosland commented on  PUP-5109  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Puppet::Resource::Catalog::Compiler#set_server_facts always produces a warning on ipv6 only systems   
 

  
 
 
 
 

 
 Igor Galić, we have a PR up to fix this issue, but it has raised some questions.  How is the serverip fact used?  If it is used to compose URLs, then the user will now need to add logic to handle the IPv4 vs IPv6 case.  For more detail, see the PR: https://github.com/puppetlabs/puppet/pull/7656. Thanks for any insight on this.  
 

  
 
 
 
 

 
 
 

 
 
 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.95553.144084808.47033.1565199960365%40Atlassian.JIRA.


Jira (BOLT-1468) implement wait_until_available in bolt-server

2019-08-07 Thread Scott McClellan (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Scott McClellan assigned an issue to Scott McClellan  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1468  
 
 
  implement wait_until_available in bolt-server   
 

  
 
 
 
 

 
Change By: 
 Scott McClellan  
 
 
Assignee: 
 Scott McClellan  
 

  
 
 
 
 

 
 
 

 
 
 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.315953.1562789343000.46887.1565197800890%40Atlassian.JIRA.


Jira (PUP-9941) Update jackson-databind in pcore-java

2019-08-07 Thread Eric Griswold (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Griswold created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9941  
 
 
  Update jackson-databind in pcore-java   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2019/08/07 9:43 AM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Eric Griswold  
 

  
 
 
 
 

 
 A moderate vulnerability was found in the version of jackson-databind in pcore-java. pom.xml update suggested: com.fasterxml.jackson.core:jackson-databind ~> 2.9.9.2  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

Jira (BOLT-1502) Do not rely on wrapper script for run-as with stdin task input

2019-08-07 Thread Cas Donoghue (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Cas Donoghue assigned an issue to Cas Donoghue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1502  
 
 
  Do not rely on wrapper script for run-as with stdin task input   
 

  
 
 
 
 

 
Change By: 
 Cas Donoghue  
 
 
Assignee: 
 Cas Donoghue  
 

  
 
 
 
 

 
 
 

 
 
 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.319291.1564682997000.46500.1565188680072%40Atlassian.JIRA.


Jira (PUP-9939) Update the PQL Queries with clients own examples.

2019-08-07 Thread Patrick Grant (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Patrick Grant updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9939  
 
 
  Update the PQL Queries with clients own examples.   
 

  
 
 
 
 

 
Change By: 
 Patrick Grant  
 
 
CS Priority: 
 Needs Priority  
 

  
 
 
 
 

 
 
 

 
 
 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.319938.1565184419000.46445.1565185020145%40Atlassian.JIRA.


Jira (PUP-9938) Puppet Agent is not a protected service.

2019-08-07 Thread Patrick Grant (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Patrick Grant updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9938  
 
 
  Puppet Agent is not a protected service.   
 

  
 
 
 
 

 
Change By: 
 Patrick Grant  
 
 
CS Priority: 
 Needs Priority  
 

  
 
 
 
 

 
 
 

 
 
 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.319937.1565183931000.46442.1565184600171%40Atlassian.JIRA.


Jira (PUP-9939) Update the PQL Queries with clients own examples.

2019-08-07 Thread Rob Denny (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Rob Denny created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9939  
 
 
  Update the PQL Queries with clients own examples.   
 

  
 
 
 
 

 
Issue Type: 
  New Feature  
 
 
Affects Versions: 
 PUP 5.5.1  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 Language  
 
 
Created: 
 2019/08/07 6:26 AM  
 
 
Fix Versions: 
 PUP 6.7.2  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Rob Denny  
 

  
 
 
 
 

 
 It is not possible to update the PQL examples in the Puppet Enterprise Console, this makes sharing PQL examples a little more difficult to share knowledge and regularly used expressions specific to our organisation.  Would it be possible to allow the Puppet Enterprise Console to pull from a "custom" directory on the Puppet Master, so we can upload "canned responses and PQL examples"?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 
   

Jira (PUP-9938) Puppet Agent is not a protected service.

2019-08-07 Thread Rob Denny (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Rob Denny created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9938  
 
 
  Puppet Agent is not a protected service.   
 

  
 
 
 
 

 
Issue Type: 
  New Feature  
 
 
Affects Versions: 
 PUP 5.5.1  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 Windows  
 
 
Created: 
 2019/08/07 6:18 AM  
 
 
Environment: 
 All Microsoft OS's (Windows 8.1 upwards, Server 2012 upwards)  
 
 
Fix Versions: 
 PUP 6.7.2  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Rob Denny  
 

  
 
 
 
 

 
 following on from Puppet Support Call 35676, it would be beneficial to get the Puppet Agent to be a protected server/executable.    Puppet is a Desired State Configuration tool, however, you can easily stop this by "killing" the process in windows, which you dont need to be an administrator to do. Would it be possible to protect the EXE/service so it can't be stopped like an Antivirus service, so a savvy computer user could disable to the puppet agent.   
 

  
 
 
 
 

 
 
 

   

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

2019-08-07 Thread Tim Meusel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Tim Meusel commented on  FACT-1967  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unable to compile libwhereami 0.2.2 on latest Archlinux   
 

  
 
 
 
 

 
 Hi. Thanks for the hint. I'm now using those commands (base directory is the extracted release from github.com):  
 
 
 
 
 mkdir build-release  
 
 
 cd build-release  
 
 
 cmake .. -DENABLE_CXX_WERROR=OFF -DCMAKE_INSTALL_PREFIX:PATH=/usr  
 
 
 make libwhereami_test  
 
 
 make  
 
 
 make install
  
 
 
 
  This looks good in a clean container environment. This is used as a base to create a package for Archlinux  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by 

Jira (FACT-1968) Unable to compile facter 3.14.2 on latest Archlinux

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


 
 
 
 

 
 
 

 
   
 Gabriel Nagy assigned an issue to Gabriel Nagy  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-1968  
 
 
  Unable to compile facter 3.14.2 on latest Archlinux   
 

  
 
 
 
 

 
Change By: 
 Gabriel Nagy  
 
 
Assignee: 
 Gabriel Nagy  
 

  
 
 
 
 

 
 
 

 
 
 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.318296.1564333964000.46354.1565179440399%40Atlassian.JIRA.


Jira (FACT-1968) Unable to compile facter 3.14.2 on latest Archlinux

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


 
 
 
 

 
 
 

 
   
 Gabriel Nagy commented on  FACT-1968  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unable to compile facter 3.14.2 on latest Archlinux   
 

  
 
 
 
 

 
 Hi Tim Meusel, You can build this by following the steps from the PKGBUILD (from prepare() and build()): https://git.archlinux.org/svntogit/community.git/tree/trunk/PKGBUILD?h=packages/facter Let me know if this works for 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.318296.1564333964000.46345.1565179260245%40Atlassian.JIRA.


Jira (PDB-3743) ensure PDB 4.4.x can be run with puppetserver 5.x

2019-08-07 Thread john (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 john commented on  PDB-3743  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: ensure PDB 4.4.x can be run with puppetserver 5.x   
 

  
 
 
 
 

 
 Late to the party but same issue ii puppet 5.5.10-4 all configuration management system ii puppet-master 5.5.10-4 all configuration management system, master service ii puppet-master-passenger 5.5.10-4 all configuration management system, scalable master service ii puppet-terminus-puppetdb 6.2.0-3 all Puppet data warehouse ii puppetdb 4.4.0-1 all Puppet Labs puppetdb   Reading the related issues seems the advice from the developers are just upgrade everything all at once   
 

  
 
 
 
 

 
 
 

 
 
 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.220054.1509640239000.46281.1565173981295%40Atlassian.JIRA.


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

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


 
 
 
 

 
 
 

 
   
 Gabriel Nagy commented on  FACT-1967  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unable to compile libwhereami 0.2.2 on latest Archlinux   
 

  
 
 
 
 

 
 Hi Tim Meusel, Those are just some new warnings that came with GCC 8.0. You can bypass them by passing the ENABLE_CXX_WERROR=OFF parameter to CMake, like this: cmake .. -DENABLE_CXX_WERROR=OFF. I'll fix the warnings in libwhereami, but in the meantime you can get it compiled by using that parameter.  
 

  
 
 
 
 

 
 
 

 
 
 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.46225.1565172420314%40Atlassian.JIRA.


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

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


 
 
 
 

 
 
 

 
   
 Gabriel Nagy assigned an issue to Gabriel Nagy  
 

  
 
 
 
 

 
 
  
 
 
 
 

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

  
 
 
 
 

 
Change By: 
 Gabriel Nagy  
 
 
Assignee: 
 Gabriel Nagy  
 

  
 
 
 
 

 
 
 

 
 
 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.46219.1565171880245%40Atlassian.JIRA.


Jira (FACT-1978) Facter 2.5.5 fails to detect Amazon Linux 2 (AMI amzn2-ami-hvm-2.0.20190618-x86_64-gp2)

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


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-1978  
 
 
  Facter 2.5.5 fails to detect Amazon Linux 2 (AMI amzn2-ami-hvm-2.0.20190618-x86_64-gp2)   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Story Points: 
 2  
 

  
 
 
 
 

 
 
 

 
 
 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.318955.1564566972000.46175.1565170500340%40Atlassian.JIRA.


Jira (FACT-1978) Facter 2.5.5 fails to detect Amazon Linux 2 (AMI amzn2-ami-hvm-2.0.20190618-x86_64-gp2)

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


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-1978  
 
 
  Facter 2.5.5 fails to detect Amazon Linux 2 (AMI amzn2-ami-hvm-2.0.20190618-x86_64-gp2)   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Sprint: 
 PR NW  -  Triage  2019-08-21  
 

  
 
 
 
 

 
 
 

 
 
 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.318955.1564566972000.46177.1565170500348%40Atlassian.JIRA.


Jira (FACT-1968) Unable to compile facter 3.14.2 on latest Archlinux

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


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-1968  
 
 
  Unable to compile facter 3.14.2 on latest Archlinux   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Sprint: 
 PR NW  -  Triage  2019-08-21  
 

  
 
 
 
 

 
 
 

 
 
 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.318296.1564333964000.46168.1565170380385%40Atlassian.JIRA.


Jira (FACT-1968) Unable to compile facter 3.14.2 on latest Archlinux

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


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-1968  
 
 
  Unable to compile facter 3.14.2 on latest Archlinux   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Story Points: 
 2  
 

  
 
 
 
 

 
 
 

 
 
 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.318296.1564333964000.46163.1565170380363%40Atlassian.JIRA.


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

2019-08-07 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: 
 PR NW  -  Triage  2019-08-21  
 

  
 
 
 
 

 
 
 

 
 
 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.46155.1565170320432%40Atlassian.JIRA.


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

2019-08-07 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  
 
 
Story Points: 
 2  
 

  
 
 
 
 

 
 
 

 
 
 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.46152.1565170320404%40Atlassian.JIRA.


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

2019-08-07 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  
 
 
Story Points: 
 5  
 

  
 
 
 
 

 
 
 

 
 
 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.46130.1565169060357%40Atlassian.JIRA.


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

2019-08-07 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: 
 PR NW  -  Triage  2019-08-21  
 

  
 
 
 
 

 
 
 

 
 
 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.46134.1565169060376%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-07 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  
 
 
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.125405.1459986358000.46111.1565168461442%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-07 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: 
 PR NW  -  Triage  2019-08-21  
 

  
 
 
 
 

 
 
 

 
 
 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.46126.1565168461522%40Atlassian.JIRA.


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

2019-08-07 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  
 

  
 
 
 
 

 
 
 

 
 
 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.46002.1565167084077%40Atlassian.JIRA.


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

2019-08-07 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  
 

  
 
 
 
 

 
 
 

 
 
 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.46056.1565167084325%40Atlassian.JIRA.


Jira (PUP-9936) Change $deviceconfdir section to agent

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


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9936  
 
 
  Change $deviceconfdir section to agent   
 

  
 
 
 
 

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

  
 
 
 
 

 
 
 

 
 
 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.319404.1564740003000.46070.1565167084398%40Atlassian.JIRA.


Jira (FACT-1935) Facter ipaddress6 on Windows returns link-local address with interface identifier

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


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-1935  
 
 
  Facter ipaddress6 on Windows returns link-local address with interface identifier   
 

  
 
 
 
 

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

  
 
 
 
 

 
 
 

 
 
 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.316045.1562828787000.46060.1565167084350%40Atlassian.JIRA.


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

2019-08-07 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  
 

  
 
 
 
 

 
 
 

 
 
 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.46005.1565167084095%40Atlassian.JIRA.


Jira (FACT-1936) facter -p segfaults with facts that call open-uri.open

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


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-1936  
 
 
  facter -p segfaults with facts that call open-uri.open   
 

  
 
 
 
 

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

  
 
 
 
 

 
 
 

 
 
 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.316163.1562873035000.46066.1565167084380%40Atlassian.JIRA.


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

2019-08-07 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  
 

  
 
 
 
 

 
 
 

 
 
 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.46016.1565167084143%40Atlassian.JIRA.


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

2019-08-07 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  
 

  
 
 
 
 

 
 
 

 
 
 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.46021.1565167084163%40Atlassian.JIRA.


Jira (FACT-1984) Call facter gem and facter c++ as puppet does

2019-08-07 Thread Oana Tanasoiu (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oana Tanasoiu assigned an issue to Oana Tanasoiu  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-1984  
 
 
  Call facter gem and facter c++ as puppet does   
 

  
 
 
 
 

 
Change By: 
 Oana Tanasoiu  
 
 
Assignee: 
 Oana Tanasoiu  
 

  
 
 
 
 

 
 
 

 
 
 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.319842.1565166404000.45947.1565166420281%40Atlassian.JIRA.


Jira (FACT-1984) Call facter gem and facter c++ as puppet does

2019-08-07 Thread Oana Tanasoiu (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oana Tanasoiu created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-1984  
 
 
  Call facter gem and facter c++ as puppet does   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2019/08/07 1:26 AM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Oana Tanasoiu  
 

  
 
 
 
 

 
 Facter-statistax shouldn't make a system call when it calls facter, instead the tool should call facter as puppet does in order the metrics to be more reliable.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

Jira (FACT-1961) Create one fact

2019-08-07 Thread Sebastian Miclea (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Sebastian Miclea assigned an issue to Sebastian Miclea  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-1961  
 
 
  Create one fact   
 

  
 
 
 
 

 
Change By: 
 Sebastian Miclea  
 
 
Assignee: 
 Sebastian Miclea  
 

  
 
 
 
 

 
 
 

 
 
 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.317059.1563435166000.45933.1565163420129%40Atlassian.JIRA.