Closed kevinelliott closed 1 year ago
Thanks for the code. The fact that you have a station override bit in the airframes script makes me think about weather the specific json structure field mapping should maybe be moved over there. Let me know if you have an argument either way, otherwise i'll think about it for a bit.
Thanks for the code. The fact that you have a station override bit in the airframes script makes me think about weather the specific json structure field mapping should maybe be moved over there. Let me know if you have an argument either way, otherwise i'll think about it for a bit.
I don't have a compelling argument either way. It was originally put there just in case someone wanted to run multiple instances and have different station ids, but ultimately I think that isn't very beneficial (as it would really just end up sending the same data for multiple station ids for no reason).
Turns out I currently don't have the energy to do any changes. Sorry for the delay. Is this still the current version to be merged?
Turns out I currently don't have the energy to do any changes. Sorry for the delay. Is this still the current version to be merged?
Yes, that would be great! Happy to iterate and add improvements after.
@Sec42 merge away!
merged
This builds on previous work I did to add JSON output to the ACARS parser. It augments the output to be in the format that Airframes is expecting, and also adds a script that can be piped to in order to send the output. The sender script also supports having additional remote outputs.
Example usage:
In order to send to additional outputs, simply add
-o tcp:hostname:port
as many times to theiridium-acars-to-airframes.py
command.