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

service/s3: Update hostCompatibleBucketName doc to reflect #848 changes #1683

Merged
merged 2 commits into from May 5, 2022

Conversation

lggomez
Copy link
Contributor

@lggomez lggomez commented Apr 26, 2022

Updated the comment for the method as S3ForcePathStyle was deprecated and at a first glance it is not obvious why the default behavior changes when migrating from SDK v1 to V2 and how to enforce the endpoint to not append the bucket name. This includes #848

PS: I saw the PR template about opening an issue first but it wasn't clear which files are autogenerated and which ones are not (if everything under feature/* falls into this category). If the former is needed please tell me

@lggomez lggomez force-pushed the service/s3/endpoint_doc_update branch from 2027653 to a20bc9a Compare April 26, 2022 16:15
@lggomez lggomez changed the title Update hostCompatibleBucketName doc to reflect #848 changes service/s3: Update hostCompatibleBucketName doc to reflect #848 changes Apr 26, 2022
Updates the doc string for hostCompatibleBucketName adding link to the resolved Endpoint member driving the behavior.
Copy link
Contributor

@jasdel jasdel left a comment

Choose a reason for hiding this comment

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

Thanks for updating the documentation for this behavior. I've made a minor tweak to the change, and adding link to the member driving this behavior.

@jasdel jasdel merged commit 11aebce into aws:main May 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants