This means that flights are forever stuck on 100% progress and the webhook is never called, which means that the Geoserver workspaces are never created, among other issues.
Proposed fix is to slightly relax the authentication code, only on the /nodeodm/task/uuid/info endpoint, so that requests coming from the IP of the webhook_adapter container bypass the authentication step.
With the introduction of authentication on NodeODM API calls, the
webhook_adapter
container can no longer ping the NodeODM API to monitor Flights, since the API rejects its requests with a HTTP 403 error.This means that flights are forever stuck on 100% progress and the webhook is never called, which means that the Geoserver workspaces are never created, among other issues.