Implementing that type of multi-account support likely had some big authz changes (I've done a couple of those projects before), and GitHub defaults to a 404 for authz errors instead of leaking information with a 403. Just a wild guess.
Implementing that type of multi-account support likely had some big authz changes (I've done a couple of those projects before), and GitHub defaults to a 404 for authz errors instead of leaking information with a 403. Just a wild guess.
> Update - We’re in the process of rolling back an authorization-related change that is causing 404s and other errors.
But you don't get to choose this with XaaS. It goes down when it goes down, it comes up when it comes up. Our connectivity supplier sends us a notice that "circuit from X to Y will be going down from 0200-0500" and we have no choice but to accept it.
Typically updates are best done on Tuesday morning given that most people are awake and working and thus if there are problems they can fix it, but you wouldn't go ahead while the resilience is down (say due to a fibre cut, or a power outage)
Still seems odd that no CI/QA would have caught such a widespread bug.