Clarify trigger semantics for pipeline-errors 'threshold' and 'active'#1494
Clarify trigger semantics for pipeline-errors 'threshold' and 'active'#1494earies wants to merge 1 commit into
Conversation
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request updates the openconfig-platform-pipeline-counters YANG model to version 0.5.2. It adds a new revision entry and provides clearer descriptions for the threshold and active leaves regarding their trigger and transition semantics. A review comment correctly identifies that the revision date is set to a future date and should be corrected.
|
/gcbrun |
|
No major YANG version changes in commit cbfc9b4 |
|
OC Review June 2nd. There is an conflicting change that has bumped up the version of the yang file to 6.0, please make the version change into 6.1 after re basing to latest master for us to take it further. |
|
OC operator review June 23. @earies could you take care of the conflict ? We can take this to closure right after that. |
* (M) release/models/platform/openconfig-platform-pipeline-counters.yang
- Clarify trigger semantics for 'threshold' and 'active'
- Increment to version 0.5.2
earies
force-pushed
the
pipeline-counters-threshold
branch
from
9987b23 to
cbfc9b4
Compare
ack - branch is up to date and conflict resolved |
|
/gcbrun |
4 participants
Change Scope
Clarify the trigger semantics shared by pipeline-errors-common
thresholdandactiveleafs. Documentation only change, no schema changes.Platform Implementations
N/A
Tree View
No tree updates were made as part of this patchset.