datastores

asternos datastore operations rpcs rpcs copy config copy config path access /copy config/input read write /copy config/input/source read write /copy config/input/target read write /copy config/input /copy config/input path /copy config/input node type container access read write /copy config/input/source /copy config/input/source path /copy config/input/source node type leaf access read write data type \<yang type union> constraints multiple constraints the uri type represents a uniform resource identifier (uri) as defined by the rule 'uri' in rfc 3986 objects using the uri type must be in us ascii encoding, and must be normalized as described by rfc 3986 sections 6 2 1, 6 2 2 1, and 6 2 2 2 characters that can be represented without using percent encoding are represented as characters (without percent encoding), and all case insensitive characters are set to lowercase except for hexadecimal digits within a percent encoded triplet, which are normalized to uppercase as described in section 6 2 2 1 of rfc 3986 the purpose of this normalization is to help provide unique uris note that this normalization is not sufficient to provide uniqueness two uris that are textually distinct after this normalization may still be equivalent objects using the uri type may restrict the schemes that they permit for example, 'data ' and 'urn ' schemes might not be appropriate a zero length uri is not a valid uri this can be used to express 'uri absent' where required in the value set and its semantics, this type is equivalent to the uri smiv2 textual convention defined in rfc 5017 enumeration with options startup running mandatory yes /copy config/input/target /copy config/input/target path /copy config/input/target node type leaf access read write data type \<yang type union> constraints multiple constraints enumeration with options startup the uri type represents a uniform resource identifier (uri) as defined by the rule 'uri' in rfc 3986 objects using the uri type must be in us ascii encoding, and must be normalized as described by rfc 3986 sections 6 2 1, 6 2 2 1, and 6 2 2 2 characters that can be represented without using percent encoding are represented as characters (without percent encoding), and all case insensitive characters are set to lowercase except for hexadecimal digits within a percent encoded triplet, which are normalized to uppercase as described in section 6 2 2 1 of rfc 3986 the purpose of this normalization is to help provide unique uris note that this normalization is not sufficient to provide uniqueness two uris that are textually distinct after this normalization may still be equivalent objects using the uri type may restrict the schemes that they permit for example, 'data ' and 'urn ' schemes might not be appropriate a zero length uri is not a valid uri this can be used to express 'uri absent' where required in the value set and its semantics, this type is equivalent to the uri smiv2 textual convention defined in rfc 5017 mandatory yes