Summary
With how many pulp environments there can be, content units can easily fall out of sync between them. It doesn't appear that copy_content() has a way of setting a destination environment to complement the to_repository parameter. Adding such a parameter would drastically simplify content synchronization.
Issue Type
Current behavior
There doesn't appear to be a built-in way to synchronize content units between pulp environments when using copy_content().
Desired behavior
copy_content() should have ideally have an optional parameter for a destination environment, such as client.copy_content(TARGET_REPO, DESTINATION_REPO, to_client=Client(url=DEST_URL, cert=CERT))
Use case
A stage pulp environment is occasionally used for comparing content against prod, however even when running pub to push a compose and update pulp, the packages in the stage pulp environment aren't guaranteed to be 1:1 with prod. Copying pulp content units directly between environments may be more reliable.
Additional Information
Summary
With how many pulp environments there can be, content units can easily fall out of sync between them. It doesn't appear that
copy_content()has a way of setting a destination environment to complement theto_repositoryparameter. Adding such a parameter would drastically simplify content synchronization.Issue Type
Current behavior
There doesn't appear to be a built-in way to synchronize content units between pulp environments when using
copy_content().Desired behavior
copy_content()should have ideally have an optional parameter for a destination environment, such asclient.copy_content(TARGET_REPO, DESTINATION_REPO, to_client=Client(url=DEST_URL, cert=CERT))Use case
A
stagepulp environment is occasionally used for comparing content againstprod, however even when runningpubto push a compose and update pulp, the packages in thestagepulp environment aren't guaranteed to be 1:1 with prod. Copying pulp content units directly between environments may be more reliable.Additional Information