ROS2 Configuration management
Hello,
In my project, as we get more customers, more hardware versions, more robots, configuration management is becoming more and more complex to manage and I'm wondering how does the ROS community handle it.
Our config is centralized in the bringup package, as it is for many I assume. One idea would be to move the config to its own repository and create a branch for each robot. A problem with that approach is that, to add/delete/modify a parameter, one would have to do it for each branch.
Another approach would be to have a default configuration in the bringup package/repository and in a separate configuration repository, create branches for each robot but only with some yaml files that override the defaults.
How do you version control your ROS configuration efficiently and scalably for a system where parameter modifications is still very common? This doesn't sound like a ROS/Robotics specific problem yet I failed to find much help online.