frostfs-node/cmd
Evgenii Stratonikov 2d954dfacf
All checks were successful
DCO action / DCO (pull_request) Successful in 2m34s
Build / Build Components (1.20) (pull_request) Successful in 4m15s
Build / Build Components (1.21) (pull_request) Successful in 4m14s
Vulncheck / Vulncheck (pull_request) Successful in 3m41s
Tests and linters / Staticcheck (pull_request) Successful in 5m43s
Tests and linters / Lint (pull_request) Successful in 6m8s
Tests and linters / Tests (1.21) (pull_request) Successful in 6m8s
Tests and linters / Tests (1.20) (pull_request) Successful in 7m52s
Tests and linters / Tests with -race (pull_request) Successful in 7m50s
[#793] adm: Always use committee as FrostFS ID owner
Committee should be able to authorize everything, there are no other
usecases for the frostfs-adm currently. Also, it somewhat eases
configuration, because committee hash depends on the protocol
configuration.

Signed-off-by: Evgenii Stratonikov <e.stratonikov@yadro.com>
2023-11-13 15:26:20 +03:00
..
frostfs-adm [#793] adm: Always use committee as FrostFS ID owner 2023-11-13 15:26:20 +03:00
frostfs-cli [#796] cli: Fix object nodes command 2023-11-09 13:41:36 +03:00
frostfs-ir [#772] node: Apply gofumpt 2023-10-31 17:03:03 +03:00
frostfs-lens [#772] node: Apply gofumpt 2023-10-31 17:03:03 +03:00
frostfs-node [#770] object: Introduce ape chain checker for object svc 2023-11-08 13:34:03 +00:00
internal/common [#772] node: Apply gofumpt 2023-10-31 17:03:03 +03:00