Details
Description
We should generalize the approach of dealing with scheduler updates by always uniquely identifying them by a new composite key that includes both jobKey and the updateId, e.g.:
struct JobUpdateKey {
1: JobKey jobKey
2: string updateId
}
The above approach would benefit us long term when it comes to implementing a fully functional REST API. Having both job key and update ID components in the URL will help us logically split authorization and application data layers.
E.g.: in /api/updates/role/env/name/updateId the /role/env/name may be used for authorization whereas the updateId will remove the ambiguity from the data lookup.
Attachments
Issue Links
- is duplicated by
-
AURORA-960 Update commands should be able to perform actions based on update ids
-
- Resolved
-
-
-
- Resolved
-
- is related to
-
AURORA-1139 Remove backwards compatibility shims from JobUpdateKey introduction
-
- Resolved
-
- relates to
-
-
- Resolved
-