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
When manifest files are sent to MCP #328
There is an Archive DAG that processes them.
In this ticket, we need to create that logic and implement it.
Note: We need to parse out the granule name from the path found in the manifest.
More detailed Instructions TBD
Placeholder Ticket Info Below (provides some background)
Implement Post Ingest MAXAR Delivery Bucket (MCP) File Deletions (Placeholder)
This is a placeholder ticket until the approach is better understood.
For now, here are some reminders of some of the details discussed so far
For any granules and their files that are removed from MCP, we must also remove those specific DynamoDB Records
Logs and Info to be processed for this task must be sent away from CBA PROD and the processing needs to happen on MCP
The DMS needs to become the source of truth for MAXAR granule info.
We must verify a file exists in 3 places before we delete it.
CBA PROD Buckets (Protected bucket for content files and Public bucket for Thumbs
CBA PROD DR (ORCA - Only a single archive bucket exists in ORCA which has files from both Protected and Public buckets)
Earthdata Search (CMR Records Validated to have S3 URLs Pointing at CBA PROD)
The text was updated successfully, but these errors were encountered:
When manifest files are sent to MCP #328
There is an Archive DAG that processes them.
In this ticket, we need to create that logic and implement it.
Note: We need to parse out the granule name from the path found in the manifest.
More detailed Instructions TBD
Placeholder Ticket Info Below (provides some background)
Implement Post Ingest MAXAR Delivery Bucket (MCP) File Deletions (Placeholder)
This is a placeholder ticket until the approach is better understood.
For now, here are some reminders of some of the details discussed so far
The text was updated successfully, but these errors were encountered: