Mark failed evidence descriptions instead of retrying
Previously the worker reset failed descriptions back to PENDING, causing infinite retry loops for permanently broken evidence. Add a FAILED status so these items stop cycling and can be investigated. Signed-off-by: Bryan Frimin <bryan@getprobo.com>
This commit is contained in:
@@ -27,6 +27,7 @@ const (
|
||||
EvidenceDescriptionStatusPending EvidenceDescriptionStatus = "PENDING"
|
||||
EvidenceDescriptionStatusProcessing EvidenceDescriptionStatus = "PROCESSING"
|
||||
EvidenceDescriptionStatusCompleted EvidenceDescriptionStatus = "COMPLETED"
|
||||
EvidenceDescriptionStatusFailed EvidenceDescriptionStatus = "FAILED"
|
||||
)
|
||||
|
||||
func (s EvidenceDescriptionStatus) MarshalText() ([]byte, error) {
|
||||
@@ -43,6 +44,8 @@ func (s *EvidenceDescriptionStatus) UnmarshalText(data []byte) error {
|
||||
*s = EvidenceDescriptionStatusProcessing
|
||||
case EvidenceDescriptionStatusCompleted.String():
|
||||
*s = EvidenceDescriptionStatusCompleted
|
||||
case EvidenceDescriptionStatusFailed.String():
|
||||
*s = EvidenceDescriptionStatusFailed
|
||||
default:
|
||||
return fmt.Errorf("invalid EvidenceDescriptionStatus value: %q", val)
|
||||
}
|
||||
|
||||
1
pkg/coredata/migrations/20260326T150000Z.sql
Normal file
1
pkg/coredata/migrations/20260326T150000Z.sql
Normal file
@@ -0,0 +1 @@
|
||||
ALTER TYPE evidence_description_status ADD VALUE IF NOT EXISTS 'FAILED';
|
||||
Reference in New Issue
Block a user