So:
{
"payload": {
"message_type": "platform_instruction_set",
"platform_ID": "unit_111",
"instruction_set": {...}
}
}
?
That'd work. imo I think it's simpler to just add platform_ID to the instruction sets themselves, it's not onerous to add a field to a bit of JSON being sent. Plus they still need to build up the destination string when publishing the message, right? (So already doing the work of knowing what glider to send it to etc)
Up to you. If you stick to the structure above I can quickly add in some code on sfmc-adapter side to handle platform_instruction_set. Alternatively, if adding platform_ID to instruction_set as-is, I've already updated it to handle that, and falling back to getting platform ID from the destination topic when that doesn't exist. So it'll work as-is as long as they publish to the right channel.
Dan Jones authored