tree ab5d2c93fe8c58ae12a1f6910de10ea3fc3ad03e
parent 14c8aee20d25e59bda722e5d09527ee675c926e2
author Ed Tanous <ed.tanous@intel.com> 1558636956 -0700
committer Ed Tanous <ed.tanous@intel.com> 1560532579 +0000

Fix some of the system endpoints

1. Move the system endpoints to AsyncResp where possible.  This starts
to clean up our scope issues, and makes the code a bit cleaner, as it's
not tabbed in as much.  It's by no means a fix, but it certainly is
better, and easier to verify.  Also it gives us throw protection as far
as the connection objects go.
2. Implement the "properties" field when accessing urls like:
/bus/system/<serviceName>/<ObjectPath>/<InterfaceName>

Tested:
Called GET on
/bus/system/xyz.openbmc_project.FanSensor/xyz/openbmc_project/sensors/fan_tach/Fan_1/xyz.openbmc_project.Sensor.Value

and observed the response:
{
  "bus_name": "xyz.openbmc_project.FanSensor",
  "interface": "xyz.openbmc_project.Sensor.Value",
  "methods": [],
  "object_path": "/xyz/openbmc_project/sensors/fan_tach/Fan_1",
  "properties": {
    "MaxValue": 14000.0,
    "MinValue": 0.0,
    "Value": null
  },
  "signals": [],
  "status": "ok"
}

Previous to this patch, properties was an empty object {}

Signed-off-by: Ed Tanous <ed.tanous@intel.com>
Change-Id: I8fceb395fb64f2a1857df8ba64b5914c09c18552