As a user, I want to trigger a "background sync" for repositories in content view versions.
The use case:
1. Sync "RHEL 7Server" repo in on-demand download policy
2. Create a CV w/ filters to reduce packages from 14000 to 4
3. Publish CV to get CVV 1.0
4. Attempting to export CVV 1.0 will error since the packages have not yet been downloaded
I would like to be able to force pulp to download the 4 packages in that repo. This is equivalent to a "background" download policy in results.
I am not defining how this is implemented but would like to see it either at the repository level or at the content view version level. Something like this
hammer content-view version synchronize --id 12