Actions
Story #7939
closedTask #7938: [EPIC] As a user, I have improved Galaxy V3 sync performance
As a user, the /v3/ endpoint returns the repository_version.created time
Start date:
Due date:
% Done:
100%
Estimated time:
Platform Release:
Groomed:
Yes
Sprint Candidate:
No
Tags:
Sprint:
Sprint 89
Quarter:
Description
For example when the user requests this: /pulp_ansible/galaxy/<path:path>/api/v3/
They will receive this:
{
"published": "2019-08-24T14:15:22Z"
}
The published time comes from repository_version.created.
Related issues
Updated by bmbouter about 4 years ago
- Subject changed from As a user, I the /v3/ endpoint returns the repository_version.created time to As a user, the /v3/ endpoint returns the repository_version.created time
Updated by bmbouter about 4 years ago
- Blocks Story #7942: As a sync user, I get no-op when possible added
Updated by fao89 almost 4 years ago
- Status changed from NEW to ASSIGNED
- Assignee set to fao89
- Groomed changed from No to Yes
- Sprint set to Sprint 88
Updated by pulpbot almost 4 years ago
- Status changed from ASSIGNED to POST
Added by Fabricio Aguiar almost 4 years ago
Updated by Anonymous almost 4 years ago
- Status changed from POST to MODIFIED
- % Done changed from 0 to 100
Applied in changeset pulp_ansible|c28fc752227b9dcf3b40939340976e9d547e66c9.
Updated by pulpbot almost 4 years ago
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Updated by bmbouter almost 4 years ago
- Has duplicate Story #7731: As a user, I can use a /metadata endpoint to efficiently tell me if I need to perform a sync at all added
Actions
Introduce a new v3/ endpoint returning publication time
https://pulp.plan.io/issues/7939 closes #7939