Story #3234
closed
Story #3209: As a user, I have Repository Versions
As an authenticated user, I can create a new version by adding or removing content to the latest version.
100%
Description
- I can follow the progress. (adding/removing are asynchronous).
- can add and remove together in a single call
A POST to the api/v3/repositories/123/versions/ should accept 2 POST body parameters: add_content_units, remove_content_units. A task should be spawned to create a new repository version. The repository version starts with the content from previous version, if any, and then adds units from add_content_units, then removes content from remove_content_units.
Updated by daviddavis over 6 years ago
- Blocked by Story #3173: As a plugin author, I have documentation on how to implement a sync operation for my importer added
Updated by dkliban@redhat.com over 6 years ago
- Groomed changed from No to Yes
- Sprint Candidate changed from No to Yes
Updated by amacdona@redhat.com over 6 years ago
- Description updated (diff)
Updated based on RepositoryVersions discussion. The initial implementation no longer includes an importer parameter, the deployment of the sync task be the responsibility of the Detail Importer Viewset rather than the RepositoryVersionsViewset.
Updated by amacdona@redhat.com over 6 years ago
- Blocked by deleted (Story #3173: As a plugin author, I have documentation on how to implement a sync operation for my importer)
Updated by jortel@redhat.com over 6 years ago
Let's drop the "units" suffix and use add_content and remove_content.
Updated by amacdona@redhat.com over 6 years ago
@jortel, -1 for `add_content` and `remove_content` since "content" can be singular or plural. In this context it will be plural, but the model already defines `add_content` (singular). `add_content_units` is admittedly clunky, but is more clear.
Updated by dkliban@redhat.com over 6 years ago
- Status changed from NEW to ASSIGNED
- Assignee set to dkliban@redhat.com
Updated by daviddavis over 6 years ago
Not a huge fan of add/remove_content_units but I like it better than add/remove_content. Seems like the param should be plural. Perhaps another option: add/remove_content_hrefs?
Updated by dkliban@redhat.com over 6 years ago
- Status changed from ASSIGNED to POST
Added by dkliban@redhat.com over 6 years ago
Added by dkliban@redhat.com over 6 years ago
Revision d88f2f1a | View on GitHub
Adds ability to POST to repository version API
This patchs adds ability to create new repository versions by specifying a list of content to add to the previous version and remove from the previous version.
Updated by dkliban@redhat.com over 6 years ago
- Status changed from POST to MODIFIED
- % Done changed from 0 to 100
Applied in changeset pulp|d88f2f1a7b405cd579b7ae4489b9b9019bd76dac.
Updated by bmbouter over 4 years ago
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
.
Adds ability to POST to repository version API
This patchs adds ability to create new repository versions by specifying a list of content to add to the previous version and remove from the previous version.
closes #3234 https://pulp.plan.io/issues/3234