Scott Blair
Results
2
comments of
Scott Blair
Actually just occurred to me after submitting this bug that using 127.0.0.1 might be another viable workaround. I'll give that a try and see how it goes.
Been debugging the issue with the cleanup policy you described. Best I can tell, it works as expected only when the S3 object has a leading slash. So `entities.csv` results...