From f4d30301fd4b7dca4375875aedae59e5c3542a34 Mon Sep 17 00:00:00 2001 From: Alexander Sulfrian Date: Tue, 27 Jan 2015 19:28:02 +0100 Subject: DBSettings: Fix time_zone option. In the documentation, in the 1.3.x version and in django this option is called time_zone (and not timezone). There is no reason to change this. --- src/lib/Bcfg2/DBSettings.py | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'src/lib') diff --git a/src/lib/Bcfg2/DBSettings.py b/src/lib/Bcfg2/DBSettings.py index f5b5d16aa..5a83c25c3 100644 --- a/src/lib/Bcfg2/DBSettings.py +++ b/src/lib/Bcfg2/DBSettings.py @@ -109,7 +109,7 @@ def finalize_django_config(opts=None, silent=False): OPTIONS=opts.reporting_db_opts, SCHEMA=opts.reporting_db_schema) - settings['TIME_ZONE'] = opts.timezone + settings['TIME_ZONE'] = opts.time_zone settings['TEMPLATE_DEBUG'] = settings['DEBUG'] = \ opts.web_debug @@ -261,7 +261,7 @@ class _OptionContainer(object): type=Bcfg2.Options.Types.comma_dict, default=dict()), # Django options Bcfg2.Options.Option( - cf=('reporting', 'timezone'), help='Django timezone'), + cf=('reporting', 'time_zone'), help='Django timezone'), Bcfg2.Options.BooleanOption( cf=('reporting', 'web_debug'), help='Django debug'), Bcfg2.Options.Option( -- cgit v1.2.3-1-g7c22