Description
I have a use case where I'm programmatically starting updates via the Aurora API and sometimes the request to the scheduler times out or fails, even though the update is written to storage and started.
I'd like to be able to store some unique identifier on the update so that we can reconcile this state later. We can make this generic by allowing clients to store arbitrary metadata on an update (similar to how they do it with job configuration).