Skip to content

S3 Repository: Deprecate specifying region#22848

Merged
rjernst merged 1 commit intoelastic:5.xfrom
rjernst:deprecate_s3_region
Jan 29, 2017
Merged

S3 Repository: Deprecate specifying region#22848
rjernst merged 1 commit intoelastic:5.xfrom
rjernst:deprecate_s3_region

Conversation

@rjernst
Copy link
Copy Markdown
Member

@rjernst rjernst commented Jan 28, 2017

The region and endpoint settings overlap, and have complicated logic for
which to use. Futhermore, region is not necessary, as for most cases it
is automatically figured out by the s3 client, given the bucket name,
and for custom cases like a new region, the endpoint is necessary
anyways. This commit adds a deprecation warning when specifying region.

relates #22758

The region and endpoint settings overlap, and have complicated logic for
which to use. Futhermore, region is not necessary, as for most cases it
is automatically figured out by the s3 client, given the bucket name,
and for custom cases like a new region, the endpoint is necessary
anyways. This commit adds a deprecation warning when specifying region.

relates elastic#22758
Copy link
Copy Markdown

@abeyad abeyad left a comment

Choose a reason for hiding this comment

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

LGTM

Copy link
Copy Markdown
Contributor

@dadoonet dadoonet left a comment

Choose a reason for hiding this comment

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

LGTM2 :)

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

Labels

>deprecation :Distributed/Snapshot/Restore Anything directly related to the `_snapshot/*` APIs v5.3.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants