405 method not allowed in DEBUG gives zero information as to why

[david-heward-unmind]

Can we improve the logging around the 405 method not allowed middleware errors?

I am using a proxy service to expose and test an atlantis build out locally and its currently chucking out 405 method not allowed errors. After toying around with a few things (including debug mode) i haven't managed to figure out why my container is unwilling to accept requests & the super useful logs simply spew out.

{"level":"debug","ts":"2022-05-23T11:17:59.899Z","caller":"server/middleware.go:44","msg":"POST / – from 172.17.0.1:59750","json":{}}
{"level":"debug","ts":"2022-05-23T11:17:59.900Z","caller":"server/middleware.go:70","msg":"POST / – respond HTTP 405","json":{}}

Which tells me no more than the blindingly obvious.

Perhaps we could add a section of documentation that attempts to document the reasons (even in order) that this may be occurring. Even if nothing is added to the code.

[enarmontas]

I think it should be more verbose here as the message is very generic. It can at least mention that Atlantis webhook should be configured with /events endpoint.

[jamengual]

is this still happening with v0.19.8?