-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
feature: add support for per-service endpoint url configuration #2737
Conversation
pick 1ca30ba add support for per-service endpoint url configuration
0f8236a
to
8aa98e0
Compare
@@ -35,6 +36,7 @@ public static function getArguments() | |||
// (e.g. http://search-blah.{region}.cloudsearch.amazonaws.com) | |||
return explode('.', new Uri($args['endpoint']))[1]; | |||
}; | |||
unset($args['endpoint']['default']); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why is this necessary? This seems like an endpoint is always required, so it should never go to the default?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The client resolver won't handle the 'required' property if there's a default
Issue #, if available:
#1239
Description of changes:
Adds the ability to configure endpoints on a per-service basis via the environment and ini file. Order of precedence is as follows:
endpoint
client configurationAWS_ENDPOINT_URL_<SERVICE_IDENTIFIER>
env varservices
endpoint in shared config example:AWS_ENDPOINT_URL
env varendpoint_url
in shared config. example:For backward-compatibility, we will continue to support the
endpoint
client constructor option, however,endpoint_url
will take precedence, if resolved from any one of the above-mentioned options.By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.