[FEATURE]: Require full path to configuration file at launch

[evan-palmer]

Feature Type

Changing existing functionality in the BlueROV2 driver

Problem Description

When other projects include the launch file from the blue project to launch the system, they are required to add a configuration file to the blue_bringup package instead of the bringup package of the project launching the blue system. This is cumbersome and makes it difficult to modify the blue configurations.

Feature Description

Require the full path to the configuration file to be provided at launch rather than a configuration file in the blue_bringup/configs directory.

Alternative Solutions

Another option could be to break the arguments up to specify the full path to the configuration file directory, then the configuration file name; however, this could be difficult to use and may cause confusion.

Additional Context

No response

[evan-palmer]

After reviewing what I've done in the past (see here, I think that I will actually replicate the approach that I took there