feature/add_mocks #117
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 project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/frostfs-http-gw#117
Loading…
Reference in a new issue
No description provided.
Delete branch "dkirillov/frostfs-http-gw:feature/add_mocks"
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?
4270140663
to7b49e81e0b
7b49e81e0b
to98c43c74a3
WIP: feature/add_mocksto feature/add_mocks@ -0,0 +32,4 @@
}
// Container implements frostfs.FrostFS interface method.
func (x *FrostFS) Container(ctx context.Context, layerPrm handler.PrmContainer) (*container.Container, error) {
We keep parameter definition outside of this package so
FrostFS
interface can be defined without import of this package, right?Right
@ -0,0 +130,4 @@
// }
//
// return res, nil
// }
Unused?
@ -0,0 +227,4 @@
// }
//
// return nil
//}
Unused?
@ -0,0 +351,4 @@
// }
//
// return table, nil
//}
Unused?
@ -0,0 +368,4 @@
return true
}
for _, rec := range table.Records() {
Can we simplify access check somehow so we won't depend on eACL? Maybe we can define a list of
cnr + owner + op + objID
tuples which are allowed and all others are denied?@ -36,2 +35,4 @@
}
// PrmContainer groups parameters of FrostFS.Container operation.
type PrmContainer struct {
What you think about having separate go file for frostfs interface and parameter definitions?
frostfs.go
andfrostfs_mock.go
looks good in my opinion.It isn't so big to move this to separate file I suppose
98c43c74a3
to3741e3b003