You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
NeoFS CLI help command suggests to pass WIF, hex or wallet file to get private key.
$ neofs-cli --help
...
Flags:
...
-k, --key --key new private key in hex, WIF, NEP-2 or filepath (use --key new to generate key for request)
However after #562 it is not true. I suggest to keep support of WIF or hex encoded files, but we can do that in different arguments (the same way as NEOFS_KEY and NEOFS_WALLET are the same arguments in storage node config).
The text was updated successfully, but these errors were encountered:
Currently have static priority of what key is used irregardless of
whether a flag was provided via CLI or in config. This makes it
impossible to override some of the config settings. While we could try
to check if the key is provided by CLI by binding CLI flag under to
viper under a different name the same problem would occur for config/environment
variables. Fixing all of this with current set of keys is too complicate.
In this commit we revert changes from nspcc-dev#610 and use a single flag for all types of keys.
Signed-off-by: Evgenii Stratonikov <evgeniy@nspcc.ru>
NeoFS CLI help command suggests to pass WIF, hex or wallet file to get private key.
However after #562 it is not true. I suggest to keep support of WIF or hex encoded files, but we can do that in different arguments (the same way as NEOFS_KEY and NEOFS_WALLET are the same arguments in storage node config).
The text was updated successfully, but these errors were encountered: