atsign-foundation/at_tools

bug (at_cli): update verb ignores -p and defaults to public!

Opened this issue · 1 comments

Describe the bug


trunk on  trunk [!?]
N ➜ at_cli -a -f ~/.atsign/keys/@snooker25_key.atKeys --atsign @snooker25 -k test1.testingdemo -p false -v update --value "foobar"
146

trunk on  trunk [!?]
I ➜ at_cli -a -f ~/.atsign/keys/@snooker25_key.atKeys --atsign @snooker25 -k test2.testingdemo -p true -v update --value "foobar"
147

trunk on  trunk [!?]
I ➜ at_cli -a -f ~/.atsign/keys/@snooker25_key.atKeys --atsign @snooker25 -v scan \
-r ".testingdemo"
["public:test1.testingdemo@snooker25","public:test2.testingdemo@snooker25"]

Steps to reproduce

  1. First I '...'
  2. Then I '...'
  3. And then '...'

Expected behavior

Private values stay private!

Screenshots

No response

Smartphones

  • Device: [e.g. iPhone6]
  • OS: [e.g. iOS8.1]
  • Browser [e.g. stock browser, safari]
  • Version [e.g. 22]

Were you using an atApplication when the bug was found?

No response

Additional context

No response

nvm! -p is a flag now, we need to update docs to reflect this!