PR Details

Description

For CDASim, carma exec doesn't work because network configuration is hardcoded to host, but cdasim uses different IPs. I could use docker exec but this won't last in between test and have to do the sourcing exporting again, which is not user-friendly. This will be useful only for Sim PCs as vehicles don't need it right away. And it can be updated whenever the script is updated next.

This PR lets the user specify network to connect to. Usage: carma exec -n network_name

Related GitHub Issue

Related Jira Key

Motivation and Context

This happens a lot when I try to test something in CDASim, I need to change the network myself in the /usr/bin/carma script.

How Has This Been Tested?

CDASIM

Types of changes

[ ] Defect fix (non-breaking change that fixes an issue)
[X] New feature (non-breaking change that adds functionality)
[ ] Breaking change (fix or feature that cause existing functionality to change)

Checklist:

[X] I have added any new packages to the sonar-scanner.properties file
[X] My change requires a change to the documentation.
[X] I have updated the documentation accordingly.
[X] I have read the CONTRIBUTING document.
[X] I have added tests to cover my changes.
[X] All new and existing tests passed.

usdot-fhwa-stol / carma-platform

carma exec to accept network #2457