Project

General

Profile

Actions

Bug #9157

closed

JS Script, Node Properties expansion and Quicksearch should be disabled on migration

Added by François ARMAND over 7 years ago. Updated over 7 years ago.

Status:
Released
Priority:
1
Category:
System integration
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

We want to have the following behaviour:

- for new install of 3.1/3.2, we want to enable by default JSscript, Node properties expansion and quicksearch
- for existing instance migrated, we want them to be disabled (no behavior change)
- for future migration, we want to keep the same behavior as the one configured by the user

So we need to :

- add in boostrap.ldif "feature enabled" for the three of them, so that future migration don't thing there are not set,
- add "disable feature" in a migration script, to avoid changing behavior of existing config.


Subtasks 1 (0 open1 closed)

User story #9160: Disable features (quicksearch, js engine, node properties) on upgrade ReleasedFrançois ARMAND2016-09-28Actions
Actions #1

Updated by Vincent MEMBRÉ over 7 years ago

  • Status changed from New to In progress
Actions #2

Updated by Vincent MEMBRÉ over 7 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Vincent MEMBRÉ to François ARMAND
  • Pull Request set to https://github.com/Normation/rudder/pull/1211
Actions #3

Updated by Vincent MEMBRÉ over 7 years ago

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

Updated by Vincent MEMBRÉ over 7 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 3.1.15/14 and 3.2.8/7 which were released today.

Actions

Also available in: Atom PDF