Feature #864

Enhance puppetrun to pass through --no-noop functionality

Added by Derek Whayman over 4 years ago. Updated 8 months ago.

Status:Accepted Start date:
Priority:Normal Due date:
Assignee:- % Done:

0%
Category:executables
Target version:-
Affected Puppet version:0.24.4 Branch:
Keywords:
Votes: 6

Description

If I use noop=true for regular puppetd runs so I get the “what would happen?” reports, I cannot use puppetrun to trigger a noop=false run on clients. This request is to add a switch or similar to puppet runs that prods the puppetd run into running with —no-noop (or similar).

Many thanks, Derek

Related issues

related to Puppet - Feature #3868: disable use_cached_catalog in puppet kick Closed 05/25/2010

History

#1
Updated by Redmine Admin almost 4 years ago

  • Status changed from 1 to Accepted

#2
Updated by James Turnbull over 3 years ago

  • Category changed from newfeature to executables
  • Affected Puppet version set to 0.24.4

#3
Updated by James Turnbull almost 3 years ago

  • Assignee deleted (Puppet Community)

#4
Updated by Jesse Wolfe almost 2 years ago

  • Target version changed from 4 to 52

#5
Updated by James Turnbull over 1 year ago

  • Status changed from Accepted to Needs Decision
  • Assignee set to Luke Kanies
  • Target version deleted (52)

Luke – I would have thought this would have worked? hmmm.

#6
Updated by Mohit Chawla over 1 year ago

  • Target version set to 2.6.1

This could be really useful. :)

#7
Updated by James Turnbull over 1 year ago

  • Target version deleted (2.6.1)

#8
Updated by Luke Kanies over 1 year ago

  • Status changed from Needs Decision to Accepted
  • Assignee deleted (Luke Kanies)

I thought I accepted this ages ago.

Also available in: Atom PDF