[#553] authmate: Don't use basic acl #554
No reviewers
TrueCloudLab/storage-services-developers
Labels
No labels
P0
P1
P2
P3
good first issue
Infrastructure
blocked
bug
config
discussion
documentation
duplicate
enhancement
go
help wanted
internal
invalid
kludge
observability
perfomance
question
refactoring
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/frostfs-s3-gw#554
Loading…
Reference in a new issue
No description provided.
Delete branch "dkirillov/frostfs-s3-gw:featue/553-dont_use_basic_acl"
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?
close #553
a45bbe9c14
to4253fc5b90
WIP: [#553] authmate: Don't use basic aclto [#553] authmate: Don't use basic acl@ -47,1 +44,4 @@
type PrmAddContainerPolicyChain struct {
ContainerID cid.ID
Chain chain.Chain
Don't you want to add comments like in other param structs?
Sure
@ -73,0 +84,4 @@
Op: chain.CondStringEquals,
Kind: chain.KindRequest,
Key: native.PropertyKeyActorPublicKey,
Value: hex.EncodeToString(prm.Owner.Bytes()),
Do we need explicit allow rule for container owner? As far as I understand, we can use frostfs-cli to create container and then upload object without additional APEs
Yes, we have to add explicit rule for container owner. We will create AccessBox there and we need access.
@ -138,0 +138,4 @@
// AddContainerPolicyChain implements frostfs.FrostFS interface method.
func (x *FrostFS) AddContainerPolicyChain(ctx context.Context, prm frostfs.PrmAddContainerPolicyChain) error {
var prmAddAPEChain pool.PrmAddAPEChain
prmAddAPEChain.Target = ape.ChainTarget{
According to internal code style, could you remind me, do we prefer such
var
definition or use:=
straight away?Oh, I just extended your branch. I'll fix style
ed4cc417b7
todce34ddb9b
dce34ddb9b
tob1775f9478