harmony-py was using a GET for all calls to harmony, but this was causing 413 issues when trying to use a long list of granuleIds because of URL length limits. This PR switches to use a POST with multipart/form-data (we were already doing this when a shapefile was included in the request).
Local Test Steps
Run make test and verify all tests pass.
Run the first request in the examples/tutorial.ipynb notebook. Note that there's a bug in harmony parsing width and height which will be addressed as a separate ticket. So you'll need to comment those out so the cell looks like this:
Jira Issue ID
HARMONY-1721
Description
harmony-py was using a GET for all calls to harmony, but this was causing 413 issues when trying to use a long list of granuleIds because of URL length limits. This PR switches to use a POST with multipart/form-data (we were already doing this when a shapefile was included in the request).
Local Test Steps
Run
make test
and verify all tests pass. Run the first request in theexamples/tutorial.ipynb
notebook. Note that there's a bug in harmony parsing width and height which will be addressed as a separate ticket. So you'll need to comment those out so the cell looks like this:Verify the request completes successfully. You can also check the harmony logs in the UAT environment to tell that it is using a POST and not a GET.
PR Acceptance Checklist