Rename object search and ACL filters fields for consistency

Signed-off-by: Stanislav Bogatyrev <stanislav@nspcc.ru>
This commit is contained in:
Stanislav Bogatyrev 2020-10-23 15:38:31 +03:00 committed by Stanislav Bogatyrev
parent f1acb8c14f
commit b063e5b910
2 changed files with 7 additions and 8 deletions

View file

@ -98,10 +98,9 @@ message EACLRecord {
// Filter to check particular properties of the request or object.
//
// By default `header_name` field refers to the corresponding object's
// `Attribute`. Some Object's header fields can also be accessed by adding
// `$Object:` prefix to the name. Here is the list of fields available via
// this prefix:
// By default `key` field refers to the corresponding object's `Attribute`.
// Some Object's header fields can also be accessed by adding `$Object:`
// prefix to the name. Here is the list of fields available via this prefix:
//
// * $Object:version \
// version
@ -128,10 +127,10 @@ message EACLRecord {
MatchType match_type = 2 [json_name = "matchType"];
// Name of the Header to use
string header_name = 3 [json_name="headerName"];
string key = 3 [json_name="key"];
// Expected Header Value or pattern to match
string header_val = 4 [json_name="value"];
string value = 4 [json_name="value"];
}
// List of filters to match and see if rule is applicable

View file

@ -298,7 +298,7 @@ message SearchRequest {
// Filter structure checks if object header field or attribute content
// matches a value.
//
// By default `name` field refers to the corresponding object's `Attribute`.
// By default `key` field refers to the corresponding object's `Attribute`.
// Some Object's header fields can also be accessed by adding `$Object:`
// prefix to the name. Here is the list of fields available via this prefix:
//
@ -338,7 +338,7 @@ message SearchRequest {
MatchType match_type = 1;
// Attribute or Header fields to match
string name = 2;
string key = 2;
// Value to match
string value = 3;