S3 Client HeadObject requires SSE parameters #864
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Matching GetObject, though we can't re-use the code since it's a distinct struct. Signed-off-by: Christian Mesh <christianmesh1@gmail.com>
|
Reminder for the PR assignee: If this is a user-visible change, please update the changelog as part of the PR. |
Yantrio
approved these changes
Nov 13, 2023
TF_ACC=1 go test -coverprofile s3.cov ./internal/backend/remote-state/s3/...
ok github.com/opentofu/opentofu/internal/backend/remote-state/s3 116.815s coverage: 84.5% of statements |
cube2222
approved these changes
Nov 13, 2023
thumperward
pushed a commit
to thumperward/opentf
that referenced
this pull request
Jan 10, 2024
Signed-off-by: Christian Mesh <christianmesh1@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Matching GetObject, though we can't re-use the code since it's a distinct struct.
Broken in #840
Resolves #863
@Yantrio suggests that since this bug was not released in a stable release, it does not need to go in the CHANGELOG.md
Target Release
1.6.0