Closed Bug 1210072 Opened 9 years ago Closed 9 years ago

Open SSL endpoint for Pulse's management API

Categories

(Infrastructure & Operations Graveyard :: WebOps: Other, task)

Product:
Infrastructure & Operations Graveyard
Component:
WebOps: Other
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: mcote, Assigned: cliang)

References

Details

(Whiteboard: [kanban:https://webops.kanbanize.com/ctrl_board/2/1867] )

Ideally we'd be able to migrate PulseGuardian before Pulse itself. This will be possible only if we expose the management API (over SSL) to the Internet; currently it is only available via VPN. I propose making it available at https://pulse.mozilla.org/api/. This way we can move PulseGuardian to Heroku and it should start polling the new cluster automatically after we switch the DNS entries on the migration day. Jeff Bryner has signed off on this from a security perspective.
Whiteboard: [kanban:https://webops.kanbanize.com/ctrl_board/2/1867]
Assignee: server-ops-webops → cliang
@mcote: I believe I've made the management API available https://pulse.mozilla.org/api/. Can you please confirm that its working for you?
Yup, that works! Thanks for the help!
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.