Closed Bug 952317 Opened 11 years ago Closed 11 years ago

Fix up __heartbeat__ and ver.txt on FxA Stage

Categories

(Cloud Services :: Server: Firefox Accounts, defect)

defect
Not set
normal

Tracking

(Not tracked)

VERIFIED WONTFIX

People

(Reporter: jbonacci, Assigned: rfkelly)

References

Details

(Whiteboard: [qa+])

Not sure if we want or care for this, but since we have it for Dev FxA and for the Persona stacks... AUTH: https://api-accounts.stage.mozaws.net returns an "ok" https://api-accounts.stage.mozaws.net/__heartbeat__ returns a {} https://api-accounts.stage.mozaws.net/ver.txt returns a 404 CONTENT: https://accounts.stage.mozaws.net returns "Cannot GET /" https://accounts.stage.mozaws.net/__heartbeat__ returns "Cannot GET /__heartbeat__" https://accounts.stage.mozaws.net/ver.txt returns "Cannot GET /ver.txt" SCRYPT: https://scrypt-accounts.stage.mozaws.net returns "OK" (not "ok", but "OK) :-) https://scrypt-accounts.stage.mozaws.net/__heartbeat__ returns a 404 https://scrypt-accounts.stage.mozaws.net/ver.txt returns a 404
Blocks: 907494
Whiteboard: [qa+]
This may also need to be moved from Bugzilla to GitHub (https://github.com/mozilla-services/puppet-config). :rfkelly is this your bug to work on, or is this something for OPs, or both?
The missing __heartbeat__ urls sound like dev bugs, and should be filed against the respective project repositories for implementation. I'm not sure we want to keep ver.txt in production, it's an awsbox thing. We'd have to figure out what we want it to say in a production deployment - the git hash or the tagged version number of both or something else or...?
I am going to pass on ver.txt right now for Stage since it is supposed to be Prod like. fxa-auth-server Dev issue: https://github.com/mozilla/fxa-auth-server/issues/464 fxa-content-server Dev issue: https://github.com/mozilla/fxa-content-server/issues/187 fxa-scrypt-helper Dev issue: https://github.com/mozilla/fxa-scrypt-helper/issues/41
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WONTFIX
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.