[Robot] Configuration management #345
Description
Summary
There may/will come a time where we will have multiple of the same sensor, and it will be an annoyance if we will have to adjust the hard-coded values such as IP-addresses per robot / sensor.
Instead, it might be worth it to look into methods of configuration management, such as each robot having it's own .yaml file with its configuration settings, or each robot having its own environment variables that store the right settings.
DOD:
- ...
- Works on the robots
- Works in simulation
- Documentation up-to-date
- Reviewed
Motivation
Get rid of hard-coded variables and avoid having to constantly manually change these variables locally per situation.
Same sensors on a robot that don't conflict on IP address, better fleet management,
Describe Alternatives
Are there other approaches that were considered?
Additional Context
Related issues, links, or references.