Jira (PUP-9790) undefined method `pip_version' with pip3 provider

2019-06-30 Thread Maximilian Philipps (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Maximilian Philipps commented on  PUP-9790  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: undefined method `pip_version' with pip3 provider   
 

  
 
 
 
 

 
 Alright, looking forward to it.  
 

  
 
 
 
 

 
 
 

 
 
 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 post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.313529.1561106191000.1534.1561962600159%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-9812) With "root" account, Puppet "ssh_authorized_keys" create file "authorized_keys" & change the owner & group

2019-06-30 Thread Maheswaran Shanmugam (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Maheswaran Shanmugam created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9812  
 
 
  With "root" account, Puppet "ssh_authorized_keys" create file "authorized_keys" & change the owner & group   
 

  
 
 
 
 

 
Issue Type: 
  New Feature  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 Types and Providers  
 
 
Created: 
 2019/06/30 7:02 PM  
 
 
Environment: 
 This case is tested with: PE: 2018.1.x v OS: RHEL 6.9 and Centos 7.0  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Maheswaran Shanmugam  
 

  
 
 
 
 

 
 ``` ssh_authorized_key  { 'ever...@magpie.example.com': ensure => present, user => 'everetv', type => 'ssh-rsa', key => 'B3Nza[...]qXfdaQ==', target => '/opt/sysadm/etc/ssh_keys/everetv/authorized_keys', } ``` By default, in this example, the resource type "ssh_authorized_key" looks for the file "authorized_keys" owned by the specific user "everetv" inside the directory "/opt/sysadm/etc/ssh_keys/everetv/". In the secure environment, this file can't be created as a specific user and end with following error. ``` Error: /Stage[main]/Main/Ssh_authorized_key[ever...@magpie.example.com]: Could not evaluate: Permission denied @ dir_s_mkdir - /opt/sysadm/etc/ssh_keys/everetv  ``` Running agent service as root, there should be a feature to create the key file and change an owner and group as per property is given while defining the resource. This feature will be very handy to deal with the security requirement of the organization where the "non-root" account is not permitted to create the files. This case is raised in connection with customer ticket "https://puppetlabs.zendesk.com/agent/tickets/35293"  
 

  
 
 
 
  

Jira (PDOC-283) Yard gem 0.9.20 causes name spaced puppet functions to render wrong

2019-06-30 Thread Glenn Sarti (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Glenn Sarti commented on  PDOC-283  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Yard gem 0.9.20 causes name spaced puppet functions to render wrong   
 

  
 
 
 
 

 
 PR is ready for merge. https://github.com/puppetlabs/puppet-strings/pull/205  
 

  
 
 
 
 

 
 
 

 
 
 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 post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.314689.1561754673000.1505.1561945560118%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.