Project

Profile

Help

Story #65

As a plugin writer, the platform enforces only one profiler per content_type_id

Added by Anonymous almost 7 years ago. Updated about 1 year ago.

Status:
CLOSED - WONTFIX
Priority:
Normal
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
Quarter:

Description

Currently in platform/src/pulp/plugins/loader/api.py, there is code to ""validate"" importers, but no code to validate profilers.Due to assumptions in the applicability system, it is important for the platform to enforce that there may only be one profiler registered per content_type_id that it supports. For example, only one profiler should be allowed to advertise that it handles RPM content.As part of this story, we can remove the comment from get_profiler_by_type in that module that says, ""this makes the assumption that there is only 1 profiler per type"".

History

#1 Updated by rbarlow almost 7 years ago

  • Project changed from 22 to Pulp

#2 Updated by amacdona@redhat.com about 5 years ago

  • Tags Pulp 3 added

#3 Updated by bmbouter over 2 years ago

  • Tags deleted (Pulp 3)

#4 Updated by ipanova@redhat.com about 1 year ago

  • Status changed from NEW to CLOSED - WONTFIX
  • Tags Pulp 2 added

This is a pulp2 issues, pulp2 is in maintenance mode, only critical bugfixes are accepted

Please register to edit this issue

Also available in: Atom PDF