Closed wphyojpl closed 1 month ago
archiving_types is not really working correctly at this moment.. Need more tests.
archiving_types is not really working correctly at this moment.. This is fixed.
But Archive lambda is being triggered before ES indexing lambda is executed. As a result, it's always missing / no need to archive.
DAAC SNS is published twice. Need to check.
cnm response only has collection name w/o version. Need to use only collection name.
Testing failure:
"archive_status": "cnm_r_failed",
"archive_error_message": "[{\"uri\": \"https://uds-distribution-placeholder/uds-sbx-cumulus-staging/URN:NASA:UNITY:UDS_LOCAL_ARCHIVE_TEST:DEV:UDS_UNIT_COLLECTION___2407291400/URN:NASA:UNITY:UDS_LOCAL_ARCHIVE_TEST:DEV:UDS_UNIT_COLLECTION___2407291400:abcd.1234.efgh.test_file05/abcd.1234.efgh.test_file05.data.stac.json\", \"error\": \"unknown error: An error occurred (403) when calling the HeadObject operation: Forbidden\"}, {\"uri\": \"https://uds-distribution-placeholder/uds-sbx-cumulus-staging/URN:NASA:UNITY:UDS_LOCAL_ARCHIVE_TEST:DEV:UDS_UNIT_COLLECTION___2407291400/URN:NASA:UNITY:UDS_LOCAL_ARCHIVE_TEST:DEV:UDS_UNIT_COLLECTION___2407291400:abcd.1234.efgh.test_file05/abcd.1234.efgh.test_file05.cmr.xml\", \"error\": \"unknown error: An error occurred (403) when calling the HeadObject operation: Forbidden\"}]",
"archive_error_code": "VALIDATION_ERROR"
Who will take care of S3 bucket's IAM role updates for the real DAAC to pull data?
Testing with Unity-Venue-Dev
customer created bucket.
Looks like need to add arn:aws:s3:::*unity*
to lambda-processing-role
.
Probably need to do similar thing on mock-daac lambda as well to that custom bucket
Should we store the success / failure history of DAAC? Currently, when a status is updated, the old failure messages will be deleted. Should they be stored?
Keep Granules stac compliant. Move archival to "properties"
Closes #380 Closes #378 Closes #377