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

Update cloud.google.com/go/pubsub and supporting libraries #29353

Merged
merged 1 commit into from
Dec 9, 2021

Conversation

andrewkroh
Copy link
Member

What does this PR do?

Moving from cloud.google.com/go/pubsub v1.3.1 to v1.17.1.

Updating via go get cloud.google.com/go/pubsub.

Relates #29352

Why is it important?

Pull in bug fixes from third-party library.

Checklist

  • My code follows the style guidelines of this project
    - [ ] I have commented my code, particularly in hard-to-understand areas
    - [ ] I have made corresponding changes to the documentation
    - [ ] I have made corresponding change to the default configuration files
    - [ ] I have added tests that prove my fix is effective or that my feature works
  • I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

Related issues

@elasticmachine
Copy link
Collaborator

Pinging @elastic/security-external-integrations (Team:Security-External Integrations)

@botelastic botelastic bot added needs_team Indicates that the issue/PR needs a Team:* label and removed needs_team Indicates that the issue/PR needs a Team:* label labels Dec 8, 2021
@mergify
Copy link
Contributor

mergify bot commented Dec 8, 2021

This pull request does not have a backport label. Could you fix it @andrewkroh? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

  • backport-v./d./d./d is the label to automatically backport to the 7./d branch. /d is the digit

NOTE: backport-skip has been added to this pull request.

@mergify mergify bot added the backport-skip Skip notification from the automated backport with mergify label Dec 8, 2021
Moving from v1.3.1 to v1.17.1.

Updating via `go get cloud.google.com/go/pubsub`.

Relates elastic#29352
@andrewkroh andrewkroh force-pushed the feature/update-pubsub branch from c365652 to 1fb353e Compare December 8, 2021 20:29
@andrewkroh andrewkroh added backport-v7.16.0 Automated backport with mergify backport-v8.0.0 Automated backport with mergify bug and removed backport-skip Skip notification from the automated backport with mergify labels Dec 8, 2021
@elasticmachine
Copy link
Collaborator

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS
Pipeline View Test View Changes Artifacts preview preview

Expand to view the summary

Build stats

  • Start Time: 2021-12-08T20:30:20.321+0000

  • Duration: 201 min 12 sec

  • Commit: 1fb353e

Test stats 🧪

Test Results
Failed 0
Passed 48583
Skipped 4276
Total 52859

💚 Flaky test report

Tests succeeded.

🤖 GitHub comments

To re-run your PR in the CI, just comment with:

  • /test : Re-trigger the build.

  • /package : Generate the packages and run the E2E tests.

  • /beats-tester : Run the installation tests with beats-tester.

  • run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

@andrewkroh andrewkroh added backport-skip Skip notification from the automated backport with mergify and removed backport-v8.0.0 Automated backport with mergify backport-v7.16.0 Automated backport with mergify labels Dec 9, 2021
@andrewkroh
Copy link
Member Author

I will backport this if I can confirm that it fixes the bug we are seeing in #29352.

@andrewkroh andrewkroh merged commit 4154447 into elastic:master Dec 9, 2021
@andrewkroh
Copy link
Member Author

andrewkroh commented Dec 9, 2021

@Mergifyio backport 7.16

(opening a PR to run tests on 7.16, not planning to merge yet)

@mergify
Copy link
Contributor

mergify bot commented Dec 9, 2021

backport 7.16

✅ Backports have been created

andrewkroh added a commit that referenced this pull request Dec 9, 2021
Moving from v1.3.1 to v1.17.1.

Updating via `go get cloud.google.com/go/pubsub`.

Relates #29352
andrewkroh added a commit that referenced this pull request Dec 16, 2021
…29369)

Moving from v1.3.1 to v1.17.1.

Updating via `go get cloud.google.com/go/pubsub`.

Relates #29352

Co-authored-by: Andrew Kroh <andrew.kroh@elastic.co>
@andrewkroh
Copy link
Member Author

@Mergifyio backport 8.0

@mergify
Copy link
Contributor

mergify bot commented Dec 16, 2021

backport 8.0

✅ Backports have been created

andrewkroh added a commit that referenced this pull request Dec 16, 2021
Moving from v1.3.1 to v1.17.1.

Updating via `go get cloud.google.com/go/pubsub`.

Relates #29352

(cherry picked from commit 4154447)
andrewkroh added a commit that referenced this pull request Dec 17, 2021
…29471)

Moving from v1.3.1 to v1.17.1.

Updating via `go get cloud.google.com/go/pubsub`.

Relates #29352

(cherry picked from commit 4154447)

Co-authored-by: Andrew Kroh <andrew.kroh@elastic.co>
@ruflin
Copy link
Contributor

ruflin commented Jan 19, 2022

@Mergifyio backport 7.17

@mergify
Copy link
Contributor

mergify bot commented Jan 19, 2022

backport 7.17

✅ Backports have been created

mergify bot pushed a commit that referenced this pull request Jan 19, 2022
Moving from v1.3.1 to v1.17.1.

Updating via `go get cloud.google.com/go/pubsub`.

Relates #29352

(cherry picked from commit 4154447)

# Conflicts:
#	go.sum
@ruflin
Copy link
Contributor

ruflin commented Jan 19, 2022

@andrewkroh @efd6 This did go into 7.16 but not 7.17. I'm pretty sure it should also be in 7.17. Can you check that the following PR is merged if needed? #29906

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport-skip Skip notification from the automated backport with mergify bug Filebeat Filebeat
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants