Waiting for the GITC response currently throttles the number of image sets we can send. Change to remove the wait period and complete successfully when we complete the send. Handle the GITC response outside of the state machine.
Overview of work done
remove the wait for task token during the sendToGITC lambda
change to using the image name + granule concept id for the CNM identifier
save CNM message sent to GITC in audit bucket with granuleUR + submission time as filename
move the umm-json lookup to the utils module so it can be reused out of state machine
handle the GITC response separately by moving to a regular lambda (not a cumulus process) and save the CNM-R in the same audit location with same filename (+cnm-r.json) to enable easy reconciliation
Overview of verification done
No new unit tests, existing tests pass
Overview of integration done
Deployed to SIT. Workflow succeeds when invoked manually and both CNM & CNM-R messages are saved in the audit bucket under collection_var prefix
Github Issue: closes #7
Description
Waiting for the GITC response currently throttles the number of image sets we can send. Change to remove the wait period and complete successfully when we complete the send. Handle the GITC response outside of the state machine.
Overview of work done
Overview of verification done
No new unit tests, existing tests pass
Overview of integration done
Deployed to SIT. Workflow succeeds when invoked manually and both CNM & CNM-R messages are saved in the audit bucket under collection_var prefix
PR checklist:
See Pull Request Review Checklist for pointers on reviewing this pull request