Fix ros namespacing for node

xinyi-joffre commented 6 years ago

Changed node_name to rospy.get_name(), so that fully resolved name, including namespace would be included. Since ROS allows for ROS_NAMESPACE environment variables to affect the namespacing of the node, this change will make sure that the rosparam file is loaded under the correct namespace, instead of globally. The topic specified in the relay config will follow standard ROS rules such as global with '/' and without '/' as under same namespace.
Updated message property for topic, since the forward slashes in ROS namespacing convention is not allowed in IotHub messages. Instead, we can replace all forward slashes with a period.

xinyi-joffre commented 6 years ago

Addresses #6

Nardax commented 6 years ago

LGTM

ooeygui commented 5 years ago

Could you resolve this against the C++ codebase and issue a new pull request?

microsoft / ros_azure_iothub