From 9e1f176d314dd629fb51a3d3c2f14562f88a6a20 Mon Sep 17 00:00:00 2001 From: Sol Jerome Date: Sat, 27 Jul 2013 17:34:26 -0500 Subject: Yum: Add back disableMetaData method The documentation string for this method led me to believe that we could remove it. However, after looking closely, it appears as though disableMetaData is still undefined for Collection objects in __init__.py. Signed-off-by: Sol Jerome --- src/lib/Bcfg2/Server/Plugins/Packages/Yum.py | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) (limited to 'src/lib/Bcfg2/Server/Plugins/Packages') diff --git a/src/lib/Bcfg2/Server/Plugins/Packages/Yum.py b/src/lib/Bcfg2/Server/Plugins/Packages/Yum.py index aee16eee1..453198ac8 100644 --- a/src/lib/Bcfg2/Server/Plugins/Packages/Yum.py +++ b/src/lib/Bcfg2/Server/Plugins/Packages/Yum.py @@ -322,6 +322,26 @@ class YumCollection(Collection): (certdir, err)) self.pulp_cert_set = PulpCertificateSet(certdir) + @property + def disableMetaData(self): + """ Report whether or not metadata processing is enabled. + This duplicates code in Packages/__init__.py, and can probably + be removed in Bcfg2 1.4 when we have a module-level setup + object. """ + if self.setup is None: + return True + try: + return not self.setup.cfp.getboolean("packages", "resolver") + except (ConfigParser.NoSectionError, ConfigParser.NoOptionError): + return False + except ValueError: + # for historical reasons we also accept "enabled" and + # "disabled" + return self.setup.cfp.get( + "packages", + "metadata", + default="enabled").lower() == "disabled" + @property def __package_groups__(self): return True -- cgit v1.2.3-1-g7c22