Project

General

Profile

Actions

User story #13421

closed

User story #13408: Automatically upgrade techniques when we upgrade Rudder

Document prefered method for techniques upgrades

Added by Nicolas CHARLES over 5 years ago. Updated over 5 years ago.

Status:
Released
Priority:
N/A
Category:
Documentation
Target version:
UX impact:
Suggestion strength:
User visibility:
Effort required:
Name check:
Fix check:
Regression:

Description

Documentation states that we should do a gruesome copy to update Techniques after Rudder upgrade
We should recommand using rudder server upgrade-techniques with the proper options

Actions #1

Updated by Nicolas CHARLES over 5 years ago

  • Status changed from New to In progress
  • Assignee set to Nicolas CHARLES
Actions #2

Updated by Nicolas CHARLES over 5 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Nicolas CHARLES to Alexis Mousset
  • Pull Request set to https://github.com/Normation/rudder-doc/pull/506
Actions #3

Updated by Rudder Quality Assistant over 5 years ago

  • Status changed from Pending technical review to Discussion
  • Assignee changed from Alexis Mousset to Nicolas CHARLES
Actions #4

Updated by Nicolas CHARLES over 5 years ago

  • Status changed from Discussion to Pending technical review
  • Assignee changed from Nicolas CHARLES to Alexis Mousset
Actions #5

Updated by Rudder Quality Assistant over 5 years ago

  • Status changed from Pending technical review to Discussion
  • Assignee changed from Alexis Mousset to Nicolas CHARLES
Actions #6

Updated by Nicolas CHARLES over 5 years ago

  • Status changed from Discussion to Pending release
Actions #7

Updated by Vincent MEMBRÉ over 5 years ago

  • Status changed from Pending release to Released
This bug has been fixed in Rudder 4.1.15, 4.3.5 and 5.0.1 which were released today.
Changelog
Changelog
Changelog
Actions

Also available in: Atom PDF