Skip to content

chore(releasing): Add upgrade note for 0.31.0 about S3 path changes #17934

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.

Sign up for GitHub

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

Merged
jszwedko merged 3 commits into from
Jul 11, 2023
Merged

chore(releasing): Add upgrade note for 0.31.0 about S3 path changes #17934

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
d6b0f22
chore(releasing): Add upgrade note for 0.31.0 about S3 path changes
jszwedko Jul 10, 2023
31f1eb0
Allow spelling
jszwedko Jul 10, 2023
4d69383
Fix markdown
jszwedko Jul 10, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 14 additions & 0 deletions website/content/en/highlights/2023-07-05-0-31-0-upgrade-guide.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,6 +14,10 @@ Vector's 0.31.0 release includes **breaking changes**:
1. [Removal of various deprecated internal metrics](#deprecated-internal-metrics)
1. [`component_received_event_bytes_total` and `component_sent_event_bytes_total` consistently use estimated JSON size of the event](#event_json_size)

and **potentially impactful changes**:

1. [AWS S3 endpoint path changes](#s3-paths)

We cover them below to help you upgrade quickly:

## Upgrade guide
Expand Down Expand Up @@ -61,3 +65,13 @@ of the event should it be serialized to JSON.
Measuring the events like this allows a consistent measurement to be applied
across all components regardless of how the source or sink serializes the event
when connecting to the external service.

### Potentially impactful changes

#### AWS S3 endpoint path changes {#s3-paths}

The handling of AWS S3 endpoints for the `aws_s3` source and sink has changed due to an upgrade of
the SDK that we use. For S3-compatible APIs like Cloudflare R2 you may find that you need to remove
Comment thread Fixed
the bucket name from the endpoint, if you have it specified. For example
``https://xxxxxxxxxxxxxxxxxxxxxxxxxxx.r2.cloudflarestorage.com/<bucket name>` should be written as
``https://xxxxxxxxxxxxxxxxxxxxxxxxxxx.r2.cloudflarestorage.com``.
Comment thread
dsmith3197 marked this conversation as resolved.
Outdated