Project

General

Profile

Actions

User story #8291

closed

Document easier way to reload techniques after upgrade

Added by Jonathan CLARKE almost 5 years ago. Updated almost 5 years ago.

Status:
Released
Priority:
N/A
Category:
Documentation
Target version:
Suggestion strength:
User visibility:
Effort required:

Description

Currently docs say "After the commit has been validated by GIT, please go to the Rudder web interface, to the Administration tab, Policy Server tab, and click on "Reload Techniques". It will reload the Technique library and trigger a full redeployment on nodes."

Thanks to #7868 we now have "rudder server reload-techniques" command which would fit nicely in this suite of CLI commands.

Actions #1

Updated by Jonathan CLARKE almost 5 years ago

  • Status changed from New to In progress
  • Assignee set to Jonathan CLARKE
Actions #2

Updated by Jonathan CLARKE almost 5 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Jonathan CLARKE to Alexis MOUSSET
Actions #3

Updated by Jonathan CLARKE almost 5 years ago

  • Pull Request set to https://github.com/Normation/rudder-doc/pull/184
Actions #4

Updated by Jonathan CLARKE almost 5 years ago

  • Status changed from Pending technical review to Pending release
  • % Done changed from 0 to 100
Actions #5

Updated by Vincent MEMBRÉ almost 5 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 3.1.10 and 3.2.3 which were released on 2016-06-01, but not announced.

Actions

Also available in: Atom PDF