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

[Pending] Add AWS v2 package for the agent sidecar #1769

Draft
wants to merge 36 commits into
base: main
Choose a base branch
from

Conversation

hlts2
Copy link
Contributor

@hlts2 hlts2 commented Aug 16, 2022

Description:

I implemented the AWS v2 package for the agent sidecar.
As discussed previously, The logic for uploading and downloading data from s3 is implemented in a file-based way.

NOTE: This PR contains the following new dependencies.

go get github.com/aws/aws-sdk-go-v2/aws
go get github.com/aws/aws-sdk-go-v2/config
go get github.com/aws/aws-sdk-go-v2/service/s3
go get github.com/aws/aws-sdk-go-v2/feature/s3/manager

Impact

The results of the backup speed comparison are as follows. (Average of 5 times)

File size: 280MB

- AWS V1
 - Download time: 10s
 - Upload time: 31s

- AWS V2
 - Download time: 10s
 - Upload time: 29s

Related Issue:

How Has This Been Tested?:

Environment:

  • Go Version: 1.17.3
  • Docker Version: 20.10.8
  • Kubernetes Version: 1.22.0
  • NGT Version: 1.13.8

Types of changes:

  • Bug fix [type/bug]
  • New feature [type/feature]
  • Add tests [type/test]
  • Security related changes [type/security]
  • Add documents [type/documentation]
  • Refactoring [type/refactoring]
  • Update dependencies [type/dependency]
  • Update benchmarks and performances [type/bench]
  • Update CI [type/ci]

Changes to Core Features:

  • Have you added an explanation of what your changes do and why you'd like us to include them?
  • Have you written new tests for your core changes, as applicable?
  • Have you successfully ran tests with your changes locally?

Checklist:

  • I have read the CONTRIBUTING document.
  • I have checked open Pull Requests for the similar feature or fixes?
  • I have added tests and benchmarks to cover my changes.
  • I have ensured all new and existing tests passed.
  • I have commented my code, particularly in hard-to-understand areas
  • I have updated the documentation accordingly.

Summary by CodeRabbit

  • New Features

    • Enhanced S3 storage integration with new concurrency control for upload and download operations.
    • Introduced new logging capabilities for S3 operations.
    • Added new configuration options for S3 client customization, including SSL usage, endpoint discovery, and more.
  • Bug Fixes

    • Removed outdated S3 configuration options such as parameter validation and MD5 validation to streamline functionality.
  • Documentation

    • Updated documentation to reflect new features and removed configurations in S3 storage settings.
  • Refactor

    • Implemented new internal structures for S3 client operations to improve performance and maintainability.

hlts2 and others added 30 commits December 6, 2021 16:31
Signed-off-by: hlts2 <hiroto.funakoshi.hiroto@gmail.com>
Signed-off-by: hlts2 <hiroto.funakoshi.hiroto@gmail.com>
Signed-off-by: hlts2 <hiroto.funakoshi.hiroto@gmail.com>
Signed-off-by: hlts2 <hiroto.funakoshi.hiroto@gmail.com>
Signed-off-by: hlts2 <hiroto.funakoshi.hiroto@gmail.com>
Signed-off-by: hlts2 <hiroto.funakoshi.hiroto@gmail.com>
Signed-off-by: hlts2 <hiroto.funakoshi.hiroto@gmail.com>
Signed-off-by: hlts2 <hiroto.funakoshi.hiroto@gmail.com>
Signed-off-by: hlts2 <hiroto.funakoshi.hiroto@gmail.com>
Signed-off-by: hlts2 <hiroto.funakoshi.hiroto@gmail.com>
Signed-off-by: hlts2 <hiroto.funakoshi.hiroto@gmail.com>
Signed-off-by: hlts2 <hiroto.funakoshi.hiroto@gmail.com>
Signed-off-by: hlts2 <hiroto.funakoshi.hiroto@gmail.com>
Signed-off-by: hlts2 <hiroto.funakoshi.hiroto@gmail.com>
Signed-off-by: hlts2 <hiroto.funakoshi.hiroto@gmail.com>
Signed-off-by: hlts2 <hiroto.funakoshi.hiroto@gmail.com>
Signed-off-by: hlts2 <hiroto.funakoshi.hiroto@gmail.com>
Signed-off-by: hlts2 <hiroto.funakoshi.hiroto@gmail.com>
Signed-off-by: hlts2 <hiroto.funakoshi.hiroto@gmail.com>
Signed-off-by: hlts2 <hiroto.funakoshi.hiroto@gmail.com>
@vdaas-ci
Copy link
Collaborator

