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

S3 Backend: Converts from legacy/helper/schema to configschema #33534

Merged
merged 20 commits into from
Jul 25, 2023

Conversation

gdavison
Copy link
Contributor

Convert S3 Backend implementation from legacy/helper/schema to configschema as part of modernization effort.

Relates #30443

Target Release

This change should be invisible to practitioners

Draft CHANGELOG entry

This change should be invisible to practitioners

@gdavison gdavison requested a review from a team as a code owner July 17, 2023 19:38
"fmt"
"os"
"strings"

"github.com/aws/aws-sdk-go/aws"
"github.com/aws/aws-sdk-go/service/dynamodb"
"github.com/aws/aws-sdk-go/service/s3"
awsbase "github.com/hashicorp/aws-sdk-go-base"

This comment was marked as spam.

@gdavison gdavison merged commit 5588603 into main Jul 25, 2023
@gdavison gdavison deleted the s3/update-configschema branch July 25, 2023 00:46
@github-actions
Copy link
Contributor

Reminder for the merging maintainer: if this is a user-visible change, please update the changelog on the appropriate release branch.

Copy link
Contributor

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 contributions.
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 Dec 13, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants