As a developer, I want to refactor the utils.does_s3_prefix_exist method, so I can use a less expensive operation. The head_object operation is approx 12.5x less expensive than list_objects_v2 even with a MaxKeys set to 1.
Note: This may be lower priority since does_s3_prefix_exist is only called 1x when any metadata record is updated in docdb.
Acceptance criteria
[ ] Given the does_s3_prefix_exist method is called for any prefix, the head_object operation is used.
Sprint Ready Checklist
[ ] 1. Acceptance criteria defined
[ ] 2. Team understands acceptance criteria
[ ] 3. Team has defined solution / steps to satisfy acceptance criteria
[ ] 4. Acceptance criteria is verifiable / testable
[ ] 5. External / 3rd Party dependencies identified
User story
As a developer, I want to refactor the
utils.does_s3_prefix_existmethod, so I can use a less expensive operation. The head_object operation is approx 12.5x less expensive than list_objects_v2 even with a MaxKeys set to 1.Note: This may be lower priority since
does_s3_prefix_existis only called 1x when any metadata record is updated in docdb.Acceptance criteria
does_s3_prefix_existmethod is called for any prefix, the head_object operation is used.Sprint Ready Checklist
Notes