Project

Profile

Help

Issue #4809

closed

Custom Distributions cannot be disabled from being served by the content app

Added by bmbouter over 5 years ago. Updated about 4 years ago.

Status:
CLOSED - WONTFIX
Priority:
Normal
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
Platform Release:
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:

Description

The content app searches for the distribution according to the Master model, BaseDistribution. It has a line like:

BaseDistribution.objects.get(base_path__in=base_paths)

This will include any subclass of BaseDistribution that a plugin writer has configured to be handled by a handler they provide. If that handler doesn't match it will be handled by the default handler which would serve that content as well. This is probably not what the plugin writer wanted.

There should be a way to disable a custom Distribution from serving through the Pulp content app default handler.

Actions #1

Updated by bmbouter over 5 years ago

In thinking about this more I don't think it's something that would actually happen because the url would be matched by the plugin provided handler so it wouldn't reach the default handler.

Actions #2

Updated by amacdona@redhat.com over 5 years ago

  • Triaged changed from No to Yes
Actions #3

Updated by dkliban@redhat.com about 4 years ago

  • Status changed from NEW to CLOSED - WONTFIX

We will not be fixing this until a real use case demands a fix.

Also available in: Atom PDF