-
Notifications
You must be signed in to change notification settings - Fork 1
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 support for building new JSON events with jmespath #18
Comments
Not sure we still need this given the |
Scott, you are on the watchers list for this repo. That's why you are getting emails: I don't think I can remove you. |
Hey Scott, its just a Github login, so you should be able to reset your password.
Brian Kennedy
CTO, Intelligent Operations
***@***.***
| Mobile:(302) 482-4571
www.cdillc.com<https://www.cdillc.com/>
***@***.***<https://www.cdillc.com/>
***@***.***<https://twitter.com/cdillc> ***@***.*** <https://www.linkedin.com/company/cdi-llc/> ***@***.*** <https://www.instagram.com/cdillc/?hl=en> ***@***.*** <https://www.facebook.com/cdillc/> ***@***.*** <https://www.youtube.com/channel/UCx99j8mutlnYuhaP9Cw_dEQ>
From: socamb ***@***.***>
Sent: Thursday, November 3, 2022 12:23 PM
To: Kintyre/jmespath ***@***.***>
Cc: Subscribed ***@***.***>
Subject: Re: [Kintyre/jmespath] Add support for building new JSON events with jmespath (#18)
When I try to unsubscribe or go to that link, it wants me to login. I do not remember my login credentials. I don't get these emails often, so it is not a bother, I just wanted you to know about it in case something is going on that is not public.
Please advise as to what you want me to do, if anything.
Scott
From: Lowell Alleman ***@***.***<mailto:***@***.***>>
Sent: Thursday, November 3, 2022 11:44 AM
To: Kintyre/jmespath ***@***.***<mailto:***@***.***>>
Cc: socamb ***@***.***<mailto:***@***.***>>; Comment ***@***.***<mailto:***@***.***>>
Subject: Re: [Kintyre/jmespath] Add support for building new JSON events with jmespath (#18)
Scott, you are on the watchers list for this repo. That's why you are getting emails:
https://github.com/Kintyre/jmespath/watchers<https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FKintyre%2Fjmespath%2Fwatchers&data=05%7C01%7C%7Cc500b8fdfa264c11b44808dabdb243dc%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638030870584064584%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=3Xr1n5BZBr6IOQ6%2BIf7lRYUNdq0Te9L57pN3aoqKdJ4%3D&reserved=0<https://github.com/Kintyre/jmespath/watchers%3chttps:/nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FKintyre%2Fjmespath%2Fwatchers&data=05%7C01%7C%7Cc500b8fdfa264c11b44808dabdb243dc%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638030870584064584%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=3Xr1n5BZBr6IOQ6%2BIf7lRYUNdq0Te9L57pN3aoqKdJ4%3D&reserved=0>>
I don't think I can remove you.
-
Reply to this email directly, view it on GitHub<https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FKintyre%2Fjmespath%2Fissues%2F18%23issuecomment-1302306209&data=05%7C01%7C%7Cc500b8fdfa264c11b44808dabdb243dc%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638030870584064584%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=jKP4ByfZS1P8vheUaRKuM%2ByGR0jdApC1ESMap%2BHxjlM%3D&reserved=0>, or unsubscribe<https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FADI4ZBKIFSIWN2F45BL6FE3WGPMU7ANCNFSM4GF2EYYQ&data=05%7C01%7C%7Cc500b8fdfa264c11b44808dabdb243dc%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638030870584064584%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=KIr8FBkAot8j4ustCyS10jj6QhycVlLzhk9yRg2vmTg%3D&reserved=0>.
You are receiving this because you commented.Message ID: ***@***.***<mailto:***@***.***>>
—
Reply to this email directly, view it on GitHub<#18 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ABADWJ7YJTSHZHTAK3FGPQDWGPRHLANCNFSM4GF2EYYQ>.
You are receiving this because you are subscribed to this thread.Message ID: ***@***.******@***.***>>
NOTICE: This electronic mail message and all attachments transmitted with it are intended solely for the use of the addressee and may contain legally privileged proprietary and confidential information. If the reader of this message is not the intended recipient, or if you are an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution, copying, or other use of this message or its attachments is strictly prohibited. If you have received this message in error, please notify the sender immediately by replying to this message and delete it from your computer.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Consider allowing
input=
to be a wildcarded field as well. All of the field(s) that match would be passed in as top-level keys.So if you had a single event with fields like this:
Could could run a command like so:
And the output value for
rec
would looks something like:If one of the
rec.*
fields already contains a JSON string, then thefrom_string()
function can be used to convert and, if necessary, further manipulate the record.BTW: I'm not even sure the syntax of the JMESPath example is legit. Good luck future self!
The text was updated successfully, but these errors were encountered: