Project

Profile

Help

Maintenance. Planio will be undergoing a scheduled maintenance this weekend. Between Saturday, July 24 at 9:00 UTC and Sunday, July 25, 22:00 UTC your account might observe occasional downtimes which may last up to several minutes in some cases.

Story #9099

task created_resources provides hrefs, but no guidance on how to determine the type from the href

Added by jsherril@redhat.com 7 days ago. Updated 3 days ago.

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

0%

Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Documentation, Katello
Sprint:
Quarter:

Description

Currently an rpm sync task with mirror=true provides mutliple types of created_resources, a version_href and a publication_href.

It is left up to the user to figure out how to map an href to a particular object. This is made more difficult when you consider that we'd want code to detect this generically across all content types without having to code for each one.

Its easy to write a regex that would match version href for example:

   /.*\/versions\/.*/

However this would match other href's as well, we could expect an id:

/.*\/versions\/\d*\//

but this depends on them being numerical, is that okay? Will that break in the future?

It would be helpful to have some set of regex's or some guidance on how to determine if a given href is a:

  • repository
  • version
  • publication
  • distribution

across all content types, with a commitment that (at least for pulp3), that these regexs or guidance will not change.

This could be verified with a unit_test at the code level.

History

#1 Updated by dkliban@redhat.com 3 days ago

  • Tracker changed from Issue to Story
  • % Done set to 0
  • Severity deleted (2. Medium)
  • Triaged deleted (No)

#2 Updated by dkliban@redhat.com 3 days ago

  • Tags Documentation added

Please register to edit this issue

Also available in: Atom PDF