Architecture #11155
closed
Warn on risk of updating file format
Description
We need to take care when updating fileFormat in the multi-site git sync scenario. See also https://www.rudder-project.org/redmine/issues/10899 for other problem related to that scenario.
The problem to take care of is when you have two rudder install: Rudder-dev (version y.a.b) and Rudder-prod (x.c.d), and you sync their git in the way: Rudder-dev ==> Rudder-prod (with an "archive restore" on Rudder2 after each git sync), then that scenario is broken if for version y, fileFormat is greater than in version x because rudder-prod will see a file format that it does not understand and will fail the archive restoration.
Updated by François ARMAND over 7 years ago
- Description updated (diff)
- Category set to Documentation
- Status changed from New to In progress
- Assignee set to François ARMAND
- Target version set to 3.1.22
For now, we just want to add a comment with a link to that ticket in the corresponding code.
Updated by François ARMAND over 7 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from François ARMAND to Nicolas CHARLES
- Pull Request set to https://github.com/Normation/rudder/pull/1703
Updated by François ARMAND over 7 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|047c7fa4a960e5786d133163866eb7e034dd2619.
Updated by Vincent MEMBRÉ over 7 years ago
- Status changed from Pending release to Released