In dump create add type uint64 for values in additional parameters
The additional parameters passed to the dump create interfaces
are accepting a key-value pair and the value should be a string.
In some of the dump use cases an integer error log id needs to be
passed, it was being passed as a string. But to make it
more readable and to reduce conversion errors, updating the dict
definition to accept 32 bit unsigned integer.
Signed-off-by: Dhruvaraj Subhashchandran <dhruvaraj@in.ibm.com>
Change-Id: Iefc3a49c2d569a4b179fc515938349f8f84bb3ae
diff --git a/yaml/xyz/openbmc_project/Dump/Create.interface.yaml b/yaml/xyz/openbmc_project/Dump/Create.interface.yaml
index a2b6382..3daaf2a 100644
--- a/yaml/xyz/openbmc_project/Dump/Create.interface.yaml
+++ b/yaml/xyz/openbmc_project/Dump/Create.interface.yaml
@@ -16,12 +16,13 @@
Method to create a manual Dump.
parameters:
- name: AdditionalData
- type: dict[string, string]
+ type: dict[string, variant[string,uint64]]
description: >
The additional data, if any, for initiating the dump.
The key in this case should be an implementation
specific enum defined for the specific type of dump
either in xyz or in a domain.
+ The values can be either a string or a 64 bit number.
The enum-format string is required to come from a
parallel class with this specific Enum name.
All of the Enum strings should be in the format