[WARNING:INTCFG] Changes in interal/config may require you to change Helm charts. Please check.

@hlts2 hlts2 closed this Aug 16, 2022
@hlts2 hlts2 reopened this Aug 16, 2022
@hlts2 hlts2 changed the title Feature/internal db s3/aws sdk v2 [Pending] Add AWS v2 package for the agent sidecar Aug 16, 2022
Signed-off-by: hlts2 <hiroto.funakoshi.hiroto@gmail.com>
@cloudflare-pages
Copy link

cloudflare-pages bot commented Aug 16, 2022

Deploying vald with  Cloudflare Pages  Cloudflare Pages

Latest commit: 389050f
Status: ✅  Deploy successful!
Preview URL: https://1ac1703e.vald.pages.dev
Branch Preview URL: https://feature-internal-db-s3-aws-s.vald.pages.dev

View logs

@codecov
Copy link

codecov bot commented Aug 16, 2022

Codecov Report

Attention: Patch coverage is 0% with 28 lines in your changes are missing coverage. Please review.

Project coverage is 31.82%. Comparing base (6d4b505) to head (828a0e6).

❗ Current head 828a0e6 differs from pull request most recent head 389050f. Consider uploading reports for the commit 389050f to get more accurate results

Files Patch % Lines
...ent/sidecar/usecase/initcontainer/initcontainer.go 0.00% 14 Missing ⚠️
pkg/agent/sidecar/usecase/sidecar/sidecar.go 0.00% 14 Missing ⚠️
Additional details and impacted files
@@             Coverage Diff             @@
##             main    #1769       +/-   ##
===========================================
+ Coverage   18.91%   31.82%   +12.91%     
===========================================
  Files         565      374      -191     
  Lines       65223    32027    -33196     
===========================================
- Hits        12337    10194     -2143     
+ Misses      52089    21443    -30646     
+ Partials      797      390      -407     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

}

