Currently, Antenna saves crash data to AWS S3 and then AWS S3 generates an event and that triggers Pigeon to add the crash id to the RabbitMQ socorro.normal processing queue.

That involves a few parts. When we originally designed it, Pigeon was also throttling incoming crashes and handling populating the socorro.submitter queue. We don't do that anymore in Pigeon.

This bug covers:

1. set up local dev environment bits for pubsub
2. implementing a pubsub publishing component in Antenna
3. wrapping the component in a feature-flag which will default to off for now
4. writing tests

Making this a P2 to do soon.

I've got this working in a local dev environment. I'm using the pubsub emulator which works nicely. I wrote a helper script for setting up and manipulating the pubsub emulator environment.

I still need to explore fail-scenarios and make sure they're covered appropriately, test it with a real Pub/Sub project/topic, and add unit tests and a systemtest.

We're not doing a feature flag. Instead, we're just defaulting to a NoOpCrashPublish class. When we want to publish to Pub/Sub, we'll switch it.

willkg merged PR #299: "fix bug 1527343: implement publishing to Pub/Sub" in 8679718.

We pushed this to prod just now. Marking as FIXED.