Ability to reference a publisher content library from another vCenter

[donovanmuller]

Is your feature request related to a problem? Please describe.

If you have two vCenters, for example, vx-A and vx-B, with content libraries set up as follows:

• On vx-A: Content library A-publisher configured as a publisher
• On vx-A: Content library A-subscriber-A configured as a subscriber to A-publisher
• On vx-B: Content library B-subscriber-A configured as a subscriber to A-publisher

In the vCenter UI, it is possible to configure things as above. Beyond adding Subscriptions to subscriber libraries in the same vCenter (A-subscriber-A), you can add a Subscription to a subscriber content library in another vCenter (vx-B) by selecting vx-A and then the corresponding publisher library, A-publisher.

However, I cannot replicate this with GOVC. The problem is that when using the vx-B host details, the publisher library (A-publisher) is not visible and, therefore, not usable when executing a command like the below:

$ env
GOVC_URL=vx-B
...

$ govc library.subscriber.create -cluster Management -folder ... -pool ... -net ... A-publisher B-subscriber-A
govc: "path"="A-publisher" matches 0 items

$ govc library.ls
B-subscriber-A

Describe the solution you'd like

A way to reference the content library (A-publisher) in another vCenter when creating subscriptions, to match the functionality available via the UI.

Describe alternatives you've considered
None

Additional context
None

[github-actions]

Howdy 🖐   donovanmuller ! Thank you for your interest in this project. We value your feedback and will respond soon.

If you want to contribute to this project, please make yourself familiar with the CONTRIBUTION guidelines.

[github-actions]

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Mark as fresh by adding the comment /remove-lifecycle stale.

[donovanmuller]

/remove-lifecycle stale