Jira (PUP-2928) Puppet tries to update the group for user when he is listed as its member twice.

2018-10-03 Thread Jon Pugh (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jon Pugh updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-2928  
 
 
  Puppet tries to update the group for user when he is listed as its member twice.   
 

  
 
 
 
 

 
Change By: 
 Jon Pugh  
 
 
Affects Version/s: 
 PUP 5.3.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 post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-2928) Puppet tries to update the group for user when he is listed as its member twice.

2018-10-03 Thread Jon Pugh (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jon Pugh commented on  PUP-2928  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Puppet tries to update the group for user when he is listed as its member twice.   
 

  
 
 
 
 

 
 This is also an issue for me. I think the description could also be stated as "puppet user resource does not always correctly honour the membership => 'minimum' attribute". If the worry is backwards compatibility (I personally don't see any concern though) then possibly offer an alternate value eg.  membership => 'unique_minimum' Whilst the file_line fix Ed Marshall suggested might work it is clearly an undesirable and fragile hack implemented only due to necessity as this ticket has not been addressed.  
 

  
 
 
 
 

 
 
 

 
 
 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.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-7779) Re-implement `puppet facts upload` and associated server endpoint

2017-08-29 Thread Jon Pugh (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jon Pugh commented on  PUP-7779 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Re-implement `puppet facts upload` and associated server endpoint  
 
 
 
 
 
 
 
 
 
 
If an option on the agent to run this after each Puppet run could be added it would be very useful for those who want the functionality of https://tickets.puppetlabs.com/browse/PUP-5934 without having to implement their own method of calling the script. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-5934) Updated fact values should be submitted after each Puppet run

2017-07-21 Thread Jon Pugh (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jon Pugh commented on  PUP-5934 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Updated fact values should be submitted after each Puppet run  
 
 
 
 
 
 
 
 
 
 
+1 to the points made by Nick and Reid. As a customer I find the Puppet Console display of facts as they were before the last run to be extremely un-intuitive and find myself explaining to new team members that the reason they are seeing old values for facts they expected to be updated or created by a puppet run is due to this. A "before and after" view would be ideal - at the moment the "after" view only appears after the next run - some people end up doing a second run just to see the facts change. Make it a parameter on the agent if you want customers to actively acknowledge the behaviour perhaps? 
We also find it devalues the use of fact queries via PuppetDB significantly though I acknowledge the points made about "very current facts" being the underlying need. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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