Introduce apeSvc
at the same level with aclSvc
#798
Labels
No labels
P0
P1
P2
P3
badger
frostfs-adm
frostfs-cli
frostfs-ir
frostfs-lens
frostfs-node
good first issue
triage
Infrastructure
blocked
bug
config
discussion
documentation
duplicate
enhancement
go
help wanted
internal
invalid
kludge
observability
perfomance
question
refactoring
wontfix
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/frostfs-node#798
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The PR #770 has introduced the usage of the access policy engine for
Object.Put
method infrostfs-node
.It's incorrect that
apeChecker
is the part of ACL service - it is a temporary solution.It is suggested to implement the pair for
aclSvc
-apeSvc
inpkg/services/object/ape/v2
.Please, note, that common service uses
aclSvc
for its nextHandler and it needs the second handler for a while (after all methods start using only APE checking the first handler will be removed)apeSvc
along withaclSvc
cmd/frostfs-node/object.go
commonSvc
commonSvc
should useapeSvc
middleware forPut
methodI think we should replace or rename acl service instead. The goal of APE is to check access rules, acl service is exactly about that.
The issue won't be solved: we don't need to create new service (check the comment above)