schemas: fix virtual_sensor.json
Added a few properties which were configured but missing from the
schema. I doubt that the phosphor-virtual-sensor supports those anyways,
but this patch can be a starting point for discussion with the code
owners.
Missing properties: PowerState, EntityId, EntityInstance
Tested: Schema Validator Pass
Change-Id: I41ca35b2f3427704c87a58e44ea2ecf1a7adfbe3
Signed-off-by: Alexander Hansen <alexander.hansen@9elements.com>
diff --git a/schemas/virtual_sensor.json b/schemas/virtual_sensor.json
index 5239b30..c10fbce 100644
--- a/schemas/virtual_sensor.json
+++ b/schemas/virtual_sensor.json
@@ -2,6 +2,7 @@
"$schema": "http://json-schema.org/draft-07/schema#",
"$defs": {
"VirtualSensor": {
+ "additionalProperties": false,
"title": "phosphor-virtual-sensor configuration",
"description": "The configuration used by the virtual-sensor daemon in the phosphor-virtual-sensor repository. Virtual sensors are xyz.openbmc_project.Sensor.Value D-Bus objects that have sensor values calculated from the D-Bus sensors listed here.",
"type": "object",
@@ -25,6 +26,15 @@
"Name": {
"type": "string"
},
+ "PowerState": {
+ "$ref": "legacy.json#/$defs/Types/PowerState"
+ },
+ "EntityId": {
+ "$ref": "legacy.json#/$defs/Types/EntityId"
+ },
+ "EntityInstance": {
+ "$ref": "legacy.json#/$defs/Types/EntityInstance"
+ },
"Sensors": {
"description": "Any DBus sensors whose values are used to determine the value of the virtual sensor.",
"items": {