Bug 9969 – client support for multiple origins desired

Bug 9969 - client support for multiple origins desired


Summary:	client support for multiple origins desired

Status:	RESOLVED FIXINSOURCE

Product:	pkg
Component:	api-python
Version:	unspecified
Platform:	ANY/Generic All

Importance:	P3 enhancement (vote)
Target Milestone:	---
Assigned To:	Shawn Walker
QA Contact:	pkg/api-python watcher

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2009-07-10 14:06 UTC by johansen
Modified:	2009-11-17 23:07 UTC (History)
CC List:	1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note

You need to log in before you can comment on or make changes to this bug.

Description johansen 2009-07-10 14:06:02 UTC

The new transport allows support for transport operations from publishers that
have multiple origins; however, the current client framework doesn't allow
users to configure more than one origin per publisher.  This is a RFE to allow
users to configure multiple origins for a publisher.

Comment 1 Shawn Walker 2009-07-10 21:06:22 UTC

*** This bug has been marked as a duplicate of bug 6153 ***

Comment 2 johansen 2009-07-17 15:16:25 UTC

6153 is a bug against the depot.  This is for the pkg clients that use the API.
 With Las Vegas and Prague coming online soon, and the transport work that's
already been done to support this, we should change the client configuration to
support multiple origins.  There shouldn't be any changes to the depot
necessary to support this change.

Comment 3 Shawn Walker 2009-11-13 02:18:47 UTC

Deprecating -O option (will still be accepted silently with same behaviour as
previous).

Adding -g/--add-origin and -G/--remove-origin options.

Comment 4 Shawn Walker 2009-11-17 23:07:44 UTC

Resolved in changeset 1504 / 265a1d6b86bdbf14ee02f166e3a1eb3d019ad6e9.