| commit | c84e111db5d3f57f4e8fbb5dfff0219d052435a0 | [log] [tgz] |
|---|---|---|
| author | Yoshi Automation Bot <yoshi-automation@google.com> | Fri Jun 17 06:48:17 2022 -0700 |
| committer | GitHub <noreply@github.com> | Fri Jun 17 08:48:17 2022 -0500 |
| tree | 8d88c5e1258d7b81ec31c8e1da5d1de8642c0c8f | |
| parent | d0876076bb09b62a9cfce43bf7e8c7aaecd64dbd [diff] |
chore(all): auto-regenerate gapics (#6207) This is an auto-generated regeneration of the gapic clients by cloud.google.com/go/internal/gapicgen. Once the corresponding genproto PR is submitted, genbot will update this PR with a newer dependency to the newer version of genproto and assign reviewers to this PR. If you have been assigned to review this PR, please: - Ensure that the version of genproto in go.mod has been updated. - Ensure that CI is passing. If it's failing, it requires your manual attention. - Approve and submit this PR if you believe it's ready to ship. Corresponding genproto PR: https://github.com/googleapis/go-genproto/pull/829 Changes: feat(aiplatform): add model_version_id to UploadModelResponse in aiplatform v1 model_service.proto PiperOrigin-RevId: 455486702 Source-Link: https://github.com/googleapis/googleapis/commit/f2e55382d437b3f7463176c95cedc1293c5971fb docs(storage/internal): Clarified how clients should work with resumable uploads docs: Clarified ListNotifications pagination docs: Made "live generation" wording consistent with docs for other Cloud Storage APIs fix: Made negative offsets larger in magnitude that object size return the full object for ReadObject operations fix: Made naming format for Logging.log_bucket be a path rather than raw bucket name, to be consistent with the rest of the API feat: Changed Custom Dual Regions to be specified in a proto message rather than a syntactic encoding within the bucket location feat: Added etag support PiperOrigin-RevId: 455465509 Source-Link: https://github.com/googleapis/googleapis/commit/0470cd6d5019a397cc132b34551a83d2bc309d35 feat(binaryauthorization): Adds a pod_namespace field to pod events created by Continuous Validation, to distinguish pods with the same name that run in different namespaces Committer: @tswift242 PiperOrigin-RevId: 455380856 Source-Link: https://github.com/googleapis/googleapis/commit/1cbacff2f2fe932f91a39d7c1538cb1afc50bd89 feat(video/transcoder): add support for user labels for job and job template PiperOrigin-RevId: 455298767 Source-Link: https://github.com/googleapis/googleapis/commit/a9969d336bc114b5ab1a1c81b91d4495540ea76f
Go packages for Google Cloud Platform services.
import "cloud.google.com/go"
To install the packages on your system, do not clone the repo. Instead:
Change to your project directory:
cd /my/cloud/project
Get the package you want to use. Some products have their own module, so it's best to go get the package(s) you want to use:
$ go get cloud.google.com/go/firestore # Replace with the package you want to use.
NOTE: Some of these packages are under development, and may occasionally make backwards-incompatible changes.
For an updated list of all of our released APIs please see our reference docs.
Our libraries are compatible with at least the three most recent, major Go releases. They are currently compatible with:
By default, each API will use Google Application Default Credentials for authorization credentials used in calling the API endpoints. This will allow your application to run in many environments without requiring explicit configuration.
client, err := storage.NewClient(ctx)
To authorize using a JSON key file, pass option.WithCredentialsFile to the NewClient function of the desired package. For example:
client, err := storage.NewClient(ctx, option.WithCredentialsFile("path/to/keyfile.json"))
You can exert more control over authorization by using the golang.org/x/oauth2 package to create an oauth2.TokenSource. Then pass option.WithTokenSource to the NewClient function: snip:# (auth-ts)
tokenSource := ...
client, err := storage.NewClient(ctx, option.WithTokenSource(tokenSource))
Contributions are welcome. Please, see the CONTRIBUTING document for details.
Please note that this project is released with a Contributor Code of Conduct. By participating in this project you agree to abide by its terms. See Contributor Code of Conduct for more information.