Story #3912
closed
As a user, I can specify the file manifest name on the remote when syncing and publishing a repository
Status:
CLOSED - CURRENTRELEASE
Description
Currently, we require users to specify the full url to the PULP_MANIFEST file. This is a bit at odds with how Pulp 2 and other plugins work so instead, we'd like to add a separate field in which users can specify the filename of the remote manifest.
- Related to Story #3913: As a user I can specify the manifest filename when publishing a repo version added
- Status changed from NEW to ASSIGNED
- Assignee set to vdusek
- Subject changed from As a user, I can specify the file manifest name on the remote when syncing a repository to As a user, I can specify the file manifest name on the remote when syncing and publishing a repository
Forgot to mention that we need to update the publish code too in a similar way.
- Status changed from ASSIGNED to POST
- Status changed from POST to MODIFIED
- % Done changed from 0 to 100
- Related to Issue #4000: Tests in master are failing due to a change in pulp_file added
- Related to Issue #4017: Remove the manifest field on remote added
- Sprint/Milestone set to 0.1.0
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Also available in: Atom
PDF
.
Allow custom name of the manifest when syncing and publishing
When creating a remote user can specify his own name of the manifest. As a path to it will be used url/manifest. For example: $ http POST .../remotes/file/ name=rem1 url=https://repos.fedorapeople.org/pulp/pulp/demo_repos/test_file_repo/ manifest=PULP_MANIFEST
Same situation when creating a publisher. For example: $ http POST .../publishers/file/ name=publisher1 manifest=my_manifest.csv
closes #3912, #3913 https://pulp.plan.io/issues/3912 https://pulp.plan.io/issues/3913