Enable endpoint discovery by default for services that support it #1840
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Endpoint discovery allows the SDK to discover an endpoint based on the resource being accessed. This change makes this feature opt-out instead of opt-in for clients of services that support endpoint discovery. An additional call to the endpoint discovery service will be made when an endpoint needs to be discovered, that value is then cached and re-used.
Motivation and Context
There may be services launched in the future that only support endpoint discovery instead of traditional static endpoints. We believe endpoint discovery will provide a better experience for customers, and therefore we want to give them that better experience out of the box without expecting them to know to enable it. Any customers that do not wish to use endpoint discovery may opt-out by setting 'endpointDiscoveryEnabled(false)' on the client builder.
Testing
Ran all unit/functional and mock integration tests. Verified through manual integration testing that endpoint discovery calls were being made.
Types of changes
Checklist
mvn install
succeedsLicense