[#326] Automation of PATCH method in GRPC #326
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
4 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/frostfs-testlib#326
Loading…
Reference in a new issue
No description provided.
Delete branch "Kiriruso/frostfs-testlib:feature-patch-testsuite-part-one"
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: Kirill Sosnovskikh k.sosnovskikh@yadro.com
7e0eefcba8
to6200577af5
[#326] Automation of PATCH in GRPCto [#326] Automation of PATCH method in GRPC@ -284,2 +284,4 @@
@reporter.step("Patch object {cid}/{oid} from {endpoint}")
def patch_object(
why did you add patch method to folder steps?
I think it is enough to use this method via FrostfsCli implementations
Added based on the surrounding code, in principle, this function is not required to test the functionality. I can remove this.
please remove it, we try to use in everywhere
CliClientWrapper
for frostfs-cli operations6200577af5
toc47e0ea7d0
c47e0ea7d0
to1e8e983d05
New commits pushed, approval review dismissed automatically according to repository settings