Rudder

OK, so this a bit complicated. We missed the categories for groups and rules (not as important because it's a tag on rule, not the whole tree).

It's a big change: we need to rethink the directory layout to keep the same as groups for /var/rudder/config-repo.
And have a way to handle groups exported with an incorrect category. I think I will just create a category with name == uuid in that case and add them to that.

We weren't moving groups which changed categories either.

The chosen new mapping is one that match the LDAP/UI representation of group categories and groups:

archive/
 `- groups
      |- category_with_name
      |     |- category.json // the category info: uuid, name, etc
      |     `- some_group.json // the group as before
      `- some_group_under_root_category.json

This mapping is so-so, since the group serialisation also contains the group category id, so we duplicate the information, and if we move a group, it doesn't actually change its category, which is surprising. But I wanted to have the same json serialisation than the one from API.

I hesitated with a mappring like:

archive/
 |- group-categories.json // one big json will the categories 
 `- groups
      |- some_group.json // the group as before
      `- some_group_under_root_category.json

But it was strang to have a mixe of "one item for each groups" and "one big json with lots of categories".
Still, maybe it would be easier to manipulate.