Working with the eACL rule target apart from the protocol #267

New issue

Closed

opened 2025-12-28 17:36:47 +00:00 by sami · 0 comments

sami commented

2025-12-28 17:36:47 +00:00

Owner

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

Originally assigned to: @alexvanin on GitHub.

I've noticed next statement in ACL code:
nspcc-dev/neofs-s3-gw@1012a3c6a4/api/handler/acl.go (L820-L824)

According to this, handler expects that both fields can be set in the message.

However, protocol requires (maybe not detailed enough) exactly one field to be set. Am I missing something? What can we do to follow the protocol?

Originally created by @cthulhu-rider on GitHub (Jun 24, 2022). Originally assigned to: @alexvanin on GitHub. I've noticed next statement in ACL code: https://github.com/nspcc-dev/neofs-s3-gw/blob/1012a3c6a418183bdf75d50b30f0bdc6260977ec/api/handler/acl.go#L820-L824 According to this, handler expects that both fields can be set in the [message](https://github.com/nspcc-dev/neofs-api/blob/10f18e4b69ec79991b1a2b83e212d99203f3ee1a/acl/types.proto#L150-L158). However, protocol requires (maybe not detailed enough) exactly one field to be set. Am I missing something? What can we do to follow the protocol?