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 EventHub user properties in @metadata object #66

Merged
merged 5 commits into from
Jun 1, 2021

Conversation

mirolessev
Copy link
Contributor

Add EventHub user properties in @metadata object

  • enhancement

Release notes

What does this PR do?

Why is it important/What is the impact to the user?

This PR add EventHub user properties in @metadata object.

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 (and/or docker env variables)
  • I have added tests that prove my fix is effective or that my feature works

Author's Checklist

  • [ ]

How to test this PR locally

  1. Create EventHub message
    • Add body data (any JSON Object)
    • Add user properties as a metadata
  2. Send message to EventHub
  3. Consume message from EventHub and check [@metadata][user_properties]

Related issues

Use cases

You can access EventHub metadata in logstash pipeline

Screenshots

Logs

Add EventHub user properties in @metadata object
@cla-checker-service
Copy link

cla-checker-service bot commented May 21, 2021

💚 CLA has been signed

@robbavey
Copy link
Contributor

@mirolessev Can you please sign the CLA? it can be found here - https://www.elastic.co/contributor-agreement

@mirolessev
Copy link
Contributor Author

mirolessev commented May 28, 2021 via email

Copy link
Contributor

@robbavey robbavey left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Thank you the contribution - I tested this locally, and it worked as advertised.

Would you mind also adding an entry to the changelog, and updating the version?

Once that is done, I can go ahead and merge the code, and publish the plugin

@mirolessev
Copy link
Contributor Author

mirolessev commented Jun 1, 2021 via email

Copy link
Contributor

@robbavey robbavey left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would you mind changing the versions to 1.3.0 - typically for changes where we add features to a plugin, we update the minor version. Apologies for not mentioning this in my initial comment. once that is done, we are good to go, and I'll go ahead and merge and publish

CHANGELOG.md Outdated Show resolved Hide resolved
VERSION Outdated Show resolved Hide resolved
CHANGELOG.md Outdated Show resolved Hide resolved
mirolessev and others added 2 commits June 1, 2021 23:01
Co-authored-by: Rob Bavey <rob.bavey@elastic.co>
Co-authored-by: Rob Bavey <rob.bavey@elastic.co>
@robbavey robbavey merged commit dcb85da into logstash-plugins:master Jun 1, 2021
@robbavey
Copy link
Contributor

robbavey commented Jun 2, 2021

@mirolessev Thank you for your contribution - version 1.3.0 of this plugin with your update in it has been published!

@aaron-dsouza-zz
Copy link

@robbavey will this updated plugin be made part of the logstash docker image?

@roaksoax
Copy link

roaksoax commented Jun 8, 2021

@aaron-dsouza it will for 7.14.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants