Inconsistent response behavior with a 'values' array

[pkolbeck]

Services and endpoints send responses differently depending on the request.

dripline-python/dripline/core/request_handler.py

Line 32 in 2ff8c54

def do_get_request(self, a_request_message):

Calling get with a specifier, e.g. dl-agent get <service> -s <specifier> returns the value in a dictionary with the "values" key pointing to the value.
Calling get without a specifier, e.g. dl-agent get <endpoint> returns just the value (this could be a dictionary, string, float, etc).
Calling set with a specifier returns a value based on the return value of the implemented on_set.
Calling set without a specifier returns a None value.
Callng cmd (always requires a specifier) returns the value based on the return value of the function called in the implementation.

Out of all of these, only calling get with a specifier puts the return value into a 'values' array. This inconsistency in behavior does not serve a discernible purpose at the moment, and consistent behavior should be established by no longer putting values in a 'values' array.

Applying a calibration function and getting a dictionary of the form {"value_raw": <value_raw>, "value_cal": <value_cal>} would be unaffected.

[wcpettus]

From discussion on 6/30 call: Some of this formatting is imposed by how dl-agent represents responses to the command line. We should look into the actual dripline packets that are getting sent (dl-agent get may be stripping some of the formatting, e.g., it may all be in a {'values' : ...} dict that we aren't seeing)