1. 06 Feb, 2021 2 commits
  2. 05 Feb, 2021 1 commit
  3. 03 Feb, 2021 4 commits
  4. 02 Feb, 2021 4 commits
  5. 01 Feb, 2021 3 commits
  6. 30 Jan, 2021 1 commit
  7. 29 Jan, 2021 6 commits
  8. 28 Jan, 2021 2 commits
  9. 27 Jan, 2021 1 commit
  10. 26 Jan, 2021 4 commits
  11. 18 Dec, 2020 3 commits
  12. 14 Dec, 2020 1 commit
  13. 09 Dec, 2020 2 commits
  14. 07 Dec, 2020 1 commit
  15. 30 Nov, 2020 1 commit
    • Ricardo Maraschini's avatar
      Ignore self reference object on empty prefix · 87cbd09f
      Ricardo Maraschini authored
      
      When a given prefix is empty and we attempt to list its content AWS
      returns that the prefix contains one object with key defined as the
      prefix with an extra "/" at the end.
      
      e.g.
      
      If we call ListObjects() passing to it an existing but empty prefix,
      say "my/empty/prefix", AWS will return that "my/empty/prefix/" is an
      object inside "my/empty/prefix" (ListObjectsOutput.Contents).
      
      This extra "/" causes the upload purging process to panic. On normal
      circunstances we never find empty prefixes on S3 but users may touch
      it.
      Signed-off-by: default avatarRicardo Maraschini <rmarasch@redhat.com>
      87cbd09f
  16. 14 Nov, 2020 1 commit
  17. 06 Nov, 2020 1 commit
  18. 05 Nov, 2020 2 commits