Signer Keyring

[daniel-farina]

I'm trying to specify the signer-keyring in this case test with no luck.

beaker wasm deploy counter --signer-account test --signer-keyring test- --network testnet --no-wasm-opt --raw '{ "count": 0 }' --label 'My first Beaker Contract'

Output:

The argument '--signer-account <SIGNER_ACCOUNT>' cannot be used with '--signer-keyring <SIGNER_KEYRING>'

My logic is I'm trying to use an account called test on my test keyring-backend?

I also fixed some descriptions via #82

[daniel-farina]

ok after further testing I guess the idea is to use only -signer-keyring test which will default to the os keyring with is managed via the beaker beaker key command.

I think this is a bit different from what most people are used to where they usually can specify the account name and the keyring-backend.

How can can you for example specify the account name and on the os keyring?

Thank you for any clarifications, ideally we follow something similar to:

https://docs.cosmos.network/master/run-node/keyring.html

[iboss-ptk]

I do agree that the --signer-x interface could be improve, will relook at the overall of signer semantics.

Specifically for this case, keyring crate only support os backend, which can be referenced via --signer-keyring. For --signer-account is similar to test backend. For other backends, I don't see a clear use case so I'm not implementing it, unless you have different opinion.