Bug 796693

Summary:	Feature: Ability to apply dependencies/sync in order.
Product:	[Retired] Pulp	Reporter:	Ashley Penney <apenney>
Component:	user-experience	Assignee:	Todd Sanders <tsanders>
Status:	CLOSED NOTABUG	QA Contact:	Preethi Thomas <pthomas>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	mhrivnak, skarmark, tsanders
Target Milestone:	---	Keywords:	FutureFeature, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-09-27 14:43:08 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Ashley Penney 2012-02-23 13:56:48 UTC

I would love the ability to manage chained sets of repositories better.

Right now I have (for example):

ops-live-rhel-6-x86_64-puppet
ops-unstable-rhel6-x86_64-puppet
ops-stable-rhel6-x86_64-puppet

(I also have rhel5, rhel5 i386, etc.)

An emergency fix comes out and I need to sync it to the stable repos.  I currently have to manually do a sync on every single one of these in order and it's unbearable.  I'd like a way to do this better and I don't want to constrain that solution by making suggestions here.  I was thinking in terms of --recursive to make it follow the chain of cloned resources until it hits one with an external feed and then syncing than and so on until it hits the one you started with, but I'll take anything that makes this less unbearable.

Comment 86 Michael Hrivnak 2013-09-27 14:43:08 UTC

Pulp has changed a lot since this was filed. The current way to do promotion is to copy a package from one repo to another, which is blazing-fast. Please re-open if you think there is still an issue here.