Skip to content

Commit

Permalink
chore: manually regen cloudbuild do to breaking changes (#4476)
Browse files Browse the repository at this point in the history 
* chore: manually regen cloudbuild do to breaking changes

I had to manually manipulate the old code directory so that it
could compile. In the future this makes me question if v2 directories
make sense for generated code were we must always match the proto
spec for code to actually work.

I also include a few changes to the generator the helped me regen
and debug what was wrong.
Changes:

feat(cloudbuild/apiv1): Implementation of Build Failure Info: - Added message FailureInfo field
  PiperOrigin-RevId: 385847244
  Source-Link: googleapis/googleapis@f84d1e2

feat(cloudbuild/apiv1): add a WorkerPools API
  BREAKING CHANGE: Proto had a prior definitions of WorkerPool resources which were never supported. This change replaces those resources with definitions that are currently supported.

  Committer: @mwiczer
  PiperOrigin-RevId: 385610622
  Source-Link: googleapis/googleapis@7a1fb83
  • Loading branch information
@codyoss
codyoss authored Jul 21, 2021
1 parent 8936bc3 commit 19ea3f8
Show file tree
Hide file tree
Showing 12 changed files with 552 additions and 1,387 deletions.
171 changes: 165 additions & 6 deletions cloudbuild/apiv1/cloud_build_client.go
View file

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

Loading

0 comments on commit 19ea3f8

Please sign in to comment.