Follow up to #342
The Slack notification rules currently point to incorrect S3 files
- The
ppx.ndjson.zst file does not exist on S3, so we do not get any "New records" notifications. This needs to be updated to ppx_with_restricted.ndjson.zst
- The local OPEN+RESTRICTED
results/metadata.tsv is being compared to the OPEN metadata.tsv.zst on S3, so we will always receive diffs of the RESTRICTED data. This needs to be updated to metadata_with_restricted.tsv.zst.
These are easy fixes, but I'm also questioning whether these Slack notifications are still useful. If not, we should no longer maintain the rules and just remove them completely.
Follow up to #342
The Slack notification rules currently point to incorrect S3 files
ppx.ndjson.zstfile does not exist on S3, so we do not get any "New records" notifications. This needs to be updated toppx_with_restricted.ndjson.zstresults/metadata.tsvis being compared to the OPENmetadata.tsv.zston S3, so we will always receive diffs of the RESTRICTED data. This needs to be updated tometadata_with_restricted.tsv.zst.These are easy fixes, but I'm also questioning whether these Slack notifications are still useful. If not, we should no longer maintain the rules and just remove them completely.