Break apart trigger interface
Having this large type creates confusion for translation. Splitting
this parameter into two fields allows us to remove the variant property
altogether, and allows splitting the rules for each type into their own
description.
The only users of this are bmcweb and telemetry, both of which have
patches up to effect this change under the same topic. Testing in those
patches.
Change-Id: I51a1dd3fe0619aa7a75f92764875552feda01a92
Signed-off-by: Ed Tanous <ed@tanous.net>
diff --git a/yaml/xyz/openbmc_project/Telemetry/TriggerManager.interface.yaml b/yaml/xyz/openbmc_project/Telemetry/TriggerManager.interface.yaml
index b6965fa..2e5d9fe 100644
--- a/yaml/xyz/openbmc_project/Telemetry/TriggerManager.interface.yaml
+++ b/yaml/xyz/openbmc_project/Telemetry/TriggerManager.interface.yaml
@@ -38,11 +38,16 @@
Collection of report names that are updated when threshold
conditions are met. This parameter is ignored if triggerActions
parameter does not contain 'UpdateReport' action.
- - name: thresholds
- type: variant[array[struct[enum[xyz.openbmc_project.Telemetry.Trigger.Type],uint64,enum[xyz.openbmc_project.Telemetry.Trigger.Direction],double]],array[struct[string,enum[xyz.openbmc_project.Telemetry.Trigger.Severity],uint64,string]]]
+ - name: numericThresholds
+ type: array[struct[enum[xyz.openbmc_project.Telemetry.Trigger.Type],uint64,enum[xyz.openbmc_project.Telemetry.Trigger.Direction],double]]
description: >
- Contains array of numeric or discrete thresholds that are
- described in xyz.openbmc_project.Telemetry.Trigger interface.
+ Contains array of numeric thresholds that are described in
+ xyz.openbmc_project.Telemetry.Trigger interface.
+ - name: discreteThresholds
+ type: array[struct[string,enum[xyz.openbmc_project.Telemetry.Trigger.Severity],uint64,string]]
+ description: >
+ Contains array of discrete thresholds that are described in
+ xyz.openbmc_project.Telemetry.Trigger interface.
returns:
- name: triggerPath
type: object_path