Nicolas PERRON wrote:
The consequence will be that the migration to Rudder 2.8 will only be possible from Rudder 2.4.12, 2.6.9 and 2.7.6...
Erm, I'm not sure about that actually - this comma is in the distributePolicy Technique, which by definition is only used on the policy servers (and before 2.8, there could only be a single root policy server). So we don't have to worry about this "broken" promise being on nodes, because it can't be! So in effect, when a Rudder root server is upgraded, the system Techniques including distributePolicy will also be upgraded, and the promises regenerated! Easy :)
However, on the first run(s) of cf-agent, this might cause trouble, in the short period of time in between the rudder-agent upgrade to 3.5.* and the promise regeneration for the policy server. So I agree we should include this fix in older branches, but I don't think we need to change the upgrading procedure.