Trying to add a brand new, non-load-tested, non-hardened binary to a site with actual reliability requirements 12-24h before your deploy is not behavior that de

Trying to add a brand new, non-load-tested, non-hardened binary to a site with actual reliability requirements 12-24h before your deploy is not behavior that demands to be taken seriously. Someone serious would have talked to the reliability team months, if not quarters, ahead of time and learned eg transport and cutout requirements. There are also almost certainly other requirements, eg run books. Let alone on a Sunday afternoon. The whole thing smells like someone knew there was a process to do X, figured their X wouldn't pass, and tried to bypass the process.