Skip to content
This repository has been archived by the owner on Aug 2, 2022. It is now read-only.

Can't use subcommands (ex: wallet) as permission when pushing action with cleos #8947

Closed
DenisCarriere opened this issue Apr 15, 2020 · 3 comments
Assignees

Comments

@DenisCarriere
Copy link
Contributor

Issue using account names that are the same as commands or subcommands (ex: -p wallet) as permission when pushing action with cleos

Seems like there's a few command & subcommands which can't be used as account permission.

  • -p wallet
  • -p create
  • -p convert
  • -p set
  • -p get
  • -p transfer
  • -p net
  • -p sign
  • -p multisig
  • -p wrap
  • -p system
$ cleos push action hello hi '["foobar"]' -p wallet

Error message

ERROR: RequiredError: Subcommand required
Interact with local wallet
Usage: cleos wallet SUBCOMMAND

Subcommands:
  create                      Create a new wallet locally
  open                        Open an existing wallet
  lock                        Lock wallet
  lock_all                    Lock all unlocked wallets
  unlock                      Unlock wallet
  import                      Import private key into wallet
  remove_key                  Remove key from wallet
  create_key                  Create private key within wallet
  list                        List opened wallets, * = unlocked
  keys                        List of public keys from all unlocked wallets.
  private_keys                List of private keys from an unlocked wallet in wif or PVT_R1 format.
  stop                        Stop keosd.
revl added a commit that referenced this issue Apr 16, 2020
This commit fixes #8947 by upgrading CLI11 to the latest version.
revl added a commit that referenced this issue Apr 27, 2020
This commit fixes #8947 by upgrading CLI11 to the latest version.
@revl revl mentioned this issue Apr 27, 2020
3 tasks
revl added a commit that referenced this issue Apr 27, 2020
This commit fixes #8947 by upgrading CLI11 to the latest version.
@revl
Copy link
Contributor

revl commented Apr 28, 2020

The fix is in develop. It may or may not land in 2.0.

@revl revl closed this as completed Apr 28, 2020
@revl
Copy link
Contributor

revl commented Apr 28, 2020

It was merged into 2.0 as well.

@DenisCarriere
Copy link
Contributor Author

Great thanks 🙏

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants