On 4/29/20 2:53 PM, Josh Berkus wrote:
Who has the perms to fix the API doc hosting?
All, Sorry...just got back from vacation :D I thought I fixed this before I left, but then "SOMEBODY" (I won't name names) went and swapped an innocent http URL for a fancy-pants https and it all broke again :D All of the project owners have permissions to fix this, but the docs I left (before vacation) made some big assumptions (my bad). I've fixed the problem (added https) and updated the doc's docs to be more clear about the issue and solution. In all cases the root-cause was human-action and not robots, aliens or sun-spots. So it should remain fixed going forward unless anybody touches anything :D Kidding aside, this was breaking out of an 'abundance-of-caution' design by some kind soul. Despite the ugly and nearly useless error message, the problem and fix is now (hopefully) documented enough that we'll know what to do should it ever break again. Thanks Josh for letting us know! I apologize for the slowness of fix. -- Chris Evich, RHCA III Senior Quality Assurance Engineer If it ain't broke, yain't tryin' hard nough.