3 ms·
There's not enough information to come to a conclusion as to what the 503s originated from. There is enough information for manufactured outrage, of course. I
by p_ing 10mo ago
There's not enough information to come to a conclusion as to what the 503s originated from. There is enough information for manufactured outrage, of course.
I don't see why one would want to run in-the-clear over the Azure network for SQL connections.
The author was doing hobby projects. Granted, hobby projects should run on any platform, but Azure seems to have less of that free tier you can get elsewhere.
- FreezeInTheDark 10mo agoOh for sure you want to use TLS, what's insane is the developer experience of needing to implement it yourself.
- hirsin 10mo agoThe author chose a library that didn't support TLS, written by a company that isn't Microsoft. Terrible devex indeed but hard to see why that's the fault of the platform that required TLS.
- PunchyHamster 10mo ago> There's not enough information to come to a conclusion as to what the 503s originated from. It's the MS way. I remember writing some code for MS graph and wondering why the hell it isn't working, I'm doing near same thing that doc example did. Nonsense generic error message. Left for the day, ran code next morning, everything works fine. No message saying "hey the thing behind it is down", just error that was generic enough that it could be my inputs being wrong.
- p_ing 10mo agoThe author did not make any statements that would lead to the conclusion the issue is lack of information provided by the platform, simply they do not state any troubleshooting steps taken.
- rootsofallevil 10mo agoI've seen these mysterious and unexplained 503s occur Solution: 1. Delete Function App 2. Deploy again 3. Profit?