From 4df8423bdfde1c3cf65af3c84d0035aaece363e0 Mon Sep 17 00:00:00 2001 From: Yves-Gwenael Bourhis Date: Wed, 13 Mar 2019 18:28:15 +0100 Subject: [PATCH] Allow entry points to override existing resources Third party modules may want to modify existing resources behaviours. To allow overriding existing resources, entry point modules need to be loaded first. It is not an issue to load them first since we sort the classes afterwards. Change-Id: I92999d98df249649b79b13ca2be2691efdde737f --- ospurge/utils.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ospurge/utils.py b/ospurge/utils.py index b9f4dda..f5edcb8 100644 --- a/ospurge/utils.py +++ b/ospurge/utils.py @@ -54,8 +54,8 @@ def get_resource_classes(resources=None): This way we can easily extend OSPurge by just adding a new file in the `resources` dir or a package with `ENTRY_POINTS_NAME` entry point. """ - load_ospurge_resource_modules() load_entry_points_modules() + load_ospurge_resource_modules() all_classes = base.ServiceResource.__subclasses__()