1491720 - Decommission release-notifications on heroku

Status: RESOLVED FIXED

(Release Engineering :: General, defect)

Description

[Nick Thomas [:nthomas] (UTC+12)]

https://dashboard.heroku.com/apps/release-notifications
https://github.com/mozilla-releng/pulse-notify/

Has some creds to send SES mail, use pulse and logon to IRC. I don't have sufficient access to heroku to delete it there.

Comment 1

[Johan Lorenzo [:jlorenzo]]

This is done. I had access to all aforementioned systems. 

* On Heroku, I deleted both apps: release-notifications-dev and release-notifications. 
* On Github, I archived the repo https://github.com/mozilla-releng/pulse-notify.
* On Pulse, I deleted the following queues:
  * queue/pulse-notify/release-notifications 
  * queue/pulse-notify/release-notifications-dev
  * queue/pulse-notify-dev/pulse-notify-dev (I was the only one to have access to this one)
* Still on Pulse, I deleted these users:
  * pulse-notify 
  * pulse-notify-dev 
* On IRC, I removed the nickname registration for release-notifications only. The dev instance hasn't connected for more than 365 days, therefore it was automatically dropped. I checked it by trying to identify as the dev instance again. For reference, here's how I unregistered the prod account:
> *connnect as nickname*
> /msg NickServ IDENTIFY [pass]
> /msg NickServ DROP [nickname] 
* On the Releng AWS account, I deactivated the SES API key, then I deleted both release-notifications and release-notifications-dev accounts. The production account hasn't had any activity for the past 3 months. 
* I removed the passwords, at the usual location.

Comment 2

[Johan Lorenzo [:jlorenzo]]

For reference, I handled this request today, because the Heroku migration to LDAP is upcoming and I'm in an edge case which may prevent me from having access again: https://discourse.mozilla.org/t/iam-2fa-and-plus-addresses/31861.

Comment 3

[Nick Thomas [:nthomas] (UTC+12)]

Thanks for the thorough cleanup.