[autotest] Require lock reason to lock device
When locking a device, a locking reason now must be provided.
This applies to both adding a new device, and modifying an
existing device from both the web frontend and the atest
command-line tool.
BUG=chromium:336805
DEPLOY=migrate
TEST=Tested adding locked/unlocked devices and locking/unlocking devices
from both the web frontend and using the 'atest host ...' command-line tools.
Change-Id: I3a8cd8891a2999f026dd709ae8a79e2b8cbc251a
Reviewed-on: https://chromium-review.googlesource.com/267595
Tested-by: Matthew Sartori <[email protected]>
Reviewed-by: Dan Shi <[email protected]>
Commit-Queue: Matthew Sartori <[email protected]>
diff --git a/cli/topic_common.py b/cli/topic_common.py
index b191e6c..7762a75 100644
--- a/cli/topic_common.py
+++ b/cli/topic_common.py
@@ -74,6 +74,7 @@
'locked': 'Locked',
'locked_by': 'Locked by',
'lock_time': 'Locked time',
+ 'lock_reason': 'Lock Reason',
'labels': 'Labels',
'description': 'Description',
'hosts': 'Hosts',
