-
Notifications
You must be signed in to change notification settings - Fork 24
Description
Effectively, for leaderboard or AWX, we want to have effective state tracking of the pipeline. The current assertion.json is not detailed enough to have an effective understanding of what went wrong. This should be eventually usurped by status.json. However, the implementation and effectiveness of this new standard needs to be thought through more than the thread safe implementation provided by #255 .
Ultimately, the status should show a user something like this
[
{
"metadata": {
"task": {
"name": "",
"result": "",
}
},
"phase": "",
"status": "",
"timestamp": ""
}
]Would be great if the array is sorted by timestamp (earlier to latest), but need not be by here as once the JSON array is there and correct, any consumer of it can sort.
The upload process to S3 storage probably needs more back up options. Maybe we suggest that a local store should always be defined? Though making this a requirement would make it hard to smoke test or use AWX.