no Read-After-Write consistency

[samrees]

A client we use to access chartmuseum uploads charts then immediately tries to fetch them down. https://github.com/cathive/concourse-chartmuseum-resource/blob/7dab3bf0168f32dbd6632daa8571a4958c7e1145/out.ts#L267

Recently we've been seeing a failure where that immediate GET returns {"error":"No chart version found for xxxxx-0.59.3"}

Since the backing S3 storage is read-after-write consistent, we expected ChartMuseum to be the same, but it doesnt appear that it is.

Maybe this shouldnt be expected to be supported, or if it supported it will need to be supported through a different PUT call that blocks until all chartmuseums are capable of GETing it, but thought to open this issue in case others are seeing this.

[samrees]

Maybe related to this: https://github.com/helm/chartmuseum/issues/175