We noticed some 409 responses due to setting deleteAfter immediately after uploading an object to our swift cluster. Upon transitioning to include the deleteAfter in the upload instructions for an atomic call, we ran into some issues with the mock not persisting the deleteAfter/deleteAt value.
This is just to persist the deleteAfter on the object stored by the mock.
We noticed some 409 responses due to setting deleteAfter immediately after uploading an object to our swift cluster. Upon transitioning to include the deleteAfter in the upload instructions for an atomic call, we ran into some issues with the mock not persisting the deleteAfter/deleteAt value.
This is just to persist the deleteAfter on the object stored by the mock.