Config: no need to set default=None
By default oslo.cfg sets the default value as None. There is no need to explicitly do this. TrivialFix Change-Id: I8ba1e1d96a40f5563fba7e22af9bf02b9a7b13fa
This commit is contained in:
parent
c31d2fca1c
commit
9c460e28ac
|
@ -24,7 +24,6 @@ release and will be removed in the O release.
|
|||
admin_token = cfg.StrOpt(
|
||||
'admin_token',
|
||||
secret=True,
|
||||
default=None,
|
||||
help=utils.fmt("""
|
||||
A "shared secret" that can be used to bootstrap Keystone. This "token" does not
|
||||
represent a user, and carries no explicit authorization. If set to `None`, the
|
||||
|
|
|
@ -66,7 +66,6 @@ value to 0 disables this feature.
|
|||
|
||||
password_regex = cfg.StrOpt(
|
||||
'password_regex',
|
||||
default=None,
|
||||
help=utils.fmt("""
|
||||
Regular expression used to validate password strength requirements. Setting the
|
||||
value to None disables this feature. The following is an example of a pattern
|
||||
|
|
Loading…
Reference in New Issue