Skip to content

Conversation

@disq
Copy link
Member

@disq disq commented May 8, 2023

@disq disq requested review from a team and candiduslynx and removed request for a team May 8, 2023 08:31
@cq-bot cq-bot added the s3 label May 8, 2023
@disq disq requested a review from bbernays May 8, 2023 08:55
Copy link
Member

@hermanschaaf hermanschaaf left a comment

Choose a reason for hiding this comment

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

The change looks good, but missing documentation (I don't think AWS_S3_ENDPOINT is a standard AWS environment variable?)


- `endpoint` (string) (optional, default empty)

Endpoint to use for S3 API calls. This is useful for S3-compatible storage services such as MinIO.
Copy link
Member

Choose a reason for hiding this comment

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

Maybe we can include an example that shows how to use this in conjunction with an AWS_S3_ENDPOINT environment variable (we can do this in a follow-up)

Copy link
Member Author

Choose a reason for hiding this comment

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

@hermanschaaf What do you mean, there's no AWS_S3_ENDPOINT env var any more?

Copy link
Member

Choose a reason for hiding this comment

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

Sorry yeah I mean, if a user was set on using an environment variable called AWS_S3_ENDPOINT (like I think the user who requested this was), then they can still do so by doing:

endpoint: "${AWS_S3_ENDPOINT}"

which I think is worth pointing out in the docs

@candiduslynx candiduslynx changed the title feat(s3): Add support for AWS_S3_ENDPOINT env variable feat(s3): Add support for custom AWS S3 endpoint May 9, 2023
@candiduslynx candiduslynx changed the title feat(s3): Add support for custom AWS S3 endpoint feat(s3): Add support for custom S3 endpoint May 9, 2023
@candiduslynx candiduslynx added automerge Automatically merge once required checks pass priority merge labels May 9, 2023
@kodiakhq kodiakhq bot merged commit 48c6379 into main May 9, 2023
@kodiakhq kodiakhq bot deleted the feat/s3awsendpoint branch May 9, 2023 08:52
kodiakhq bot pushed a commit that referenced this pull request May 9, 2023
🤖 I have created a release *beep* *boop*
---


## [4.2.0](plugins-destination-s3-v4.1.0...plugins-destination-s3-v4.2.0) (2023-05-09)


### Features

* **s3:** Add support for custom S3 endpoint ([#10589](#10589)) ([48c6379](48c6379))


### Bug Fixes

* **deps:** Update module github.com/aws/aws-sdk-go-v2/config to v1.18.23 ([#10576](#10576)) ([eeb13d5](eeb13d5))
* **deps:** Update module github.com/aws/aws-sdk-go-v2/feature/s3/manager to v1.11.65 ([#10582](#10582)) ([4ed90e3](4ed90e3))

---
This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

automerge Automatically merge once required checks pass

Projects

None yet

Development

Successfully merging this pull request may close these issues.

feat: add AWS_S3_ENDPOINT in plugin s3 destination

6 participants