[autotest] Change production setting's default to False
puppet CL was merged and prod was updated. This CL will force the option to
default to False, thus any local scheduler run targeting remote database will
fail without --production option.
BUG=chromium:409091
TEST=local scheduler test
DEPLOY=scheduler,host_scheduler
Change-Id: Id49a4d8080534a16cb827038d6121d3c94a75dfe
Reviewed-on: https://chromium-review.googlesource.com/217373
Tested-by: Dan Shi <dshi@chromium.org>
Reviewed-by: Prashanth B <beeps@chromium.org>
Commit-Queue: Dan Shi <dshi@chromium.org>
diff --git a/scheduler/monitor_db.py b/scheduler/monitor_db.py
index 4d42b82..6a2fee9 100755
--- a/scheduler/monitor_db.py
+++ b/scheduler/monitor_db.py
@@ -117,15 +117,13 @@
parser.add_option('--test', help='Indicate that scheduler is under ' +
'test and should use dummy autoserv and no parsing',
action='store_true')
- # TODO(dshi): change default to False after puppet change is landed in
- # production.
parser.add_option('--production',
help=('Indicate that scheduler is running in production '
'environment and it can use database that is not '
'hosted in localhost. If it is set to False, '
'scheduler will fail if database is not in '
'localhost.'),
- action='store_true', default=True)
+ action='store_true', default=False)
(options, args) = parser.parse_args()
if len(args) != 1:
parser.print_usage()