Karbor

Do not use default=None for config options

Bug #1680492 reported by chenying
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Karbor
Fix Released
Undecided
lwanderley

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.

lwanderley (lwanderley)
Changed in karbor:
assignee: nobody → Leticia Wanderley (lwanderley)
Revision history for this message
lwanderley (lwanderley) wrote :

https://review.openstack.org/#/c/454433/

lwanderley (lwanderley)
Changed in karbor:
status: New → Fix Committed
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on karbor (master)

Change abandoned by chenying (<email address hidden>) on branch: master
Review: https://review.openstack.org/454229
Reason: same as this one:https://review.openstack.org/#/c/454433/

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to karbor (master)

Reviewed: https://review.openstack.org/454433
Committed: https://git.openstack.org/cgit/openstack/karbor/commit/?id=45a9de786efbe96a10c1f56fdd1cec41d0f694f7
Submitter: Jenkins
Branch: master

commit 45a9de786efbe96a10c1f56fdd1cec41d0f694f7
Author: Leticia Wanderley <email address hidden>
Date: Thu Apr 6 23:17:04 2017 -0300

    Removing unnecessary config definition

    The configuration module already defines the default value as None
    There's no need to set it again on the configuration options
    definition

    Change-Id: I72cc503c2b24d597f7acecf7b5853a2627775970
    Closes-Bug: #1680492

Changed in karbor:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.