Follow instructions in OwlBot Usage Guide - “How will I test my .github/.OwlBot.yaml file” using the instructions for split repositories. Note, if you replace step 2 with a clone of your own fork of the googleapis/googleapis-gen.git repo, you can see how changes in your forked googleapis-gen repo are eventually propagated through to the library without making changes to the protos. Lack of permissions may also force you to clone a fork instead of the repo.
After following these steps the generated code will have replaced corresponding files in the google-cloud-go repo.
You can verify the name of the docker container name can be found in the .github/OwlBot.yaml and github/OwlBot.lock.yaml files.
In the google-cloud-go root directory:
docker pull gcr.io/cloud-devrel-public-resources/owlbot-go:latest docker run --user $(id -u):$(id -g) --rm -v $(pwd):/repo -w /repo gcr.io/cloud-devrel-public-resources/owlbot-go:latest
After making changes to the post-processor, you need to publish a new version of the post-processor docker container and manually update the which version of the post-processor is used by OwlBot. To do this you need to update the SHA in the OwlBot lock file.
In your google-cloud-go repo, create a branch.
Make changes to the post-processor.
Test your changes. You can run the post-processor locally on selected clients or on all of the clients in the root directory. If the branch flag is not set to a non-empty value, the post-processor will exit early without changes. In the google-cloud-go/internal/postprocessor directory:
go run . -client-root="../.." -googleapis-dir="/path/to/local/googleapis" -branch="my-branch"
To test only selected clients:
go run . -client-root="../.." -googleapis-dir="/path/to/local/googleapis" -branch="my-branch" -dirs="accessapproval,asset"
Clean up any changes made by post-processor test runs in the previous step.
Commit your changes.
Open your PR and respond to feedback.
Once your PR is complete (but before merging it!), rebuild the post-processor docker image from your local branch using the google-cloud-go/internal/cloudbuild.yaml Cloud Build configuration. In the google-cloud-go root directory:
gcloud builds submit --project=cloud-devrel-kokoro-resources --config=internal/cloudbuild.yaml
Read the SHA of the latest post-processor docker image. In any location:
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
In your branch, update the SHA of the post-processor docker image in google-cloud-go/.github/.OwlBot.lock.yaml. Commit and push the change to your PR.
Note: OwlBot will eventually open a pull request to update the SHA if it discovers a new version of the container.
After your PR is approved and CI is green, merge your changes.
The post-processor initializes new modules by generating the required files internal/version.go, go.mod, README.md and CHANGES.md.
To add a new module, add the directory name of the module to modules in google-cloud-go/internal/postprocessor/config.yaml. Please maintain alphabetical ordering of the module names.