Project

General

Profile

Actions
Copy link

User story #8291

closed

Document easier way to reload techniques after upgrade

Added by Jonathan CLARKE over 8 years ago. Updated over 8 years ago.

Status:
Released
Priority:
N/A
Assignee:
Alexis Mousset
Category:
Documentation
Target version:
3.1.10
Pull Request:
https://github.com/Normation/rudder-d...
UX impact:
Suggestion strength:
User visibility:
Effort required:
Name check:
Fix check:
Regression:

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
Copy link
 #1

Updated by Jonathan CLARKE over 8 years ago

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

Updated by Jonathan CLARKE over 8 years ago

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

Updated by Jonathan CLARKE over 8 years ago

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

Updated by Jonathan CLARKE over 8 years ago

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

Updated by Vincent MEMBRÉ over 8 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
Copy link

Also available in: Atom PDF