Remove useless getObjectRetention call … #156
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
… because the information is delivered by the headObject call. The problem here was that the Traefic ingress is incorrect configured in regards to the
Access-Control-Expose-Headers
header. Because of that the headersX-Amz-Object-Lock-Mode
andX-Amz-Object-Lock-Retain-Until-Date
where not included in the response.Related to: https://github.com/aquarist-labs/s3gw/issues/410 and s3gw-tech/s3gw-charts#89
Describe your changes
Issue ticket number and link
Checklist before requesting a review