Rudder

I believe that the problem is that in the Rules (and node details) screen, we are using the current configuration (as in "live"), not the one of the last generation (which can be older, like it is in that use case).

I was thinking that the correct solution was to use information from the expected node configuration (ie data actually used in the node), but in fact, it would be extremelly confusing for an user, for example when he just changed a config and the displaying is still on the old one.

So perhaps the least surprising solution is to trigger a regeneration. We didn't do that because we wanted to let the user decide WHEN actually changing the config, in particular when going from audit to enforce. But it is confusing, and more so when everywhere in Rudder we trigger regeneration for everything.

So we should just trigger the regeneration.