diff options
| author | Deepak Kodihalli <dkodihal@in.ibm.com> | 2017-01-17 04:25:22 -0600 |
|---|---|---|
| committer | Deepak Kodihalli <dkodihal@in.ibm.com> | 2017-01-27 10:42:17 -0600 |
| commit | 160d3e0b810f6c5f582c7daf906ce0c99cd4194e (patch) | |
| tree | 6c918b816030b51e3c927583002a10d92a7aa66e /tools/example | |
| parent | 9916119f0daad8bd5b3fbd926ada9a023949f311 (diff) | |
| download | phosphor-logging-160d3e0b810f6c5f582c7daf906ce0c99cd4194e.tar.gz phosphor-logging-160d3e0b810f6c5f582c7daf906ce0c99cd4194e.zip | |
elog-gen.py : read multiple error yaml files
This change enables the elog-gen script to look at more than one error
yaml file (and corresponding metadata yaml file). The input to the
script had to be changed to a yaml directory, containing
error yaml files, instead of a single error yaml file.
The reason to support reading multiple error yaml files is that,
without this, applications have to all dump their errors in a single big
error yaml file. Now it's possible to write application/domain specific
error yaml files; they just need to be exported to the same location,
from where elog-gen.py can pick them.
Change-Id: I9418bf0e0b54a7b7f7701b337649cb8eb4c54913
Signed-off-by: Deepak Kodihalli <dkodihal@in.ibm.com>
Diffstat (limited to 'tools/example')
| -rw-r--r-- | tools/example/xyz/openbmc_project/Example/Foo.errors.yaml | 2 | ||||
| -rw-r--r-- | tools/example/xyz/openbmc_project/Example/Foo.metadata.yaml | 5 |
2 files changed, 7 insertions, 0 deletions
diff --git a/tools/example/xyz/openbmc_project/Example/Foo.errors.yaml b/tools/example/xyz/openbmc_project/Example/Foo.errors.yaml new file mode 100644 index 0000000..73fe62b --- /dev/null +++ b/tools/example/xyz/openbmc_project/Example/Foo.errors.yaml @@ -0,0 +1,2 @@ +- name: Foo + description: this is test error Foo diff --git a/tools/example/xyz/openbmc_project/Example/Foo.metadata.yaml b/tools/example/xyz/openbmc_project/Example/Foo.metadata.yaml new file mode 100644 index 0000000..2ac0532 --- /dev/null +++ b/tools/example/xyz/openbmc_project/Example/Foo.metadata.yaml @@ -0,0 +1,5 @@ +- name: Foo + level: INFO + meta: + - str: "FOO_DATA=%s" + type: string |
