Closed patrice-conil closed 1 month ago
Hi @patrice-conil, I see this is not applied to other APIs dealing with subscriptions, such as DeviceStatus and SimSwap notifications. This should be something to be agreed transversely.
Hi @patrice-conil, I see this is not applied to other APIs dealing with subscriptions, such as DeviceStatus and SimSwap notifications. This should be something to be agreed transversely.
Thanks @jlurien, I will therefore suggest doing it in commonalities each time we can specify the format of the field.
Hi @patrice-conil,
with the latest subscription-model changes, the newly called sink
will have a format: url
:
sink:
type: string
format: url
description: The address to which events shall be delivered using the selected protocol.
example: "https://endpoint.example.com/sink"
Would that fit as a solution for your issue here?
Problem description To have a strong typed notificationUrl, add a format constraint on type. This will simplify implementation and clarify usage.