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.

Sign up for GitHub

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

Jump to bottom

Proposal for clarifications when calling gNMI Set on a list node or element. #140

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Proposal for clarifications when calling gNMI Set on a list node or element. #140

wants to merge 2 commits into from

Commits on May 10, 2021

  1. Proposal for clarifications when calling gNMI Set on a list node or e… 

    …lement.

1. Add example JSON_IETF format for updating an individual list element.
1. Clarify that an empty subset of attributes for a keyed-list is unacceptable as a path for gNMI Set.
1. Clarify that in OpenConfig, MUST specify a path that terminates on the enclosing container in order to modify a whole list node.
1. Minor grammar fixes.

Background: I found these points to be missing from either this doc or
RFC7951. As a result, I'm proposing adding these clarifications that may
or may not be the standard or established convention. In that case,
modification suggestions are welcome to correct any inaccuracies.
    @wenovus
    wenovus committed May 10, 2021
    Configuration menu
    Copy the full SHA
    00c3ad4 View commit details
    Browse the repository at this point in the history

Commits on Oct 20, 2021

  1. Remove openconfig-specific info, fix example, and improve wording.

    @wenovus
    wenovus committed Oct 20, 2021
    Configuration menu
    Copy the full SHA
    393efa1 View commit details
    Browse the repository at this point in the history