forked from TrueCloudLab/frostfs-api
Clarify object field usage in some requests' eACL filters
Signed-off-by: Stanislav Bogatyrev <stanislav@nspcc.ru>
This commit is contained in:
parent
47c7452eb2
commit
73ccd17adb
1 changed files with 5 additions and 0 deletions
|
@ -121,6 +121,11 @@ message EACLRecord {
|
||||||
// * $Object:homomorphicHash \
|
// * $Object:homomorphicHash \
|
||||||
// homomorphic_hash
|
// homomorphic_hash
|
||||||
//
|
//
|
||||||
|
// Please note, that if request or response does not have object's headers or
|
||||||
|
// full object (Range, RangeHash, Search, Delete), it will not be possible to
|
||||||
|
// filter by object header fields or user attributes. From the well-known list
|
||||||
|
// only `$Object:objectID` and `$Object:containerID` will be available, as
|
||||||
|
// it's possible to take that information from the requested address.
|
||||||
message Filter {
|
message Filter {
|
||||||
// Define if Object or Request header will be used
|
// Define if Object or Request header will be used
|
||||||
HeaderType header_type = 1 [json_name = "headerType"];
|
HeaderType header_type = 1 [json_name = "headerType"];
|
||||||
|
|
Loading…
Reference in a new issue