[#244] Remove --local-dump from frostfs-adm config #505
No reviewers
Labels
No labels
P0
P1
P2
P3
badger
frostfs-adm
frostfs-cli
frostfs-ir
frostfs-lens
frostfs-node
good first issue
triage
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-node#505
Loading…
Reference in a new issue
No description provided.
Delete branch "ale64bit/frostfs-node:fix/244-remove-local-dump-config"
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: Alejandro Lopez a.lopez@yadro.com
Closes #244
I tried using it in dev-env but it seems we still are using rpc-endpoint:
[#244] Remove --local-dump from frostfs-adm configto WIP: [#244] Remove --local-dump from frostfs-adm config6b6e826159
to0ccf72f58c
WIP: [#244] Remove --local-dump from frostfs-adm configto [#244] Remove --local-dump from frostfs-adm config@ -215,3 +213,1 @@
return nil, fmt.Errorf("`%s` and `%s` flags are mutually exclusive", endpointFlag, localDumpFlag)
}
c, err = newLocalClient(cmd, v, wallets)
if f := cmd.Flags().Lookup(localDumpFlag); f != nil && f.Changed {
Why not
cmd.Flags().GetString()
?Also, can we still provide both via CLI? The error should occur (we only allow conflict if rpc-endpoint is provided via the configuration).
Because it forces me to introduce an
err
variable which shadows the external one and it's not different from this anyway.done
0ccf72f58c
to638e9576d1