Summary of the Amazon S3 Service Disruption

Re:Summary of the Amazon S3 Service Disruption by hinkley on Thursday March 02, 2017 @01:31PM (#13776783)

It occurs to me that having to type the English version of the numbers would probably work in this scenario.

   s3-shutdown -c "one hundred fifty"

But something simpler like a --emergency flag or the more whimsical --shutitdownshutitalldown

[ Parent | on HN ]

Re:Summary of the Amazon S3 Service Disruption by traek on Thursday March 02, 2017 @04:58PM (#13778643)

Facebook uses a `--clowntown` flag to let people do things without normal checks. [0]

[0] https://www.quora.com/When-people-who-work-at-Facebook-say-c...

[ Parent | on HN ]

Re:Summary of the Amazon S3 Service Disruption by hamms on Friday March 03, 2017 @08:10PM (#13788483)

I also rather like their intentionally verbose and scary parameter for generating arbitrary HTML in React: https://facebook.github.io/react/docs/dom-elements.html#dang...

[ Parent | on HN ]

Re:Summary of the Amazon S3 Service Disruption by rickcnagy on Thursday March 02, 2017 @03:41PM (#13777987)

I think the biggest problem with flags like --emergency is if they end up in daily use, such as git --force. Then, they are both sudo-level AND used without a lot of though.

[ Parent | on HN ]

Re:Summary of the Amazon S3 Service Disruption by hinkley on Thursday March 02, 2017 @04:35PM (#13778461)

I was in fact thinking of the --force problem which is why I went another way.

[ Parent | on HN ]

Re:Summary of the Amazon S3 Service Disruption by geeio on Thursday March 02, 2017 @04:02PM (#13778168)

Maybe more like --force-with-lease

[ Parent | on HN ]