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

Add entry for salesforce input in agentbeat spec #39770

Merged

Conversation

kush-elastic
Copy link
Collaborator

  • Enhancement

Description

  • As we have introduced new salesforce input in filebeat. for further use cases in elastic-agent we need to add new input entry in agentbeat spec file of beats.

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

@kush-elastic kush-elastic requested a review from a team as a code owner May 30, 2024 08:58
@kush-elastic kush-elastic requested review from belimawr and rdner May 30, 2024 08:58
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label May 30, 2024
Copy link
Contributor

mergify bot commented May 30, 2024

This pull request does not have a backport label.
If this is a bug or security fix, could you label this PR @kush-elastic? 🙏.
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-v8./d.0 is the label to automatically backport to the 8./d branch. /d is the digit

@kush-elastic kush-elastic added x-pack Issues and pull requests for X-Pack features. Team:Obs-InfraObs Label for the Observability Infrastructure Monitoring team labels May 30, 2024
@botelastic botelastic bot removed the needs_team Indicates that the issue/PR needs a Team:* label label May 30, 2024
@kush-elastic kush-elastic merged commit 98202e4 into elastic:main May 30, 2024
8 checks passed
@kush-elastic kush-elastic added the backport-v8.14.0 Automated backport with mergify label May 30, 2024
mergify bot pushed a commit that referenced this pull request May 30, 2024
kush-elastic added a commit that referenced this pull request May 31, 2024
(cherry picked from commit 98202e4)

Co-authored-by: Kush Rana <89848966+kush-elastic@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport-v8.14.0 Automated backport with mergify Team:Obs-InfraObs Label for the Observability Infrastructure Monitoring team x-pack Issues and pull requests for X-Pack features.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants