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

feat(all): auto-regenerate gapics #2849

Merged
merged 9 commits into from Sep 15, 2020
Merged

feat(all): auto-regenerate gapics #2849

merged 9 commits into from Sep 15, 2020

Conversation

@yoshi-automation
Copy link
Contributor

@yoshi-automation yoshi-automation commented Sep 12, 2020

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#443

@google-cla google-cla bot added the cla: yes label Sep 12, 2020
yoshi-automation added a commit to googleapis/go-genproto that referenced this pull request Sep 12, 2020
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#2849
codyoss pushed a commit to googleapis/go-genproto that referenced this pull request Sep 14, 2020
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#2849
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#443
@yoshi-automation yoshi-automation marked this pull request as ready for review Sep 14, 2020
@yoshi-automation yoshi-automation force-pushed the regen_gocloud branch from e93fc0b to 1f7aea8 Sep 14, 2020
@codyoss
Copy link
Member

@codyoss codyoss commented Sep 14, 2020

Filed: golang/go#41383 for the broken build. Looks like we should make sure to pull in an older version of tools in the samples repo though. cc @tbpg

Edit: The problem is with the indirect version being pulled in here.

@codyoss codyoss mentioned this pull request Sep 14, 2020
0 of 1 task complete
@yoshi-automation yoshi-automation force-pushed the regen_gocloud branch 2 times, most recently from daeda11 to 7746415 Sep 14, 2020
@yoshi-automation yoshi-automation force-pushed the regen_gocloud branch from 7746415 to b6ddb89 Sep 15, 2020
This reverts commit b6ddb89.
@yoshi-automation yoshi-automation force-pushed the regen_gocloud branch from 39b42bb to 6dbdcf5 Sep 15, 2020
This reverts commit 6dbdcf5.
@yoshi-automation yoshi-automation force-pushed the regen_gocloud branch from d2ada93 to 23da84b Sep 15, 2020
@yoshi-automation yoshi-automation force-pushed the regen_gocloud branch from 7cc1f97 to c64844c Sep 15, 2020
@google-cla
Copy link

@google-cla google-cla bot commented Sep 15, 2020

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 and removed cla: yes labels Sep 15, 2020
codyoss added 2 commits Sep 15, 2020
@google-cla
Copy link

@google-cla google-cla bot commented Sep 15, 2020

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.

1 similar comment
@google-cla
Copy link

@google-cla google-cla bot commented Sep 15, 2020

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 added cla: yes and removed cla: no labels Sep 15, 2020
@codyoss codyoss merged commit 6a541c2 into master Sep 15, 2020
3 checks passed
3 checks passed
@google-cla
cla/google CLAs have been manually verified by Googler who has set the 'cla: yes' label
@conventional-commit-lint-gcf
conventionalcommits.org
Details
@kokoro-team
kokoro Kokoro CI build successful
Details
@codyoss codyoss deleted the regen_gocloud branch Sep 15, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

2 participants