60e55b5ed3
Bumps [cloud.google.com/go/compute](https://github.com/googleapis/google-cloud-go) from 1.10.0 to 1.19.3. - [Release notes](https://github.com/googleapis/google-cloud-go/releases) - [Changelog](https://github.com/googleapis/google-cloud-go/blob/main/documentai/CHANGES.md) - [Commits](https://github.com/googleapis/google-cloud-go/compare/kms/v1.10.0...compute/v1.19.3) --- updated-dependencies: - dependency-name: cloud.google.com/go/compute dependency-type: direct:production update-type: version-update:semver-minor ... Migrated to the new version by following https://github.com/googleapis/google-cloud-go/blob/main/migration.md Co-authored-by: Tomáš Hozza <thozza@redhat.com> Signed-off-by: dependabot[bot] <support@github.com> Signed-off-by: Tomáš Hozza <thozza@redhat.com> |
||
|---|---|---|
| .. | ||
| optional | ||
| trace | ||
| version | ||
| .repo-metadata-full.json | ||
| annotate.go | ||
| cloudbuild.yaml | ||
| README.md | ||
| retry.go | ||
Internal
This directory contains internal code for cloud.google.com/go packages.
.repo-metadata-full.json
.repo-metadata-full.json contains metadata about the packages in this repo. It
is generated by internal/gapicgen/generator. It's processed by external tools
to build lists of all of the packages.
Don't make breaking changes to the format without consulting with the external tools.
One day, we may want to create individual .repo-metadata.json files next to
each package, which is the pattern followed by some other languages. External
tools would then talk to pkg.go.dev or some other service to get the overall
list of packages and use the .repo-metadata.json files to get the additional
metadata required. For now, .repo-metadata-full.json includes everything.
cloudbuild.yaml
To kick off a build locally run from the repo root:
gcloud builds submit --project=cloud-devrel-kokoro-resources --config=internal/cloudbuild.yaml
Updating OwlBot SHA
You may want to manually update the which version of the post processor will be used -- to do this you need to update the SHA in the OwlBot lock file. Start by running the following commands:
docker pull gcr.io/cloud-devrel-public-resources/owlbot-go:latest
docker inspect --format='{{index .RepoDigests 0}}' gcr.io/cloud-devrel-public-resources/owlbot-go:latest
This will give you a SHA. You can use this value to update the value in
.github/.OwlBot.lock.yaml.
Note: OwlBot will eventually open a pull request to update this value if it discovers a new version of the container.