Project

General

Profile

Actions
Copy link

Bug #6284

closed

Add a --force option to rudder-dev

Added by Benoît PECCATTE almost 10 years ago. Updated over 9 years ago.

Status:
Released
Priority:
N/A
Assignee:
Vincent MEMBRÉ
Category:
Rudder dev tools
Target version:
master
Pull Request:
https://github.com/Normation/rudder-t...
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

Rudder-dev always stops on error.
Using --force would allow to rerun a command and acknowledge that a command can fail (for example if the first part of the command has already been done)

Actions
Copy link
 #1

Updated by Benoît PECCATTE almost 10 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Benoît PECCATTE to Vincent MEMBRÉ
  • Pull Request set to https://github.com/Normation/rudder-tools/pull/41
Actions
Copy link
 #2

Updated by Benoît PECCATTE over 9 years ago

  • Status changed from Pending technical review to Pending release
  • % Done changed from 0 to 100
Actions
Copy link
 #4

Updated by Benoît PECCATTE over 9 years ago

  • Category set to Rudder dev tools
Actions
Copy link
 #5

Updated by Benoît PECCATTE over 9 years ago

  • Target version deleted (3.1.0~beta1)
Actions
Copy link
 #6

Updated by Benoît PECCATTE over 9 years ago

  • Status changed from Pending release to Released
  • Target version set to master
Actions
Copy link

Also available in: Atom PDF