[EPIC]: Weathertop Part 3/3: Onboarding, hardening, feedback

[ford-at-aws]

This final epic will cover the work required to move Weathertop from the lab into full production. It will answer key questions like:

• how will we handle onboarding of new code over time? E.g. is it a requirement? Suggestion?
• how will team members interact with Weathertop day-to-day? I.e. where will it fit in our SDLC?
• what will the docs or "on-call playbook" include and who will be responsible for monitoring automation?
• are people happy with this product? How can we make it better?

---

Link to Weathertop One-Pager [Internal AWS only]

User story

As an Example Code Engineer, I want to onboard my language's example code into the new Weathertop test harness so that I can monitor if my example code is running.

Acceptance criteria

I will know this is done when:

• Infra deployed in language owner's Isengard account
• Infra updated in master account to activate triggering (ask Ford)
• Docker image finalized and successfully triggering in Batch
• All example code that is invoked is passing successfully

Timeline (DUE 9/15/2023)

Onboarding:

• [x] #5050 (July 24-28)
• [x] #5054 (July 24-28)
• [x] #5059 (July 24-28)
• [x] #5051 (Aug 21-25)
• [x] #5052 (Aug 21-25)
• [x] #5056 (Aug 28-Sep 1)
• [x] #5058 (Aug 28-Sep 1)
• [x] #5055 (Sep 4-8)
• [x] #5060 (Sep 4-8)
• [x] #5057 (Sep 11-15)
• [x] #5053 (Sep 11-15)

Follow-ups:

• [x] blog post
• [x] #4308
• [x] #4307
• [ ] #5454

[ford-at-aws]

Add on: can we possibly automate cross-account deployments of stack sets for consumer stack? Add on: blog post on Build On