Project

General

Profile

Actions
Copy link

Bug #3101

closed

Moving a group to a new category does not generate a commit in configuration repository

Added by Vincent MEMBRÉ about 12 years ago. Updated almost 12 years ago.

Status:
Released
Priority:
3
Assignee:
-
Category:
Web - Nodes & inventories
Target version:
2.4.1
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

Moving a node group to a new parent category is not tracked by git.

The old group file is kept.

And the new group is not, until saved is pressed in Rudder, which add another group file

So when regenerating an archive at that time will generate an error has there will be two groups of the same id.

When moving a group, rudder should execute a "git mv groups/old/category/id/group_id groups/new/category/id/group_id" command and commit it.

I don't know which category fits the best, i put "Webapp - node management" as it happened on group page

Actions
Copy link
 #1

Updated by Vincent MEMBRÉ about 12 years ago

  • Target version changed from 2.3.10 to 2.4.2
Actions
Copy link
 #2

Updated by Vincent MEMBRÉ about 12 years ago

  • Status changed from New to Pending technical review
Actions
Copy link
 #3

Updated by Vincent MEMBRÉ almost 12 years ago

The pull request has been retargeted to branch 2.4 to be included in 2.4.1

https://github.com/Normation/rudder/pull/51

Actions
Copy link
 #4

Updated by Nicolas CHARLES almost 12 years ago

  • Status changed from Pending technical review to Pending release
  • Target version changed from 2.4.2 to 2.4.1

This is valid, thank you Vincent !

Actions
Copy link
 #5

Updated by Vincent MEMBRÉ almost 12 years ago

  • % Done changed from 0 to 100
Actions
Copy link
 #7

Updated by Nicolas PERRON almost 12 years ago

  • Status changed from Pending release to Released
Actions
Copy link

Also available in: Atom PDF