Explicitly using API_BASE_URL from current connection in datastore. #1293
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This can be seen as a bug-fix where a sub-class may not be able to impact the URIs generated. In addition, we added the (repeated) value of the base connection's API_BASE_URL in advance of swapping it out for v1beta3.
googlebot
added
the
cla: yes
Contributor
|
LGTM |
dhermes
added a commit
that referenced
this pull request
Dec 16, 2015
Explicitly using API_BASE_URL from current connection in datastore.
parthea
added a commit
that referenced
this pull request
Nov 24, 2025
* ci: configure release automation using owl bot * 🦉 Updates from OwlBot post-processor See https://github.com/googleapis/repo-automation-bots/blob/main/packages/owl-bot/README.md Co-authored-by: Owl Bot <gcf-owl-bot[bot]@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
This can be seen as a bug-fix where a sub-class may not be able to impact the URIs generated.
In addition, we added the (repeated) value of the base connection's
API_BASE_URLin advance of swapping it out forv1beta3.