Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(all): auto-regenerate gapics #4355

Merged
merged 5 commits into from Jun 30, 2021
Merged

chore(all): auto-regenerate gapics #4355

merged 5 commits into from Jun 30, 2021

Conversation

yoshi-automation
Copy link
Contributor

This is an auto-generated regeneration of the gapic clients by
cloud.google.com/go/internal/gapicgen. Once the corresponding genproto PR is
submitted, genbot will update this PR with a newer dependency to the newer
version of genproto and assign reviewers to this PR.

If you have been assigned to review this PR, please:

  • Ensure that the version of genproto in go.mod has been updated.
  • Ensure that CI is passing. If it's failing, it requires your manual attention.
  • Approve and submit this PR if you believe it's ready to ship.

Corresponding genproto PR: googleapis/go-genproto#628

Changes:

feat(pubsub): Adding subscription properties to streaming pull response in third party pubsub.proto.
PiperOrigin-RevId: 382318016
Source-Link: googleapis/googleapis@e9b2b61

fix!(datastream): Remove DiscoverConnectionProfile method signature which didn't populate the request sufficiently fix!: Overhaul resource annotations, some of which were incorrect and some of which were just non-ideal
PiperOrigin-RevId: 382316023
Source-Link: googleapis/googleapis@125799d

This is an auto-generated regeneration of the gapic clients by
cloud.google.com/go/internal/gapicgen. Once the corresponding genproto PR is
submitted, genbot will update this PR with a newer dependency to the newer
version of genproto and assign reviewers to this PR.

If you have been assigned to review this PR, please:

- Ensure that the version of genproto in go.mod has been updated.
- Ensure that CI is passing. If it's failing, it requires your manual attention.
- Approve and submit this PR if you believe it's ready to ship.

Corresponding genproto PR: googleapis/go-genproto#628

Changes:

feat(pubsub): Adding subscription properties to streaming pull response in third party pubsub.proto.
  PiperOrigin-RevId: 382318016
  Source-Link: googleapis/googleapis@e9b2b61

fix!(datastream): Remove DiscoverConnectionProfile method signature which didn't populate the request sufficiently fix!: Overhaul resource annotations, some of which were incorrect and some of which were just non-ideal
  PiperOrigin-RevId: 382316023
  Source-Link: googleapis/googleapis@125799d
@google-cla google-cla bot added the cla: yes This human has signed the Contributor License Agreement. label Jun 30, 2021
yoshi-automation added a commit to googleapis/go-genproto that referenced this pull request Jun 30, 2021
This is an auto-generated regeneration of the .pb.go files by
cloud.google.com/go/internal/gapicgen. Once this PR is submitted, genbot will
update the corresponding PR to depend on the newer version of go-genproto, and
assign reviewers. Whilst this or any regen PR is open in go-genproto, genbot
will not create any more regeneration PRs. If all regen PRs are closed,
gapicgen will create a new set of regeneration PRs once per night.

If you have been assigned to review this PR, please:

- Ensure that CI is passing. If it's failing, it requires your manual attention.
- Approve and submit this PR if you believe it's ready to ship. That will prompt
genbot to assign reviewers to the google-cloud-go PR.

Corresponding google-cloud-go PR: googleapis/google-cloud-go#4355

Changes:

feat: add new FieldBehavior NON_EMPTY_DEFAULT
  PiperOrigin-RevId: 382337225
  Source-Link: googleapis/googleapis@aa136fa

feat(pubsub): Adding subscription properties to streaming pull response in third party pubsub.proto.
  PiperOrigin-RevId: 382318016
  Source-Link: googleapis/googleapis@e9b2b61

chore: regenerate API index

  Source-Link: googleapis/googleapis@490f1e9

fix!(datastream): Remove DiscoverConnectionProfile method signature which didn't populate the request sufficiently fix!: Overhaul resource annotations, some of which were incorrect and some of which were just non-ideal
  PiperOrigin-RevId: 382316023
  Source-Link: googleapis/googleapis@125799d

chore: regenerate API index

  Source-Link: googleapis/googleapis@1c5c56c

chore(ruby): Switch Bazel jobs to use the Ruby gapic-generator 0.9.0
  PiperOrigin-RevId: 382291678
  Source-Link: googleapis/googleapis@c5954ef

