datastore: don't require auth with local datastore server #940
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.
Fixes #936
When a service object is created (such as a Dataset object), we have the choice of telling our "makeAuthenticatedRequestFactory" function that we don't care about the authentication part via an option called
customEndpoint
. A Dataset is the one place we use this option in the event a user is trying to communicate with their own Datastore server.We were skipping the auth when:
A user instantiated a Dataset providing an
apiEndpoint
option:But, we also need to support when:
DATASTORE_HOST
env var setWe have had half of the puzzle solved; we detect the presence of that env var and send the API requests to it accordingly. But, we forgot to update
customEndpoint
, the option that skips authenticating.// @brainsiq