History

Joe Kimmel 906cc96b59 Upgrade docker (#2440 ) * somehow now the only thing that doesnt work is devices.Device Signed-off-by: Joe Kimmel <jkimmel@vmware.com> * this gets rid of all the compiler errors in the vendored code Signed-off-by: Joe Kimmel <jkimmel@vmware.com> * fixed some things but a bunch of tests and maybe some compiler steps are still failing Signed-off-by: Joe Kimmel <jkimmel@vmware.com> * all the things i figured out how to fix so far Signed-off-by: Joe Kimmel <jkimmel@vmware.com> * guess i had to redo go mods after rebasing again Signed-off-by: Joe Kimmel <jkimmel@vmware.com> * update docker constants to be SHOUTY CASE now Signed-off-by: Joe Kimmel <jkimmel@vmware.com> * include DestPath in resolveEnv Signed-off-by: Joe Kimmel <jkimmel@vmware.com> * fix one mistake in Docker lib upgrade and some typos/deprecations in the file Signed-off-by: Joe Kimmel <jkimmel@vmware.com> * last changes (hopefully) to update to new docker libs Signed-off-by: Joe Kimmel <jkimmel@vmware.com> --------- Signed-off-by: Joe Kimmel <jkimmel@vmware.com>		2023-03-23 20:34:25 -04:00
..
optional	fix deps	2018-08-01 13:02:54 -07:00
trace	Bump deps (#1885 )	2022-01-21 13:59:16 -05:00
version	Bump deps (#1885 )	2022-01-21 13:59:16 -05:00
.repo-metadata-full.json	Upgrade docker (#2440 )	2023-03-23 20:34:25 -04:00
README.md	Upgrade docker (#2440 )	2023-03-23 20:34:25 -04:00
annotate.go	fix(executor): make pax tar builds reproducible again (#2384 )	2023-03-21 18:08:29 -04:00
cloudbuild.yaml	Upgrade docker (#2440 )	2023-03-23 20:34:25 -04:00
retry.go	Bump deps (#1885 )	2022-01-21 13:59:16 -05:00

README.md

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.