Project

Profile

Help

Story #1892

Find or create XSD for every XML file we deal with

Added by jcline@redhat.com over 5 years ago. Updated over 2 years ago.

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

0%

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

Description

As everyone is probably aware, the XML namespace used for yum repositories (http://linux.duke.edu/metadata/) is dead and gone. This is sad.

We deal with the yum metadata XML in this plugin, so we should have an XML Schema Definition (XSD) for the XML we accept. These XSD have probably already been written by someone, but we don't know where they are. We should find (or, as a last resort, write) an XSD for each file type. We should use them to validate incoming XML. This provides two benefits:

1) We know when upstream metadata doesn't match our expectations.
2) We document our expectations of the metadata format. This is helpful when we encounter a problem so people can either determine we are not expected the "correct" XML, or they are creating "incorrect" XML.


Checklist

History

#1 Updated by bmbouter over 2 years ago

  • Status changed from NEW to CLOSED - WONTFIX

Pulp 2 is approaching maintenance mode, and this Pulp 2 ticket is not being actively worked on. As such, it is being closed as WONTFIX. Pulp 2 is still accepting contributions though, so if you want to contribute a fix for this ticket, please reopen or comment on it. If you don't have permissions to reopen this ticket, or you want to discuss an issue, please reach out via the developer mailing list.

#2 Updated by bmbouter over 2 years ago

  • Tags Pulp 2 added

Please register to edit this issue

Also available in: Atom PDF