Incident Commander Now Allows Incidents To Be Deleted From The Cloud
A couple of weeks ago, I updated my Incident Commander application so that its data persistence layer was powered by Firebase. This moved the incident data from your localStorage API to the remote Firebase Backend-as-a-Service (BaaS). The primary benefit of this move was that the Incident Commander responsibilities can now be shared easily amongst your teammates by passing around an incident URL. But, while these URLs are extremely secure, they are theoretically crackable given enough time. As such, I've added the ability to delete an incident once you are done with it.
Run the Incident Commander application on GitHub.
View the Incident Commander code in my Incident Commander project on GitHub.
Generally speaking, the information that I enter into the Incident Commander isn't proprietary information. Sure, it talks about InVision App's architecture and mentions things like message queue sizes, network problems, database performance, recent deployments, and log entry anomalies. But, these are all discussed at a high-level. As such - for me personally - I'm not worried about the security of the data persistence.
But, for others, who either discuss things more in-depth; or, who are simply covering their butts when it comes to discussing their company's internal workings, there is now an option to Delete the Incident at the bottom of the Incident Commander application:
Clicking this link will delete your incident data from the remote Firebase database and redirect you back to the introductory page of the application. It's a minor change; but, should hopefully bring peace-of-mind to the more cautious engineers and project managers who use the Incident Commander.
Reader Comments