Open Bug 1579266 Opened 5 years ago Updated 1 month ago

update telemetry socorro import to pull from GCS instead of S3

Categories

(Socorro :: General, task, P3)

Tracking

(Not tracked)

People

(Reporter: willkg, Unassigned)

References

(Depends on 1 open bug, Blocks 1 open bug)

Details

Attachments

(1 obsolete file)

In https://github.com/mozilla/telemetry-airflow/pull/594, they switched the socorro import to put the data in BigQuery. So it's pulling from the S3 bucket that we put crash data destined for Telemetry in and putting it in BigQuery.

When Socorro switches to GCP, we need to update the processor to save crash data destined for Telemetry to save it in GCS and then help the Telemetry folks to update the socorro import to pull from the right place.

We're no longer moving Socorro to GCP, but it may still make sense to put Telemetry-destined crash data in GCS. If we do that, we'll still need a GCS emulator for local development.

No longer blocks: 1512641
Depends on: 1550534

Migrating from AWS to GCP keeps getting kicked down the road. We do eventually want to do this, but we won't until Socorro has migrated to GCP or some compelling reason pops up.

Assignee: nobody → dthorn
Status: NEW → ASSIGNED
Attachment #9380051 - Attachment is obsolete: true
Assignee: dthorn → nobody
Status: ASSIGNED → NEW
Depends on: 1881575
Depends on: 1886019
No longer depends on: 1881575
Depends on: 1886021
No longer depends on: 1886019
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: