Bug #6312

Outdated chapter: Disable automatic regeneration of promises

Added by Florian Heigl about 6 years ago. Updated almost 6 years ago.

Target version:
Pull Request:
User visibility:
Effort required:


The documentation for 2.x and 3.x mentions the option the automatic policy generation:

"In certain circumstances, it can be necessary to disable the automatic regeneration of the promises. It can be done by setting following property to false in /opt/rudder/etc/
When switching to manual deployment of promises, the presence of pending changes is advertised on top of the Regenerate now button. Each modification can be reviewed before validation."

There's two specialties about this:
  • it seems to no longer work
  • it is deprecated

08:41 < darkfader> (it seems it includes the latest version now)
08:42 < darkfader> q: is rudder.autoDeployOnModification=false
08:42 < darkfader> still supported?
08:43 < darkfader> i tried to set that up but it seems nothing changed
09:24 < ncharles> darkfader: this is deprecated


Updated by François ARMAND about 6 years ago

  • Status changed from New to Discussion
  • Assignee set to Matthieu CERDA
  • Priority changed from N/A to 3

Thanks for reporting, bad doc is the worse kind of bug.

Matthieu, do you think that you can handle that ?


Updated by Benoît PECCATTE about 6 years ago

  • Project changed from Rudder-Doc to Rudder
  • Category set to Documentation

Updated by François ARMAND about 6 years ago

  • Status changed from Discussion to In progress
  • Assignee changed from Matthieu CERDA to François ARMAND
  • Target version set to 2.10.13

Updated by François ARMAND about 6 years ago

  • Status changed from In progress to Pending release
  • % Done changed from 0 to 100

Updated by Vincent MEMBRÉ almost 6 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 2.10.13, 2.11.10 and 3.0.4 which were released today.

Also available in: Atom PDF