Yes - the intent was to address the limitation that an RPC can only be at root.
Actions can be out in a tree & nicely associated with something (e.g. instead
of having a pile of flat RPCs with long names that encode containers like
reset-www-xxx-yyy-zzz-entity).
But I don't really understand
I don’t know the history on this but the intent is to have action tied to a
data node.
https://tools.ietf.org/html/rfc7950#section-7.15
The difference between an action and an rpc is that an action is tied
to a node in the datastore, whereas an rpc is not. When an action is
invoked,
Hi all,
I was a bit surprised to find this in section 7.15 of 7950 recently:
Since an action cannot be defined at the top level of a module or in
a "case" statement, it is an error if a grouping that contains an
action at the top of its node hierarchy is used at the top level of a
