Project

General

Profile

Actions

Bug #15183

open

Reload technique library when restoring an archive

Added by Vincent MEMBRÉ about 2 years ago. Updated 7 days ago.

Status:
New
Priority:
N/A
Assignee:
-
Category:
Web - Maintenance
Target version:
Severity:
Minor - inconvenience | misleading | easy workaround
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Very Small
Priority:
51

Description

When we restore Directives and Techniques using an archive, we don't reload technique library, this can lead to disabled Techniques and Directives (they are based on a Technique that does not exist)

This does not occur if you restore techniques manually, or wait for it to run automatically, before restoring archive

We should do like we do for #4480, and trigger a synchrone technique library update before ending the archive restoration


Related issues

Related to Rudder - Bug #4480: When restoring archive (full or groups) dynamic groups are created emptyReleasedNicolas CHARLESActions
Related to Rudder - Bug #15180: Correct archives procedure to include a 'technique reload'ReleasedVincent MEMBRÉActions
Actions #1

Updated by Vincent MEMBRÉ about 2 years ago

  • Related to Bug #4480: When restoring archive (full or groups) dynamic groups are created empty added
Actions #2

Updated by Vincent MEMBRÉ about 2 years ago

  • Related to Bug #15180: Correct archives procedure to include a 'technique reload' added
Actions #3

Updated by François ARMAND about 2 years ago

  • Severity set to Minor - inconvenience | misleading | easy workaround
  • User visibility set to Operational - other Techniques | Rudder settings | Plugins
  • Priority changed from 0 to 32
Actions #4

Updated by Vincent MEMBRÉ almost 2 years ago

  • Target version changed from 5.0.13 to 5.0.14
Actions #5

Updated by Vincent MEMBRÉ almost 2 years ago

  • Target version changed from 5.0.14 to 5.0.15
  • Priority changed from 32 to 31
Actions #6

Updated by François ARMAND over 1 year ago

  • Effort required set to Very Small
  • Priority changed from 31 to 58

Is this still the case since #15180 is done?

Actions #7

Updated by Vincent MEMBRÉ over 1 year ago

This could be done directly without the need to do it manually after the import so yes i think it's still valid, but documentation is ok now ...

Actions #8

Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 5.0.15 to 5.0.16
Actions #9

Updated by Alexis MOUSSET over 1 year ago

  • Target version changed from 5.0.16 to 5.0.17
  • Priority changed from 58 to 55
Actions #10

Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 5.0.17 to 5.0.18
  • Priority changed from 55 to 53
Actions #11

Updated by Vincent MEMBRÉ about 1 year ago

  • Target version changed from 5.0.18 to 5.0.19
  • Priority changed from 53 to 51
Actions #12

Updated by Vincent MEMBRÉ 11 months ago

  • Target version changed from 5.0.19 to 5.0.20
Actions #13

Updated by Vincent MEMBRÉ 9 months ago

  • Target version changed from 5.0.20 to 797
Actions #14

Updated by Benoît PECCATTE 28 days ago

  • Target version changed from 797 to 6.1.14
Actions #15

Updated by Vincent MEMBRÉ 20 days ago

  • Target version changed from 6.1.14 to 6.1.15
Actions #16

Updated by Vincent MEMBRÉ 7 days ago

  • Target version changed from 6.1.15 to 6.1.16
Actions

Also available in: Atom PDF