Socorro's processor app uses the "processor_class" configuration variable to specify which processor to use. After bug #1386409, we only have two processor classes one of which is a minor subclass of the other which is effectively one processor class. Given that we only have one effective processor class and we don't need to switch back and forth between processor classes via configuration, we don't need the additional "processor_class" configuration variable. We can remove that and change the processor app such that there's only one processor class used (and squash those two processor classes down). This bug covers that work.
This is nice, but I don't think this is blocking any work I'm doing now. Given that, I'm going to make it a P3 for now. If a compelling reason comes up that we should prioritize this higher, we can adjust accordingly.
Priority: -- → P3
Summary: remove processor_class configuration variable from Processor2015 → remove processor_class configuration variable from processor app
We only have one processor class now. However, the way we've got configman and class creation working, it's easier to keep "processor_class" as a config option because then configman can traverse its required config and everything works nicely. If we removed it, we'd have to manually add the required_config and a bunch of things get messy/hard. It's way easier to leave it as is. Given that, I'm going to WONTFIX this.
Status: NEW → RESOLVED
Last Resolved: 2 months ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.