chore: fix s3 redirects with prefixes #15404
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.
follow-up #15151
found wrong redirects with @thaJeztah ported from s3 config to cloudfront lambda.
looks like in the s3 config some redirects just strip the key prefix and don't just redirect to
/. this PR adds a new bool fieldstripto handle that behavior.can be tested on labs:
also disable slack notif for labs env as it seems a bit too noisy.