Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

implement or deviate the control/max-alarm-status-changes leaf #1

Open
jktjkt opened this issue Jan 22, 2024 · 0 comments
Open

implement or deviate the control/max-alarm-status-changes leaf #1

jktjkt opened this issue Jan 22, 2024 · 0 comments

Comments

@jktjkt
Copy link
Collaborator

jktjkt commented Jan 22, 2024

In the alarm control, there's a leaf called /alarms/control/max-alarm-status-changes which is supposed to control the length of some alarm status history list. Currently we do not implement that leaf, but there's no deviation which would say that it isn't supported, and the default value is kept at the RFC default of 32.

This needs triaging; I have no idea how useful that leaf is. As a minimum, however, its default value should be augmented, or it should be marked as not supported.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant