Allow checking if a job's trace has been erased
Problem to solve
Using the API; right now I couldn't find a way to know beforehand if a job's trace (the log, artefacts etc.) have already been erased.
I can't seem to define an 'erased' scope while fetching all jobs, nor do I see any property returned in the response which I can use to determine if a job is erased.
Further details
Subsequent calls to the endpoint to erase a job's trace give back a client error (403
), which evidently means that the job has already been erased. I think this is right however and it should remain a 403
.
Proposal
What does success look like, and how can we measure that?
Success would be defined as giving API-consumers a way to determine that a job has been erased. Which could be achieved by:
- allowing the
erased
scope while trying to fetch all jobs from a pipeline (or excluding erased jobs with the same scope) - adding a property to the returned response for a job which determines if a job has been erased
Links / references
Edited by Gerald Eersteling