Permit

Hi <@U05767SUF8C>, I'm checking with my team and getting back to you..

Hi <@U05767SUF8C>, the data field option in data updates is basically a hack (that was added due to popular demand), we do not recommend using it, as it hurts the entire zero-trust architecture (server sees the data), and slows down event propagation and <https://docs.opal.ac/tutorials/healthcheck_policy_and_update_callbacks#-opa-healthcheck-policy|change awareness> in the system (as more data is sent over the wire).

And as a result we prefer to optimize the signature to help people verify that they’ve put in a URL for the recommended form of updates.
Yes, we could have a more dynamic schema checking here, but it wasn’t prioritized.

Hope this helps :slightly_smiling_face:

For clarity - You can of course include some value in the URL regardless of it being used.
It can also act as an indicator in logs of where the data originated from

Sounds good, i do already have all the data that i need to push when triggering the data update event but i also have an endpoint that can be called by OPAL via the standard url prop, of course that involves performing an additional query to a db. Anyway glad to hear both options are viable. Thanks again