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

Bump github.com/elastic/go-sfdc to master@8e176480d727 #41192

Merged
merged 2 commits into from
Oct 11, 2024

Conversation

shmsr
Copy link
Member

@shmsr shmsr commented Oct 10, 2024

Proposed commit message

See elastic/go-sfdc#3 for more details on why dependency was bumped to master@8e176480d727

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.

How to test this PR locally

Run filebeat module and use JWT authentication to validate if connection to Salesforce is successful or not.

Related issues

@shmsr shmsr added the bugfix label Oct 10, 2024
@shmsr shmsr requested a review from a team October 10, 2024 13:19
@shmsr shmsr self-assigned this Oct 10, 2024
@shmsr shmsr requested a review from a team as a code owner October 10, 2024 13:19
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Oct 10, 2024
@botelastic
Copy link

botelastic bot commented Oct 10, 2024

This pull request doesn't have a Team:<team> label.

Copy link
Contributor

mergify bot commented Oct 10, 2024

This pull request does not have a backport label.
If this is a bug or security fix, could you label this PR @shmsr? 🙏.
For such, you'll need to label your PR with:

  • The upcoming major version of the Elastic Stack
  • The upcoming minor version of the Elastic Stack (if you're not pushing a breaking change)

To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

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

Copy link
Contributor

mergify bot commented Oct 10, 2024

backport-8.x has been added to help with the transition to the new branch 8.x.
If you don't need it please use backport-skip label and remove the backport-8.x label.

@mergify mergify bot added the backport-8.x Automated backport to the 8.x branch with mergify label Oct 10, 2024
@shmsr shmsr changed the title Bump github.com/elastic/go-sfdc to master@8e176480d727 Bump github.com/elastic/go-sfdc to master@8e176480d727 Oct 10, 2024
@pierrehilbert pierrehilbert merged commit a25c5a5 into elastic:main Oct 11, 2024
142 checks passed
mergify bot pushed a commit that referenced this pull request Oct 11, 2024
* Bump github.com/elastic/go-sfdc to master@8e176480d727

* Add changelog and update NOTICE

(cherry picked from commit a25c5a5)
pierrehilbert pushed a commit that referenced this pull request Oct 11, 2024
…41201)

* Bump github.com/elastic/go-sfdc to master@8e176480d727

* Add changelog and update NOTICE

(cherry picked from commit a25c5a5)

Co-authored-by: subham sarkar <subham.sarkar@elastic.co>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport-8.x Automated backport to the 8.x branch with mergify bugfix needs_team Indicates that the issue/PR needs a Team:* label
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants