Closed
Bug 1219834
Opened 9 years ago
Closed 9 years ago
Whitelist warm-springs-4343.herokuapp.com on aus4-dev
Categories
(Infrastructure & Operations Graveyard :: WebOps: Product Delivery, task)
Infrastructure & Operations Graveyard
WebOps: Product Delivery
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: catlee, Assigned: cliang)
Details
(Whiteboard: [kanban:https://webops.kanbanize.com/ctrl_board/2/2056] )
Can you please add warm-springs-4343.herokuapp.com to the whitelist on aus4-dev, and aus4-dev-admin. This should only be changed on the dev nodes, not the production nodes. Thanks!
Assignee | ||
Updated•9 years ago
|
Assignee: server-ops-webops → cliang
Assignee | ||
Comment 1•9 years ago
|
||
I believe I've added warm-springs-4343.herokuapp.com to the domain whitelist. Can you please test and verify that the domain is correctly whitelisted? * Edited /data/aus-dev/src/aus4-dev.allizom.org/app/balrog.ini and /data/aus-dev/src/aus4-admin-dev.allizom.org/app/admin.ini; pushed out the change. * Restarted apache on aus1.dev.webapp * Updated puppet templates.
Reporter | ||
Comment 2•9 years ago
|
||
Yes, looks good, thanks!
Assignee | ||
Updated•9 years ago
|
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Updated•8 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•