Closed Bug 1436962 Opened 6 years ago Closed 6 years ago

[PulseGuardian] Remove unused legacy SSL endpoint addon

Categories

(Webtools :: Pulse, enhancement)

enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: emorley, Assigned: emorley)

References

Details

Bug 1383288 enabled the new style SSL feature on the `pulseguardian` Heroku app.

However the old $20/month addon hasn't yet been removed.

$ heroku addons:info --app pulseguardian ssl
=== ssl-crystalline-6395
Attachments:  pulseguardian::SSL
Installed at: Thu Aug 27 2015 12:24:18 GMT+0100 (GMT Daylight Time)
Owning app:   pulseguardian
Plan:         ssl:endpoint
Price:        $20/month
State:        created


$ heroku certs --app pulseguardian
Name                 Endpoint                     Common Name(s)             Expires               Trusted  Type
───────────────────  ───────────────────────────  ─────────────────────────  ────────────────────  ───────  ────────
shizuoka-2362        shizuoka-2362.herokussl.com  pulseguardian.mozilla.org  2017-08-31 12:00 UTC  True     Endpoint
dilophosaurus-20877  (Not applicable for SNI)     pulseguardian.mozilla.org  2018-05-09 00:08 UTC  True     ACM


$ heroku domains --app pulseguardian
...
=== pulseguardian Custom Domains
Domain Name                DNS Record Type  DNS Target
─────────────────────────  ───────────────  ───────────────────────────────────────
pulseguardian.mozilla.org  CNAME            pulseguardian.mozilla.org.herokudns.com


Checking DNS shows no references to the old style CNAME (ie `shizuoka-2362.herokussl.com`):

$ dig pulseguardian.mozilla.org CNAME +short
pulseguardian.mozilla.org.herokudns.com.


Mark, presuming you're ok with it, I'll remove the legacy addon per the migration docs (similar to what we did for Treeherder et al):
https://devcenter.heroku.com/articles/ssl#remove-ssl-endpoint-add-on-after-24-hours
Flags: needinfo?(mcote)
Oh yes, sure, I must have missed that.  Thanks!
Flags: needinfo?(mcote)
Addon removed
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.