func (c *client) download(ctx context.Context, key string, w io.WriterAt) (err error) {
input := &s3.GetObjectInput{
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚫 [golangci] reported by reviewdog 🐶
ChecksumMode, ExpectedBucketOwner, IfMatch, IfModifiedSince, IfNoneMatch, IfUnmodifiedSince, PartNumber, Range, RequestPayer, ResponseCacheControl, ResponseContentDisposition, ResponseContentEncoding, ResponseContentLanguage, ResponseContentType, ResponseExpires, SSECustomerAlgorithm, SSECustomerKey, SSECustomerKeyMD5, VersionId are missing in GetObjectInput (exhaustruct)

}

func (c *client) upload(ctx context.Context, key string, body io.Reader) (err error) {
input := &s3.PutObjectInput{
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚫 [golangci] reported by reviewdog 🐶
ACL, BucketKeyEnabled, CacheControl, ChecksumAlgorithm, ChecksumCRC32, ChecksumCRC32C, ChecksumSHA1, ChecksumSHA256, ContentDisposition, ContentEncoding, ContentLanguage, ContentLength, ContentMD5, ExpectedBucketOwner, Expires, GrantFullControl, GrantRead, GrantReadACP, GrantWriteACP, Metadata, ObjectLockLegalHoldStatus, ObjectLockMode, ObjectLockRetainUntilDate, RequestPayer, SSECustomerAlgorithm, SSECustomerKey, SSECustomerKeyMD5, SSEKMSEncryptionContext, SSEKMSKeyId, ServerSideEncryption, StorageClass, Tagging, WebsiteRedirectLocation are missing in PutObjectInput (exhaustruct)

io.WriteCloser
}

type client struct {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚫 [golangci] reported by reviewdog 🐶
fieldalignment: struct with 104 pointer bytes could be 80 (govet)

"github.com/vdaas/vald/internal/log"
)

type client struct {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚫 [golangci] reported by reviewdog 🐶
fieldalignment: struct with 208 pointer bytes could be 168 (govet)


type logger struct{}

func New() logging.Logger {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚫 [golangci] reported by reviewdog 🐶
New returns interface (github.com/aws/smithy-go/logging.Logger) (ireturn)

}

func New(opts ...Option) (Client, error) {
c := new(client)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚫 [golangci] reported by reviewdog 🐶
variable name 'c' is too short for the scope of its usage (varnamelen)


func (c *client) Open(ctx context.Context, key string) (err error) {
c.wg = new(sync.WaitGroup)
f, err := file.CreateTemp()
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚫 [golangci] reported by reviewdog 🐶
variable name 'f' is too short for the scope of its usage (varnamelen)


// New returns blob.Bucket implementation if no error occurs.
func New(opts ...Option) (b blob.Bucket, err error) {
c := new(client)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚫 [golangci] reported by reviewdog 🐶
variable name 'c' is too short for the scope of its usage (varnamelen)

return err
}

c.s3client = s3.NewFromConfig(cfg, func(o *s3.Options) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚫 [golangci] reported by reviewdog 🐶
parameter name 'o' is too short for the scope of its usage (varnamelen)

// The minimum allowed part size is 5MB, and if this value is set to zero,
// the DefaultUploadPartSize(DefaultDownloadPartSize) value will be used.
func WithMaxPartSize(size string) Option {
return func(c *client) error {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚫 [golangci] reported by reviewdog 🐶
parameter name 'c' is too short for the scope of its usage (varnamelen)

Copy link
Contributor

coderabbitai bot commented May 8, 2024

Walkthrough

Walkthrough

The recent updates focus on refining S3 storage interactions across various components in the Vald Helm chart and internal S3 storage handling. Changes include the removal of outdated S3 features, introduction of concurrency controls, and enhancements in error handling and logging. These modifications aim to streamline operations, improve performance, and ensure more robust data handling with AWS S3.

Changes

File Path Change Summary
charts/.../crds/valdrelease.yaml Modified schema properties for S3 settings, removed some outdated options.
charts/.../values.yaml Updated S3 settings in Helm values, focusing on concurrency and removing deprecated features.
internal/.../blob_test.go Updated S3Config struct to include Concurrency.
internal/.../s3/downloader/..., uploader/... Enhanced client functionality for S3 downloads and uploads, including error handling and options.
internal/.../s3/file/file.go Introduced file handling for temporary storage during operations.
internal/.../s3/logger/logger.go Added custom logging for S3 operations, mapping AWS Smithy logs to internal levels.
internal/.../s3/s3.go, option.go General enhancements in S3 client configuration and operations, maintaining existing functionalities.

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share
Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@github-actions github-actions bot added size/XL and removed size/XL labels May 8, 2024
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

Review Details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits Files that changed from the base of the PR and between 6d4b505 and 389050f.
Files selected for processing (11)
  • charts/vald-helm-operator/crds/valdrelease.yaml (1 hunks)
  • charts/vald/values.yaml (1 hunks)
  • internal/config/blob_test.go (6 hunks)
  • internal/db/storage/blob/v3/s3/downloader/downloader.go (1 hunks)
  • internal/db/storage/blob/v3/s3/downloader/option.go (1 hunks)
  • internal/db/storage/blob/v3/s3/file/file.go (1 hunks)
  • internal/db/storage/blob/v3/s3/logger/logger.go (1 hunks)
  • internal/db/storage/blob/v3/s3/option.go (1 hunks)
  • internal/db/storage/blob/v3/s3/s3.go (1 hunks)
  • internal/db/storage/blob/v3/s3/uploader/option.go (1 hunks)
  • internal/db/storage/blob/v3/s3/uploader/uploader.go (1 hunks)
Files skipped from review due to trivial changes (1)
  • internal/db/storage/blob/v3/s3/option.go
Additional comments not posted (29)
internal/db/storage/blob/v3/s3/logger/logger.go (2)

12-14: LGTM! The New function correctly implements a factory pattern for creating logger instances.


16-25: LGTM! The Logf function correctly handles different logging classifications.

internal/db/storage/blob/v3/s3/file/file.go (2)

14-24: LGTM! The Close function correctly handles the file lifecycle by closing and removing the file, with appropriate error handling.


27-36: LGTM! The CreateTemp function correctly creates a temporary file and handles potential errors.

internal/db/storage/blob/v3/s3/downloader/option.go (4)

17-26: LGTM! The WithBucket option function correctly sets and validates the bucket name.


28-37: LGTM! The WithAPIClient option function correctly sets the API client with appropriate nil checks.


39-48: LGTM! The WithConcurrency option function correctly sets the concurrency level with a minimum requirement check.


50-59: LGTM! The WithMaxPartSize option function correctly sets the maximum part size with a minimum size requirement.

internal/db/storage/blob/v3/s3/uploader/option.go (6)

20-29: LGTM! The WithErrGroup option function correctly sets the error group with appropriate nil checks.


31-40: LGTM! The WithBucket option function correctly sets and validates the bucket name.


42-51: LGTM! The WithAPIClient option function correctly sets the API client with appropriate nil checks.


53-62: LGTM! The WithContentType option function correctly sets and validates the content type.


64-73: LGTM! The WithConcurrency option function correctly sets the concurrency level with a minimum requirement check.


75-84: LGTM! The WithMaxPartSize option function correctly sets the maximum part size with a minimum size requirement.

internal/db/storage/blob/v3/s3/downloader/downloader.go (3)

36-44: LGTM! The New function correctly initializes a new downloader client with error handling.


46-74: LGTM! The Download function correctly performs the download operation with comprehensive error handling and resource management.


77-91: LGTM! The download function correctly uses the AWS SDK to perform the download and handles errors appropriately.

internal/db/storage/blob/v3/s3/uploader/uploader.go (5)

40-48: LGTM! The New function correctly initializes a new uploader client with error handling.


50-83: LGTM! The Open function correctly prepares the uploader for writing with comprehensive resource management and error handling.


85-94: LGTM! The Close function correctly manages resource cleanup for the uploader.


97-102: LGTM! The Write function correctly writes data with appropriate checks and error handling.


104-123: LGTM! The upload function correctly uses the AWS SDK to perform the upload and handles errors appropriately.

internal/db/storage/blob/v3/s3/s3.go (5)

54-70: LGTM! The New function correctly initializes a new S3 client with error handling and logger setup.


73-148: LGTM! The Open function correctly configures the S3 client with comprehensive settings and error handling.


150-153: LGTM! The Close function correctly implements a placeholder for resource cleanup.


155-159: LGTM! The Reader function correctly creates a reader for S3 downloads.


161-169: LGTM! The Writer function correctly creates a writer for S3 uploads with appropriate initialization and error handling.

charts/vald/values.yaml (1)

2356-2358: Ensure the minimum concurrency setting aligns with system requirements.

Verification successful

The verification process aimed to determine if the minimum concurrency setting of 3 for the S3 operations in the Vald system's Helm chart configuration aligns with the system's performance requirements. The script executed searched for issues and pull requests related to "concurrency" in their title or body.

Analysis of the Script Output:

  • Issues: No issues were returned from the search, indicating there are no reported problems directly mentioning "concurrency" in the context of system performance or configuration.
  • Pull Requests: A single draft pull request was found, titled "[Pending] Add AWS v2 package for the agent sidecar". This PR does not directly address the concurrency setting but seems related to an upgrade or change in the AWS SDK used by the agent sidecar. The relevance of this PR to the concurrency setting is not clear without further details.

Conclusion:

Given the absence of reported issues directly related to the concurrency setting, and the lack of clear connection between the found PR and the specific concurrency configuration, there is no evidence from the GitHub repository to suggest that the minimum concurrency setting of 3 is insufficient or problematic.

Final Response:

The review comment's concern about ensuring the minimum concurrency setting aligns with system requirements appears to be addressed adequately in the current configuration, as there are no reported issues suggesting otherwise.

Scripts Executed

The following scripts were executed for the analysis:


Script:

#!/bin/bash
# Description: Verify that the minimum concurrency setting of 3 is sufficient for the system's performance requirements.

# Test: Check if there are any related performance issues reported in the issues or pull requests.
gh issue list --search "concurrency in:title,body"
gh pr list --search "concurrency in:title,body"

Length of output: 228

charts/vald-helm-operator/crds/valdrelease.yaml (1)

1053-1055: Ensure the concurrency property's minimum value aligns with the new AWS SDK v2 requirements.

@hlts2
Copy link
Contributor Author

hlts2 commented May 8, 2024

@coderabbitai review

Copy link
Contributor

coderabbitai bot commented May 8, 2024

Actions Performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

Copy link
Contributor

coderabbitai bot commented May 8, 2024

Note

Currently processing new changes in this PR. This may take a few minutes, please wait...

Commits Files that changed from the base of the PR and between 6d4b505 and 389050f.
Files selected for processing (11)
  • charts/vald-helm-operator/crds/valdrelease.yaml (1 hunks)
  • charts/vald/values.yaml (1 hunks)
  • internal/config/blob_test.go (6 hunks)
  • internal/db/storage/blob/v3/s3/downloader/downloader.go (1 hunks)
  • internal/db/storage/blob/v3/s3/downloader/option.go (1 hunks)
  • internal/db/storage/blob/v3/s3/file/file.go (1 hunks)
  • internal/db/storage/blob/v3/s3/logger/logger.go (1 hunks)
  • internal/db/storage/blob/v3/s3/option.go (1 hunks)
  • internal/db/storage/blob/v3/s3/s3.go (1 hunks)
  • internal/db/storage/blob/v3/s3/uploader/option.go (1 hunks)
  • internal/db/storage/blob/v3/s3/uploader/uploader.go (1 hunks)
 _________________________________________________
< PhD, MSc, BSc, and a black belt in code review. >
 -------------------------------------------------
  \
   \   \
        \ /\
        ( )
      .( o ).

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share
Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

Review Details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits Files that changed from the base of the PR and between 6d4b505 and 389050f.
Files selected for processing (11)
  • charts/vald-helm-operator/crds/valdrelease.yaml (1 hunks)
  • charts/vald/values.yaml (1 hunks)
  • internal/config/blob_test.go (6 hunks)
  • internal/db/storage/blob/v3/s3/downloader/downloader.go (1 hunks)
  • internal/db/storage/blob/v3/s3/downloader/option.go (1 hunks)
  • internal/db/storage/blob/v3/s3/file/file.go (1 hunks)
  • internal/db/storage/blob/v3/s3/logger/logger.go (1 hunks)
  • internal/db/storage/blob/v3/s3/option.go (1 hunks)
  • internal/db/storage/blob/v3/s3/s3.go (1 hunks)
  • internal/db/storage/blob/v3/s3/uploader/option.go (1 hunks)
  • internal/db/storage/blob/v3/s3/uploader/uploader.go (1 hunks)
Files skipped from review as they are similar to previous changes (11)
  • charts/vald-helm-operator/crds/valdrelease.yaml
  • charts/vald/values.yaml
  • internal/config/blob_test.go
  • internal/db/storage/blob/v3/s3/downloader/downloader.go
  • internal/db/storage/blob/v3/s3/downloader/option.go
  • internal/db/storage/blob/v3/s3/file/file.go
  • internal/db/storage/blob/v3/s3/logger/logger.go
  • internal/db/storage/blob/v3/s3/option.go
  • internal/db/storage/blob/v3/s3/s3.go
  • internal/db/storage/blob/v3/s3/uploader/option.go
  • internal/db/storage/blob/v3/s3/uploader/uploader.go

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants