You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I saw an issue where the cirrus-geo process lambda was not given appropriate S3 permissions to allow uploading the payload to the S3 payloads bucket. However, the call to ProcessPayload.__call__ did not fail despite the S3 error returned, and the payload was ultimately dispatched to the specified workflow.
That __call__ needs to be audited to ensure it and all the functions it calls are not swallowing exceptions, and that upon hitting an exception it has the expected behavior of not processing that payload.
I saw an issue where the cirrus-geo
processlambda was not given appropriate S3 permissions to allow uploading the payload to the S3 payloads bucket. However, the call toProcessPayload.__call__did not fail despite the S3 error returned, and the payload was ultimately dispatched to the specified workflow.That
__call__needs to be audited to ensure it and all the functions it calls are not swallowing exceptions, and that upon hitting an exception it has the expected behavior of not processing that payload.