Fix 'Context: <blank>' fields in events.yaml and add build-time parsing check to ERROR if Context field not set correctly
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Low
|
Agustin Carranza |
Bug Description
Brief Description
-----------------
Change all “Context: “ lines to “Context: none” … so they explicitly say they have no context and should not be published by automated docs.
And then change parseEventsYaml.py (a build time parsing checker) to generate an error if:
Context is not present in definition
Or
Context is present but has no value
Severity
--------
Minor: System/Feature is usable with minor issue
Steps to Reproduce
------------------
Add/modify an alarm with Context: <Empty>
Expected Behavior
------------------
Parser check rejects the change and informs Context field can not be empty.
Actual Behavior
----------------
Parser check ends successfully.
Reproducibility
---------------
100%
System Configuration
-------
N/A
Branch/Pull Time/Commit
-------
master
Last Pass
---------
N/A
Timestamp/Logs
--------------
N/A
Test Activity
-------------
Developer testing
Workaround
----------
N/A
Changed in starlingx: | |
assignee: | nobody → Agustin Carranza (acarranz) |
Changed in starlingx: | |
importance: | Undecided → Low |
tags: | added: stx.9.0 stx.fault |
Fix proposed to branch: master /review. opendev. org/c/starlingx /fault/ +/883860
Review: https:/