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

Broker ignores broker_path_style setting when accessing management bucket #227

Open
martinrohrbach opened this issue Jul 1, 2022 · 1 comment

Comments

@martinrohrbach
Copy link

This looks like a followup to #199.

We were very happy about this change and recently tried the latest update in our environment. In the service broker settings, we have unchecked "S3 Path style access" and when we create a bucket with the CF marketplace and create a corresponding service key then everything works as expected and the service key uses domain style (or vhost style) to access the bucket.

However, we discovered that the service broker keeps accessing its managemet bucket using path style despite the config option mentioned above.

My colleagues had a quick look through the code and might have found the problem here because the broker does not actually use the path style setting:

S3Config s3Config = new S3Config(new URI(repositoryEndpoint))
.withUseV2Signer(!config.isAwsSignatureV4())
.withIdentity(userName)
.withSecretKey(repositorySecret);

Does this need the same fix as #199?

@rogalv
Copy link
Collaborator

rogalv commented Jul 4, 2022

Yes, host-style was not a supported for repository connection, it was implemented only for service bindings. Marking as an enhancement, planning to add to future release.

@rogalv rogalv added this to To Do in 2.3.1 Jul 8, 2022
@twincitiesguy twincitiesguy removed this from To Do in 2.3.1 Apr 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants