Issue #40: Should gracefully handle S3 errors when processing CoreOS signing requests - robosignatory

robosignatory

#40 Should gracefully handle S3 errors when processing CoreOS signing requests

Opened 4 years ago by jlebon. Modified 4 years ago

Right now we just do a bucket.download_file(). If that throws, we don't actually send back a message to signal FAILURE. Also, not handling it means that the message goes back to the queue and RoboSignatory is stuck in loop trying to process the same message over and over.

Metadata

Assignee

None

Tags

None

Blocking

None

Depending on

None

Related Pull Requests

#41 Merged 4 years ago

robosignatory

Source Code

#40 Should gracefully handle S3 errors when processing CoreOS signing requests Opened 4 years ago by jlebon. Modified 4 years ago

Close issue as:

Metadata

Related Pull Requests

#40 Should gracefully handle S3 errors when processing CoreOS signing requests

Opened 4 years ago by jlebon. Modified 4 years ago