Monasca

monasca-agent Config not behaving as a singleton

Bug #1485672 reported by Alistair Coles
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Monasca
Fix Committed
Undecided
Joe Keen

Bug Description

monasca_agent/common/config.py.Config used to be a singleton but no longer behaves as a singleton since (I believe) this change:

Fixing flake8 errors now that tox is working again Change-Id: Id34991711c57f20922f003928008143032723af3

Allan G (greental)
Changed in monasca:
assignee: nobody → Joe Keen (jkeen)
status: New → Triaged
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to monasca-agent (master)

Reviewed: https://review.openstack.org/213774
Committed: https://git.openstack.org/cgit/stackforge/monasca-agent/commit/?id=13f129d56c20712e8cfec4b81761ca322b1b1ffb
Submitter: Jenkins
Branch: master

commit 13f129d56c20712e8cfec4b81761ca322b1b1ffb
Author: Alistair Coles <email address hidden>
Date: Mon Aug 17 17:09:52 2015 +0100

    Make the Config class be a singleton

    Fixes the Config class so that is behaves as a singleton.
    six.add_metaclass should be used as a decorator on the class.

    Add a unit test to verify correct behavior.

    Closes-Bug: 1485672
    Change-Id: I3535704ec399a303a8178c0c6803b89682ca096f

Changed in monasca:
status: Triaged → Fix Committed
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.