[RTFACT-16153] Helm virtual index.yaml takes the first generated date instead of the latest generated date Created: 18/Mar/18  Updated: 25/Jun/18  Resolved: 25/Jun/18

Status: Resolved
Project: Artifactory Binary Repository
Component/s: Helm
Affects Version/s: 5.8.0, 5.9.0
Fix Version/s: 6.1.0

Type: Bug Priority: Minor
Reporter: Nadav Yogev Assignee: Nadav Yogev
Resolution: Fixed Votes: 0
Labels: None

Assigned QA: Nadav Yogev

 Description   

The generated timestamp is generated after each helm upload/deletion event. in a virtual repository the merge index.yaml should take the latest generated date

apiVersion: v1
entries:
  entry1:
     - apiVersion: v1
       ...
generated: 2017-11-08T15:46:33.761984695+02:00

To reproduce:
have 2 local helm repos and a virtual.
upload a chart to the first local repo, wait for indexing and then upload another chart to the 2nd local repo.
download the index.yaml from the virtual repo, and the generated date will be taken from the first repo instead of the 2nd repo.



 Comments   
Comment by Nadav Yogev [ 25/Jun/18 ]

Artifactory will now take the latest timestamp as generated parameter (if possible)

Generated at Fri May 24 11:28:58 UTC 2019 using JIRA 7.6.3#76005-sha1:8a4e38d34af948780dbf52044e7aafb13a7cae58.