chore: regenerate API index

  Source-Link: googleapis/googleapis@2e6b987

chore(ruby): Configure Ruby microgenerator arguments for Resource Manager V3
  PiperOrigin-RevId: 382196988
  Source-Link: googleapis/googleapis@a3c4f2a

chore: regenerate API index

  Source-Link: googleapis/googleapis@34210e9

feat: Data Fusion public protos
  Committer: @alexander-fenster
  PiperOrigin-RevId: 382167046
  Source-Link: googleapis/googleapis@6797726
@snippet-bot
Copy link

snippet-bot bot commented Jun 30, 2021

Here is the summary of possible violations 😱

There are 21 possible violations for not having product prefix.

The end of the violation section. All the stuff below is FYI purposes only.


Here is the summary of changes.

You are about to add 48 region tags.

This comment is generated by snippet-bot.
If you find problems with this result, please file an issue at:
https://github.com/googleapis/repo-automation-bots/issues.
To update this comment, add snippet-bot:force-run label or use the checkbox below:

  • Refresh this comment

codyoss pushed a commit to googleapis/go-genproto that referenced this pull request Jun 30, 2021
This is an auto-generated regeneration of the .pb.go files by
cloud.google.com/go/internal/gapicgen. Once this PR is submitted, genbot will
update the corresponding PR to depend on the newer version of go-genproto, and
assign reviewers. Whilst this or any regen PR is open in go-genproto, genbot
will not create any more regeneration PRs. If all regen PRs are closed,
gapicgen will create a new set of regeneration PRs once per night.

If you have been assigned to review this PR, please:

- Ensure that CI is passing. If it's failing, it requires your manual attention.
- Approve and submit this PR if you believe it's ready to ship. That will prompt
genbot to assign reviewers to the google-cloud-go PR.

Corresponding google-cloud-go PR: googleapis/google-cloud-go#4355

Changes:

feat: add new FieldBehavior NON_EMPTY_DEFAULT
  PiperOrigin-RevId: 382337225
  Source-Link: googleapis/googleapis@aa136fa

feat(pubsub): Adding subscription properties to streaming pull response in third party pubsub.proto.
  PiperOrigin-RevId: 382318016
  Source-Link: googleapis/googleapis@e9b2b61

chore: regenerate API index

  Source-Link: googleapis/googleapis@490f1e9

fix!(datastream): Remove DiscoverConnectionProfile method signature which didn't populate the request sufficiently fix!: Overhaul resource annotations, some of which were incorrect and some of which were just non-ideal
  PiperOrigin-RevId: 382316023
  Source-Link: googleapis/googleapis@125799d

chore: regenerate API index

  Source-Link: googleapis/googleapis@1c5c56c

chore(ruby): Switch Bazel jobs to use the Ruby gapic-generator 0.9.0
  PiperOrigin-RevId: 382291678
  Source-Link: googleapis/googleapis@c5954ef

chore: regenerate API index

  Source-Link: googleapis/googleapis@2e6b987

chore(ruby): Configure Ruby microgenerator arguments for Resource Manager V3
  PiperOrigin-RevId: 382196988
  Source-Link: googleapis/googleapis@a3c4f2a

chore: regenerate API index

  Source-Link: googleapis/googleapis@34210e9

feat: Data Fusion public protos
  Committer: @alexander-fenster
  PiperOrigin-RevId: 382167046
  Source-Link: googleapis/googleapis@6797726
@yoshi-automation yoshi-automation marked this pull request as ready for review June 30, 2021 18:48
@yoshi-automation yoshi-automation requested a review from a team June 30, 2021 18:48
@yoshi-automation yoshi-automation requested review from a team and kolea2 as code owners June 30, 2021 18:48
@google-cla
Copy link

google-cla bot commented Jun 30, 2021

All (the pull request submitter and all commit authors) CLAs are signed, but one or more commits were authored or co-authored by someone other than the pull request submitter.

We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that by leaving a comment that contains only @googlebot I consent. in this pull request.

Note to project maintainer: There may be cases where the author cannot leave a comment, or the comment is not properly detected as consent. In those cases, you can manually confirm consent of the commit author(s), and set the cla label to yes (if enabled on your project).

