no longer send SNS messages reporting ingest success/failure #192
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Confirmed that all 145,454 products ingested in the last 90 days came from HyP3 and cloud-based-insar-operations. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The original design was based on products being published by an SDS team and ingested by a DAAC team. For each published product, an SNS message was sent back to the SDS team with details on whether the ingest succeeded or failed, since they wouldn't have access to see those details inside the ingest system itself.
If new GUNW products are all going to be published by https://github.com/ASFHyP3/cloud-based-insar-operations, operated by ASF, then there's no need for this notification.
I'm reviewing data from the last three months to see if the old system at JPL is still publishing messages. This PR wouldn't change their ability to publish data; they just wouldn't get the status message back.