date:20180305

Jira (PUP-8513) Cannot add a resource parameter, when a default resource declaration already defines this param

2018-03-05 Thread Peter Meier (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Peter Meier created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8513  
 
 
  Cannot add a resource parameter, when a default resource declaration already defines this param   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Affects Versions: 
 PUP 5.4.0  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 Language  
 
 
Created: 
 2018/03/05 11:43 PM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Peter Meier  
 

  
 
 
 
 

 
 The following manifests fails with the error:  
 
 
 
 
 Error: Parameter 'ignore' is already set on File[/tmp/puppet-test] by # at /tmp/foo.pp:3; cannot redefine at /tmp/foo.pp:13 on node bla  
 
 
 
  Manifest:  
 
 
 
 
 File {  
 
 
   ignore => '*.bak'

Jira (FACT-1528) Custom Ruby facts with additional resolutions instead replace core facts

2018-03-05 Thread Matthew Patton (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Matthew Patton commented on  FACT-1528  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Custom Ruby facts with additional resolutions instead replace core facts   
 

  
 
 
 
 

 
 was there a regression since 3.4.x? I'm using 3.6.6 (commit d0295a91b6) and try as I might can't override build-in facts via custom. I can override via commandline:  
 
 
 
 
 FACTER_os="some string" facter os   
 
 
 
  but any value of 'has_weight' (or omitted) yields no updates  
 
 
 
 
 separator = { 'file' => File::SEPARATOR, 'path' => File::PATH_SEPARATOR }  
 
 
    
 
 
 combined = Facter.value(:os).merge({ 'separator' => separator })  
 
 
 Facter.add(:os) do  
 
 
   has_weight(99)  
 
 
   setcode do  
 
 
 combined  
 
 
   end  
 
 
 end  
 
 
 
  I'm expecting to see but alas the 'separator' block never comes thru.

Jira (PDOC-48) @author tag is swallowed up

2018-03-05 Thread Jo Rhett (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jo Rhett commented on  PDOC-48  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: @author tag is swallowed up   
 

  
 
 
 
 

 
 I was referring to that author tag. My idea was that if we are going to waste a few lines with that detail, let's use the tag. Since the PDF templates don't contain this it does seem to be going away so I agree that it's not helpful. I never loved that part of the template.  
 

  
 
 
 
 

 
 
 

 
 
 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-8413) Show refresh commands that the service provider would issue during "noop" run

2018-03-05 Thread Charlie Sharpsteen (JIRA)

Title: Message Title

Charlie Sharpsteen commented on PUP-8413

Re: Show refresh commands that the service provider would issue during "noop" run

Yup, we would have to start generating events in order to trigger actions like service refresh. Looks like the event manager might even queue "noop" events in these cases: https://github.com/puppetlabs/puppet/blob/5.4.0/lib/puppet/transaction/event_manager.rb#L161-L166 The issue is that these downstream events don't trigger any refresh action on providers where details could be logged. We could do this, but we'd have to figure out a way to ensure that 3rd-party providers don't suddenly start taking action when a noop event is delivered because such an event has never come in before. This might have to be an opt-in behavior where the events are only delivered to providers that advertise support for a noop_referesh 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 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-8511) Total time reported in report probably isn't reflective of reality

2018-03-05 Thread Melissa Stone (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Melissa Stone updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8511  
 
 
  Total time reported in report probably isn't reflective of reality   
 

  
 
 
 
 

 
Change By: 
 Melissa Stone  
 
 
Sub-team: 
 Coremunity  
 
 
Team: 
 Platform Core  
 

  
 
 
 
 

 
 
 

 
 
 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 (BOLT-363) 'all' target with mixed ssh and winrm transports runs all nodes on both transports

2018-03-05 Thread Kate Lopresti (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Kate Lopresti commented on  BOLT-363  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: 'all' target with mixed ssh and winrm transports runs all nodes on both transports   
 

  
 
 
 
 

 
 Added to release notes under Resolve Issues.   
 

  
 
 
 
 

 
 
 

 
 
 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 (BOLT-363) 'all' target with mixed ssh and winrm transports runs all nodes on both transports

2018-03-05 Thread Kate Lopresti (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Kate Lopresti updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-363  
 
 
  'all' target with mixed ssh and winrm transports runs all nodes on both transports   
 

  
 
 
 
 

 
Change By: 
 Kate Lopresti  
 
 
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 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-8512) Separate external node classifier per environment

2018-03-05 Thread Colin Deisenroth (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Colin Deisenroth created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8512  
 
 
  Separate external node classifier per environment   
 

  
 
 
 
 

 
Issue Type: 
  New Feature  
 
 
Affects Versions: 
 PUP 5.4.0  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 Puppet Server  
 
 
Created: 
 2018/03/05 4:48 PM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Colin Deisenroth  
 

  
 
 
 
 

 
 I would like to be able to use a different external node classifier based on environments, so I can test changes and then merge to the production branch.   It looks like a few tickets have been submitted about this: PUP-4521 - Pass agent-requested environment to external node classifiers PUP-4522 - Provide Facts for a classifier to select whether to enable overriding the environment PUP-5032 - Update node terminus configured_environment to mirror agent_specified_environment   However I can't understand how I should access "configured_environment" or "agent_specified_environment" within the ENC script.   My ideal solution would be to call the node classifier based on that variable, but I don't think this will be possible:  
 
 
 
 
 external_nodes = $codedir/environments/${::agent_specified_environment}/bin/enc.rb  
 
 
 
    I was told there can only be 1 ENC, but I can write a main one that is a wrapper script which can

1 2 >

1 - 100 of 110 matches

Mail list logo