IS-AgroSmart / AgroSmart-Web

1 stars 1 forks source link

WebODM migration #104

Closed jreyesr closed 3 years ago

jreyesr commented 3 years ago

This issue is intended to track all code changes required, should the decision be made to switch AgroSmart to use WebODM as a processing provider.

Backend

core/models.py

core/views.py

Test files

Test files are intentionally not listed here. See https://github.com/IS-AgroSmart/AgroSmart-Web/issues/104#issuecomment-768726324 below for the proposed way of dealing with tests.

Frontend

FlightDetails.vue

jreyesr commented 3 years ago

Planned migration procedure:

jreyesr commented 3 years ago

~Test handling is a pending issue.~ Tests are confirmed working. The Pytest runner sets the NODEODM_SERVER_URL envvar to http://container-nodeodm:3000, and all mocks work as expected.

If the approach outlined in https://github.com/IS-AgroSmart/AgroSmart-Web/issues/104#issuecomment-768721265 is taken, it should be easy to keep tests working by overriding the settings.NODEODM_SERVER_URL variable. If it's set back to http://container-nodeodm:3000, tests should still create their mocks for the correct URLs and therefore keep working as expected.

jreyesr commented 3 years ago

~There is still the issue of receiving webhooks. WebODM Lightning does not support calling a webhook after processing is complete. Therefore, there should be some way of simulating the webhook. WIP in https://github.com/IS-AgroSmart/webhook_adapter~

This problem is already solved and merged