Skip to content

Allow explicit running / candidate / operational DSes as a target for various operations #29

Description

@jktjkt

On an NMDA server, we're currently directing all writes to candidate and reads to operational. This has all sorts of nasty surprises, like a set not being visible via a get, etc. Let's at least make this explicit by allowing the data-accessing operations to target a given DS explicitly, or change this in the switch command, etc (and maybe do the right thing by not offering this behavior by default)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions