tree: 7755757914b98cc46dd535abf8e322b35f283e7e [path history] [tgz]
  1. actions/
  2. aliasfix/
  3. aliasgen/
  4. btree/
  5. carver/
  6. detect/
  7. examples/
  8. fields/
  9. gapicgen/
  10. generated/
  11. gensnippets/
  12. godocfx/
  13. kokoro/
  14. leakcheck/
  15. optional/
  16. postprocessor/
  17. pretty/
  18. protostruct/
  19. pubsub/
  20. testutil/
  21. trace/
  22. tracecontext/
  23. uid/
  24. version/
  25. .repo-metadata-full.json
  26. annotate.go
  27. annotate_test.go
  28. cloudbuild.yaml
  29. README.md
  30. retry.go
  31. retry_test.go
internal/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

The cloudbuild.yaml Cloud Build configuration currently supports:

  • Building a docker container from the internal/postprocessor/Dockerfile.

The build can be run locally in the google-cloud-go root directory:

gcloud builds submit --project=cloud-devrel-kokoro-resources --config=internal/cloudbuild.yaml

See the postprocessor/README for instructions regarding updating the post-processor docker container.

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.

See the postprocessor/README for detailed instructions.

Note: OwlBot will eventually open a pull request to update this value if it discovers a new version of the container.