Actions
Bug #3101
closedMoving a group to a new category does not generate a commit in configuration repository
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