Actions
Issue #812
closed
/v2/repositories/<repo_id>/actions/resolve_dependencies/ should be removed
Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
Platform Release:
2.7.0
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
Quarter:
Description
The API endpoint /v2/repositories/<repo_id>/actions/resolve_dependencies/ is unused, broken, undocumented, and should be removed.
Resolving dependencies is a plugin specific task, but has not been implemented by any of our plugins and is completely undocumented. Additionally, we believe that resolving dependencies falls outside of the scope of what pulp should do. The conclusion is that this endpoint should be removed.
I have already done this as a part of the django port, this bug is to track and document the change.
Related issues
Added by Austin Macdonald about 9 years ago
Added by Austin Macdonald about 9 years ago
Updated by Anonymous about 9 years ago
- Status changed from ASSIGNED to MODIFIED
- % Done changed from 0 to 100
Applied in changeset pulp|089b0f0e6cd0d10063b354af59df0c4dde9e2fac.
Updated by rbarlow about 9 years ago
- Platform Release changed from master to 2.7.0
Updated by dkliban@redhat.com almost 9 years ago
- Status changed from MODIFIED to 5
Updated by amacdona@redhat.com almost 9 years ago
- Related to Issue #806: API call to resolve repo dependencies with bad criteria returns unhelpful exception added
Updated by pthomas@redhat.com almost 9 years ago
- Status changed from 5 to 6
verified
[root@mgmt4 ~]# curl -X POST -k -u admin:admin "https://localhost/pulp/api/v2/repositories/test/actions/resolve_dependencies/"<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>500 Internal Server Error</title>
</head><body>
<h1>Internal Server Error</h1>
<p>The server encountered an internal error or
misconfiguration and was unable to complete
your request.</p>
<p>Please contact the server administrator,
root@localhost and inform them of the time the error occurred,
and anything you might have done that may have
caused the error.</p>
<p>More information about this error may be available
in the server error log.</p>
<hr>
<address>Apache/2.2.15 (Red Hat) Server at localhost Port 443</address>
</body></html>
Jul 15 14:24:46 mgmt4 pulp: django.request:ERROR: (14266-91680) raise TemplateDoesNotExist(name)
Jul 15 14:24:46 mgmt4 pulp: django.request:ERROR: (14266-91680) TemplateDoesNotExist: 404.html
Updated by amacdona@redhat.com over 8 years ago
- Status changed from 6 to CLOSED - CURRENTRELEASE
Actions
.
django conversion - repositories
closes #707 closes #749 closes #756 closes #804 closes #805 closes #812