[#42] Fix using separate container for lifecycles #442
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
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/frostfs-s3-gw#442
Loading…
Reference in a new issue
No description provided.
Delete branch "mbiryukova/frostfs-s3-gw:feature/lifecycle_container"
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?
Signed-off-by: Marina Biryukova m.biryukova@yadro.com
This is going to be quite nasty rebase after tree split PR. But it is what it is.
@ -821,0 +830,4 @@
if !lifecycleObj.Container().Equals(p.BktInfo.CID) {
n.deleteLifecycleObject(ctx, p.BktInfo, lifecycleObj)
}
This order looks a bit weird at the first glance. Is there a reason to get
lifecycleObj
before deleting container?If we try to get
lifecycleObj
after deletion, we'll get an error that container not found5863af4a26
to2abb9b38cc
@ -146,0 +143,4 @@
prmAuth.PrivateKey = &n.gateKey.PrivateKey
}
if err = n.objectDeleteWithAuth(ctx, lifecycleBkt, obj.Object(), prmAuth); err != nil {
It seems we can reuse
deleteLifecycleObject
if make it more general (let it return error)Log and return?
I wouldn't log inside it, but then we have to log in more other places so I don't know what is better.
Let's leave everything as is.