[#86] Clarify that Attributes can't have empty values

In case there is a need to set flag-like attributes, the value should be set to
something like `true` or `1`.

Signed-off-by: Stanislav Bogatyrev <stanislav@nspcc.ru>
This commit is contained in:
Stanislav Bogatyrev 2020-12-08 13:48:51 +03:00 committed by Stanislav Bogatyrev
parent 29c9e1d68b
commit 063ec430d1
3 changed files with 9 additions and 2 deletions

View file

@ -28,8 +28,10 @@ message Container {
uint32 basic_acl = 4 [json_name = "basicACL"];
// `Attribute` is a user-defined Key-Value metadata pair attached to the
// container. Container attribute are immutable. They are set at container
// creation and cna never be added or updated.
// container. Container attributes are immutable. They are set at container
// creation and can never be added or updated.
//
// Key name must be a valid UTF-8 string. Value can't be empty.
//
// There are some "well-known" attributes affecting system behaviour:
//

View file

@ -131,6 +131,9 @@ message NodeInfo {
// Administrator-defined Attributes of the NeoFS Storage Node.
//
// `Attribute` is a Key-Value metadata pair. Key name must be a valid UTF-8
// string. Value can't be empty.
//
// Node's attributes are mostly used during Storage Policy evaluation to
// calculate object's placement and find a set of nodes satisfying policy
// requirements. There are some "well-known" node attributes common to all the

View file

@ -86,6 +86,8 @@ message Header {
// `Attribute` is a user-defined Key-Value metadata pair attached to the
// object.
//
// Key name must be a valid UTF-8 string. Value can't be empty.
//
// There are some "well-known" attributes starting with `__NEOFS__` prefix
// that affect system behaviour:
//