Skip to content

Remove gcloud vendor and just use apitools code#811

Merged
dhermes merged 2 commits intogoogleapis:masterfrom
dhermes:remove-gcloud-vendor
Apr 9, 2015
Merged

Remove gcloud vendor and just use apitools code#811
dhermes merged 2 commits intogoogleapis:masterfrom
dhermes:remove-gcloud-vendor

Conversation

@dhermes
Copy link
Contributor

@dhermes dhermes commented Apr 9, 2015

See #808 for previous discussion.

Fixes #755.

Labeled dont-merge for now because it depends on an un-released fix in apitools.

/cc @craigcitro

@dhermes dhermes added api: storage Issues related to the Cloud Storage API. packaging do not merge Indicates a pull request not ready for merge, due to either quality or timing. labels Apr 9, 2015
@googlebot googlebot added the cla: yes This human has signed the Contributor License Agreement. label Apr 9, 2015
@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling f31ae34 on dhermes:remove-gcloud-vendor into 41b5b72 on GoogleCloudPlatform:master.

@craigcitro
Copy link
Contributor

and since the other PR is closed -- apitools release is done, so no more worry there.

@dhermes dhermes force-pushed the remove-gcloud-vendor branch from f31ae34 to 79332e1 Compare April 9, 2015 16:31
@dhermes
Copy link
Contributor Author

dhermes commented Apr 9, 2015

Thanks for the release Craig! @tseaver PTAL, dont-merge label removed.

@dhermes dhermes removed the do not merge Indicates a pull request not ready for merge, due to either quality or timing. label Apr 9, 2015
@coveralls
Copy link

Coverage Status

Changes Unknown when pulling 79332e1 on dhermes:remove-gcloud-vendor into * on GoogleCloudPlatform:master*.

@tseaver
Copy link
Contributor

tseaver commented Apr 9, 2015

LGTM

dhermes added a commit that referenced this pull request Apr 9, 2015
Remove gcloud vendor and just use `apitools` code
@dhermes dhermes merged commit f08e71b into googleapis:master Apr 9, 2015
@dhermes
Copy link
Contributor Author

dhermes commented Apr 9, 2015

@tseaver I'm gonna cut a release today or tomorrow

Stay in the 0.4 series or go to 0.5.0? (I vote the latter.)

@tseaver
Copy link
Contributor

tseaver commented Apr 9, 2015

I'd go with 0.5.0: we're including a new API, for instance.

@dhermes dhermes deleted the remove-gcloud-vendor branch April 9, 2015 17:56
parthea pushed a commit that referenced this pull request Aug 21, 2025
Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>
parthea pushed a commit that referenced this pull request Sep 16, 2025
Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>
parthea added a commit that referenced this pull request Sep 18, 2025
* fix(deps): require packaging >= 22.0

* require packaging >= 22.0

* fix(deps): require google-cloud-bigquery 3.4.2

* testing numpy

* fix(deps): require numpy >=1.18.1
parthea pushed a commit that referenced this pull request Nov 24, 2025
parthea pushed a commit that referenced this pull request Nov 24, 2025
Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>
parthea pushed a commit that referenced this pull request Nov 24, 2025
* feat: expose Firestore PITR fields in Database to stable
feat: expose Firestore snapshot_time field in export API to stable
feat: expose Firestore namespace ID fields in import/export APIs to stable
docs: assorted typo fixes and whitespace updates

PiperOrigin-RevId: 587811576

Source-Link: googleapis/googleapis@fbe1c8e

Source-Link: googleapis/googleapis-gen@5fe704d
Copy-Tag: eyJwIjoiLmdpdGh1Yi8uT3dsQm90LnlhbWwiLCJoIjoiNWZlNzA0ZDk0ZmEyZDlhMWRjZTc1Mjk0MmI3MzA4ODczMTI0YjdkZCJ9

* 🦉 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>
parthea pushed a commit that referenced this pull request Nov 24, 2025
Source-Link: googleapis/synthtool@febaccc
Post-Processor: gcr.io/cloud-devrel-public-resources/owlbot-python:latest@sha256:caffe0a9277daeccc4d1de5c9b55ebba0901b57c2f713ec9c876b0d4ec064f61

Co-authored-by: Owl Bot <gcf-owl-bot[bot]@users.noreply.github.com>
parthea pushed a commit that referenced this pull request Nov 25, 2025
Source-Link: googleapis/synthtool@febaccc
Post-Processor: gcr.io/cloud-devrel-public-resources/owlbot-python:latest@sha256:caffe0a9277daeccc4d1de5c9b55ebba0901b57c2f713ec9c876b0d4ec064f61

Co-authored-by: Owl Bot <gcf-owl-bot[bot]@users.noreply.github.com>
parthea pushed a commit that referenced this pull request Mar 6, 2026
…810)

Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly:
- [x] Make sure to open an issue as a [bug/issue](https://github.com/googleapis/python-bigquery/issues/new/choose) before writing your code!  That way we can discuss the change, evaluate designs, and agree on the general idea
- [x] Ensure the tests and linter pass
- [x] Code coverage does not decrease (if any source code was changed)
- [x] Appropriate docs were updated (if necessary)

Fixes #811.
parthea pushed a commit that referenced this pull request Mar 6, 2026
parthea added a commit that referenced this pull request Mar 9, 2026
Co-authored-by: Leah E. Cole <6719667+leahecole@users.noreply.github.com>
Co-authored-by: Anthonios Partheniou <partheniou@google.com>
parthea pushed a commit that referenced this pull request Mar 9, 2026
Samples are provided for INSERT, DELETE, and UPDATE in both GoogleSQL and PostgreSQL dialects. To provide a more compelling example for the INSERT case, a generated column has been added in the "create_database" example so that the generated value can be returned in the INSERT examples.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

api: storage Issues related to the Cloud Storage API. cla: yes This human has signed the Contributor License Agreement. packaging

Projects

None yet

Development

Successfully merging this pull request may close these issues.

DISCUSSION: Switch to apitools as a dependency

5 participants