Closed Bug 1183835 Opened 9 years ago Closed 9 years ago

Apply Hello channel insertion in Staging, then Production

Categories

(Content Services Graveyard :: Tiles: Ops, defect)

Product:
Content Services Graveyard
Component:
Tiles: Ops
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: oyiptong, Assigned: relud)

References

(
URL
)

Details

(Whiteboard: .?) 

This will create a 'hello' row in the channels table in Redshift.

Please apply the following database migration in Staging, then Prod:

https://raw.githubusercontent.com/mozilla/splice/bf1970cf6d9352299238a265d4c2b7c0ed7a702d/ddl/migrations/redshift/1436905466.sql
I'll set up some time tomorrow morning to do this, with either Daniel or Benson to check my work.
Status: NEW → ASSIGNED
QA Contact: dthornton
Summary: Apply Hello channel insertion in Staging → Apply Hello channel insertion in Staging, then Production
Stage migration done.  Assigning to Daniel for production migration.

Filing separate bug for updating automated tests to cover the new channel.
Assignee: kthiessen → dthornton
QA Contact: dthornton → kthiessen
Depends on: 1184208
adding a blocker for prod deploy, we should have at least the tile_index_crawl.py ready to test this new channel before this goes to prod. geoip_api_test.py test change, onyx code change, and onyx config change, to support the new channel will be deployed separately.
Depends on: 1185074
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.