Project

General

Profile

Actions

Bug #3130

closed

Changes on directives are not tracked by configuration repository

Added by Vincent MEMBRÉ about 11 years ago. Updated about 9 years ago.

Status:
Rejected
Priority:
2
Category:
Packaging
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

Just like migrating technique version from a directive (#3129), making changes to a directive is not tracked by the git repository.

Every changes (name, description, parameters) are never sent to the configuration repository, so a Directive value on the configuration respository has only the value we set it when we created thsi Directive.

There should be a git commit containing all the informations relative to those changes.

Plus there is no event log generated for any modification on directives, but i'll open another bug about that


Related issues 1 (0 open1 closed)

Is duplicate of Rudder - Bug #3129: Migrating a Directive to a new Technique version can lead to EventLog generation errorReleasedFrançois ARMAND2013-01-02Actions
Actions #1

Updated by Nicolas PERRON about 11 years ago

  • Target version changed from 2.5.0~beta1 to 2.5.0~rc1
Actions #2

Updated by Vincent MEMBRÉ about 11 years ago

  • Status changed from New to Rejected
  • Target version changed from 2.5.0~rc1 to 2.4.3

This bug is duplicates to #3129.

Changes were not savec because the technique version migration was not working.

fixing #3129 will fix it, so i reject this bug

Actions #3

Updated by Matthieu CERDA about 11 years ago

  • Target version changed from 2.4.3 to 2.4.4
Actions #4

Updated by Nicolas PERRON about 11 years ago

  • Project changed from Rudder to 34
  • Category deleted (11)
Actions #5

Updated by Benoît PECCATTE about 9 years ago

  • Project changed from 34 to Rudder
  • Category set to Packaging
Actions

Also available in: Atom PDF