ℹ️ Googlers: Go here for more info.

@google-cla google-cla bot added cla: no This human has *not* signed the Contributor License Agreement. and removed cla: yes This human has signed the Contributor License Agreement. labels Jun 30, 2021
@codyoss codyoss added cla: yes This human has signed the Contributor License Agreement. and removed cla: no This human has *not* signed the Contributor License Agreement. labels Jun 30, 2021
@google-cla
Copy link

google-cla bot commented Jun 30, 2021

All (the pull request submitter and all commit authors) CLAs are signed, but one or more commits were authored or co-authored by someone other than the pull request submitter.

We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that by leaving a comment that contains only @googlebot I consent. in this pull request.

Note to project maintainer: There may be cases where the author cannot leave a comment, or the comment is not properly detected as consent. In those cases, you can manually confirm consent of the commit author(s), and set the cla label to yes (if enabled on your project).

ℹ️ Googlers: Go here for more info.

@google-cla google-cla bot added cla: no This human has *not* signed the Contributor License Agreement. and removed cla: yes This human has signed the Contributor License Agreement. labels Jun 30, 2021
@google-cla
Copy link

google-cla bot commented Jun 30, 2021

All (the pull request submitter and all commit authors) CLAs are signed, but one or more commits were authored or co-authored by someone other than the pull request submitter.

We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that by leaving a comment that contains only @googlebot I consent. in this pull request.

Note to project maintainer: There may be cases where the author cannot leave a comment, or the comment is not properly detected as consent. In those cases, you can manually confirm consent of the commit author(s), and set the cla label to yes (if enabled on your project).

ℹ️ Googlers: Go here for more info.

@codyoss codyoss removed the cla: no This human has *not* signed the Contributor License Agreement. label Jun 30, 2021
@codyoss codyoss added automerge Merge the pull request once unit tests and other checks pass. cla: yes This human has signed the Contributor License Agreement. labels Jun 30, 2021
@google-cla
Copy link

google-cla bot commented Jun 30, 2021

All (the pull request submitter and all commit authors) CLAs are signed, but one or more commits were authored or co-authored by someone other than the pull request submitter.

We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that by leaving a comment that contains only @googlebot I consent. in this pull request.

Note to project maintainer: There may be cases where the author cannot leave a comment, or the comment is not properly detected as consent. In those cases, you can manually confirm consent of the commit author(s), and set the cla label to yes (if enabled on your project).

ℹ️ Googlers: Go here for more info.

@google-cla google-cla bot added cla: no This human has *not* signed the Contributor License Agreement. and removed cla: yes This human has signed the Contributor License Agreement. labels Jun 30, 2021
@codyoss codyoss added cla: yes This human has signed the Contributor License Agreement. and removed cla: no This human has *not* signed the Contributor License Agreement. labels Jun 30, 2021
@google-cla
Copy link

google-cla bot commented Jun 30, 2021

All (the pull request submitter and all commit authors) CLAs are signed, but one or more commits were authored or co-authored by someone other than the pull request submitter.

We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that by leaving a comment that contains only @googlebot I consent. in this pull request.

Note to project maintainer: There may be cases where the author cannot leave a comment, or the comment is not properly detected as consent. In those cases, you can manually confirm consent of the commit author(s), and set the cla label to yes (if enabled on your project).

ℹ️ Googlers: Go here for more info.

@google-cla google-cla bot added cla: no This human has *not* signed the Contributor License Agreement. and removed cla: yes This human has signed the Contributor License Agreement. labels Jun 30, 2021
@codyoss
Copy link
Member

codyoss commented Jun 30, 2021

The remaining bigquery breakage is for an experimental field, okayed with @shollyman. Manually overriding failing kokoro build.

@codyoss codyoss added cla: yes This human has signed the Contributor License Agreement. and removed cla: no This human has *not* signed the Contributor License Agreement. labels Jun 30, 2021
@codyoss codyoss merged commit 13acf7f into master Jun 30, 2021
@codyoss codyoss deleted the regen_gocloud branch June 30, 2021 21:44
@gcf-merge-on-green gcf-merge-on-green bot removed the automerge Merge the pull request once unit tests and other checks pass. label Jun 30, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cla: yes This human has signed the Contributor License Agreement.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants