yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #18209
[Bug 1323975] Re: do not use default=None for config options
** Changed in: barbican
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1323975
Title:
do not use default=None for config options
Status in OpenStack Key Management (Barbican):
Fix Released
Status in OpenStack Telemetry (Ceilometer):
Fix Released
Status in Cinder:
In Progress
Status in OpenStack Image Registry and Delivery Service (Glance):
Fix Released
Status in Orchestration API (Heat):
Fix Released
Status in OpenStack Bare Metal Provisioning Service (Ironic):
Fix Committed
Status in OpenStack Identity (Keystone):
Fix Released
Status in MagnetoDB - key-value storage service for OpenStack:
New
Status in OpenStack Message Queuing Service (Marconi):
Fix Released
Status in OpenStack Neutron (virtual network service):
Fix Released
Status in OpenStack Compute (Nova):
Incomplete
Status in Oslo - a Library of Common OpenStack Code:
Fix Released
Status in Messaging API for OpenStack:
Fix Released
Status in OpenStack Data Processing (Sahara, ex. Savanna):
Fix Released
Status in Openstack Database (Trove):
In Progress
Bug description:
In the cfg module default=None is set as the default value. It's not
necessary to set it again when defining config options.
To manage notifications about this bug go to:
https://bugs.launchpad.net/barbican/+bug/1323975/+subscriptions
References