Actions
Story #3913
closed
As a user I can specify the manifest filename when publishing a repo version
Start date:
Due date:
% Done:
100%
Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:
Description
Currently, the filename is hardcoded as PULP_MANIFEST. Allow users to specify a filename on the file publisher to be used when publishing. Optimally, the default should be the same as in #3912 (ie manifest.csv).
Related issues
Updated by daviddavis over 6 years ago
- Related to Story #3912: As a user, I can specify the file manifest name on the remote when syncing and publishing a repository added
Updated by vdusek over 6 years ago
- Status changed from NEW to ASSIGNED
- Assignee set to vdusek
Updated by vdusek over 6 years ago
- Status changed from ASSIGNED to POST
Added by vdusek over 6 years ago
Updated by vdusek over 6 years ago
- Status changed from POST to MODIFIED
- % Done changed from 0 to 100
Applied in changeset abd47ce67ba9faf1e1abc4288b2f273dc6a38cc5.
Updated by daviddavis over 6 years ago
- Related to Issue #4000: Tests in master are failing due to a change in pulp_file added
Updated by daviddavis over 6 years ago
- Related to Issue #4017: Remove the manifest field on remote added
Updated by bmbouter about 5 years ago
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Actions
.
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