Story #4680
closedAs a user I have lifecycle docs in pulpcore workflows
0%
Description
Add documentation about use cases for base_version.
1 - User being able to roll back a certain repo version.
2 - Define the base_version for a new repo version.
See: https://docs.pulpproject.org/en/3.0/nightly/restapi.html#operation/repositories_versions_create
Related issues
Updated by kersom over 5 years ago
- Related to Issue #4665: Field base_version set as none even when repo has multiple versions added
Updated by amacdona@redhat.com over 5 years ago
- Sprint/Milestone set to 3.0.0
- Triaged changed from No to Yes
- Sprint set to Sprint 52
Updated by amacdona@redhat.com over 5 years ago
- Tracker changed from Issue to Story
- Subject changed from Document use cases to use repository base_version to As a user I have lifecycle docs in pulpcore workflows
- % Done set to 0
This will take the place of the Promotion stub. s/Promotion/Lifecycle/
https://docs.pulpproject.org/en/3.0/nightly/workflows/promotion.html
This story will address 2 areas.
Workflow:¶
("workflows" might get renamed)
remind user to check plugin docs first
This section should *clearly indicate that the lifecycle workflow is the **common case, and is intended to supplement plugin documentation. Users should consult their plugin docs first to make sure this workflow applies to them.
explain the why
Lifecycling in Pulp uses the Distribution Object (Link to Distribution REST API) to host publications at a namespace controlled by the user. This is a powerful tool and is intended to allow flexible workflows. 2 examples:
- "promote" from dev->testing->prod for example.
- Rollback to previous publications
REST API autodocs¶
Improve the clarity of the help_text for each field on a distribution, try to use the language of the lifecycling workflow, and include a link.
Autodistribution should be covered in the help_text for publisher/repository. (was https://pulp.plan.io/issues/3392)
Updated by amacdona@redhat.com over 5 years ago
- Has duplicate Issue #3392: Document Autodistribution added
Updated by kersom over 5 years ago
- Related to Test #4667: Test repository version can not be updated using PATCH/PUT added
Updated by amacdona@redhat.com over 5 years ago
- Blocked by Story #4745: As a plugin writer, I can create distributions for repository versions added
Updated by amacdona@redhat.com over 5 years ago
We have been discussing some changes in this area.
1) Associating distributions to repository versions https://pulp.plan.io/issues/4745
2) master/detail distributions (no issue yet)
If either of these changes goes forward, it will completely change what these docs need to be, so I propose we remove this one from the current sprint.
Updated by amacdona@redhat.com over 5 years ago
- Sprint changed from Sprint 53 to Sprint 54
Updated by ttereshc over 5 years ago
- Sprint changed from Sprint 54 to Sprint 55
Updated by dkliban@redhat.com over 5 years ago
- Sprint changed from Sprint 55 to Sprint 56
Updated by bmbouter about 4 years ago
- Status changed from NEW to CLOSED - CURRENTRELEASE
This is referenced here https://docs.pulpproject.org/pulpcore/workflows/promotion.html?highlight=base_version