You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In geonode v4.1 the new importer is not responding the result of the upload directly. It passes an execution_id. The result of the import can be gathered at a new api endpoint called: /api/v2/resource-service/execution-status/<str: execution ID>
I think its a good idea to add a new parameter to geonoctl called resource-service. This sould implement list and describe functionallity.
When using geonodectl upload [dataset, document] ... it should immediately reply the response from /api/v2/resource-service/execution-status/execution_id
The text was updated successfully, but these errors were encountered:
In geonode v4.1 the new importer is not responding the result of the upload directly. It passes an
execution_id
. The result of the import can be gathered at a new api endpoint called:/api/v2/resource-service/execution-status/<str: execution ID>
I think its a good idea to add a new parameter to geonoctl called
resource-service
. This sould implement list and describe functionallity.When using
geonodectl upload [dataset, document] ...
it should immediately reply the response from/api/v2/resource-service/execution-status/execution_id
The text was updated successfully, but these errors were encountered: