Doubtful documentation of `NodeInfo.Attribute` #75

New issue

Open

opened 2025-12-28 18:12:25 +00:00 by sami · 0 comments

sami commented

2025-12-28 18:12:25 +00:00

Owner

Originally created by @cthulhu-rider on GitHub (Jun 7, 2022).

From netmap.NodeInfo.Attribute docs:

  // A string representation of the chain of attributes in NeoFS Storage
  // Node configuration uses ":" and "/" symbols, e.g.:
  //
  //        `NEOFS_NODE_ATTRIBUTE_1=key1:val1/key2:val2`
  //
  // Therefore the string attribute representation in the Node configuration must
  // use "\:", "\/" and "\\" escaped symbols if any of them appears in an attribute's
  // key or value.

The structure of the node attribute message provides needed feature of attribute inheritance. Mentioned doc part describes some sort of string interpretation for the particular storage node configuration. Do we need it in the protocol description? This seems like an implementation-dependent statements.

Originally created by @cthulhu-rider on GitHub (Jun 7, 2022). From `netmap.NodeInfo.Attribute` docs: ``` // A string representation of the chain of attributes in NeoFS Storage // Node configuration uses ":" and "/" symbols, e.g.: // // `NEOFS_NODE_ATTRIBUTE_1=key1:val1/key2:val2` // // Therefore the string attribute representation in the Node configuration must // use "\:", "\/" and "\\" escaped symbols if any of them appears in an attribute's // key or value. ``` The structure of the node attribute message provides needed feature of attribute inheritance. Mentioned doc part describes some sort of string interpretation for the particular storage node configuration. Do we need it in the protocol description? This seems like an implementation-dependent statements.