Thank you Aaron. That’s really helpful.
I can’t see “Request Headers” as an option. I believe it’s because my broker version is too old?
“In SolOS 9.11 which came out in Sept (2021), you can add additional headers to your outbound webhook for the RDP.”
I’m using Solace Cloud on a free trial account. I don’t see how I can upgrade my broker from “version 9.10.0.23”. I also created a new account to create a brand new broker but the only options I can see for the cloud broker are “9.6 or 9.10 (default)”.
I actually don’t think this technique is going to work for me though. The more I dug into my use case, the more I realized I’m going to need to transform the queue payload, perform some custom encryption etc.
I’m most likely going to need a transformation step after processing the queue data like you mentioned. I might use something like a custom microservice or aws lambda. The web service endpoint will be synchronous. Basically I think I’ll plan to have a new Solace REST Delivery Point that will invoke my new aws lambda function synchronously. The lambda function will perform the necessary payload transformations and invoke the original web hook endpoints. If the lambda function fails (or the downstream web hook fails), the Solace REST Delivery Point will fail and the message requeues in Solace. Does this sound correct to you?
Thanks,