Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[release/4.x] d/aws_s3_object: Test key with multiple leading slashes #35222

Merged

Conversation

ewbankkit
Copy link
Contributor

Description

S3 objects keys with a multiple leading slashes (/) have those characters removed by AWS SDK for Go v1.
Test this.

Relations

Relates #35220.

Output from Acceptance Testing

% make testacc TESTARGS='-run=TestAccS3ObjectDataSource_leadingMultipleSlashes' PKG=s3
==> Checking that code complies with gofmt requirements...
TF_ACC=1 go test ./internal/service/s3/... -v -count 1 -parallel 20  -run=TestAccS3ObjectDataSource_leadingMultipleSlashes -timeout 180m
=== RUN   TestAccS3ObjectDataSource_leadingMultipleSlashes
=== PAUSE TestAccS3ObjectDataSource_leadingMultipleSlashes
=== CONT  TestAccS3ObjectDataSource_leadingMultipleSlashes
--- PASS: TestAccS3ObjectDataSource_leadingMultipleSlashes (35.58s)
PASS
ok  	github.com/hashicorp/terraform-provider-aws/internal/service/s3	41.215s

% make testacc TESTARGS='-run=TestAccS3ObjectDataSource_leadingMultipleSlashes' PKG=s3
==> Checking that code complies with gofmt requirements...
TF_ACC=1 go test ./internal/service/s3/... -v -count 1 -parallel 20  -run=TestAccS3ObjectDataSource_leadingMultipleSlashes -timeout 180m
=== RUN   TestAccS3ObjectDataSource_leadingMultipleSlashes
=== PAUSE TestAccS3ObjectDataSource_leadingMultipleSlashes
=== CONT  TestAccS3ObjectDataSource_leadingMultipleSlashes
--- PASS: TestAccS3ObjectDataSource_leadingMultipleSlashes (35.58s)
PASS
ok  	github.com/hashicorp/terraform-provider-aws/internal/service/s3	41.215s
Copy link

Community Note

Voting for Prioritization

  • Please vote on this pull request by adding a 👍 reaction to the original post to help the community and maintainers prioritize this pull request.
  • Please see our prioritization guide for information on how we prioritize.
  • Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.

For Submitters

  • Review the contribution guide relating to the type of change you are making to ensure all of the necessary steps have been taken.
  • For new resources and data sources, use skaff to generate scaffolding with comments detailing common expectations.
  • Whether or not the branch has been rebased will not impact prioritization, but doing so is always a welcome surprise.

@github-actions github-actions bot added size/M Managed by automation to categorize the size of a PR. tests PRs: expanded test coverage. Issues: expanded coverage, enhancements to test infrastructure. service/s3 Issues and PRs that pertain to the s3 service. labels Jan 10, 2024
@ewbankkit ewbankkit merged commit 23f68e4 into release/4.x Jan 10, 2024
35 of 38 checks passed
@ewbankkit ewbankkit deleted the t-release/4.x-s3-object-key-leading-multiple-slashes branch January 10, 2024 14:09
Copy link

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 10, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
service/s3 Issues and PRs that pertain to the s3 service. size/M Managed by automation to categorize the size of a PR. tests PRs: expanded test coverage. Issues: expanded coverage, enhancements to test infrastructure.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant