treewide: use more specific object_path type
The sdbus++ tool allows the YAML to specify either "path" or
"object_path". Switch to "object_path" everywhere for consistency
and clarity.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I60c51b2ece5fc4cb23d05ce5151301db3dcddf3a
diff --git a/yaml/xyz/openbmc_project/HardwareIsolation/Create.interface.yaml b/yaml/xyz/openbmc_project/HardwareIsolation/Create.interface.yaml
index eed4373..0262660 100644
--- a/yaml/xyz/openbmc_project/HardwareIsolation/Create.interface.yaml
+++ b/yaml/xyz/openbmc_project/HardwareIsolation/Create.interface.yaml
@@ -12,7 +12,7 @@
for example, the user voluntarily tried to isolate hardware.
parameters:
- name: IsolateHardware
- type: path
+ type: object_path
description: >
The hardware inventory path which is needs to isolate.
- name: Severity
@@ -21,7 +21,7 @@
The severity of hardware isolation.
returns:
- name: Path
- type: path
+ type: object_path
description: >
The path of created xyz.openbmc_project.HardwareIsolation.Entry
object.
@@ -43,7 +43,7 @@
the isolation.
parameters:
- name: IsolateHardware
- type: path
+ type: object_path
description: >
The hardware inventory path which is needs to isolate.
- name: Severity
@@ -51,12 +51,12 @@
description: >
The severity of hardware isolation.
- name: BmcErrorLog
- type: path
+ type: object_path
description: >
The BMC error log caused the isolation of hardware.
returns:
- name: Path
- type: path
+ type: object_path
description: >
The path of created xyz.openbmc_project.HardwareIsolation.Entry
object.