Fix IBFE API Call
We need to update the order in which we call the IBFE API and upload build artifacts. There is a potential issue with artifacts failing to be uploaded, which happens after we call the IBFE API. This causes an issue because the IBFE DB would have records for reports that do not exist in S3. The main issue brought up by the IBFE team, is that they attempt to validate the existence of uploaded files before creating new DB records. Currently, new records are being created with some empty fields due to the file validation not being able to be performed.
Acceptance Criteria
-
Call IBFE API only after successfully uploading all artifacts to S3
Edited by David Freeman