Allow to redefine the request method for templates

[ninsbl]

Some templates could produce a fairly swift response, like e.g. v.db.select, r.category or the like.

In such cases, it can be often much more convenient to run the template as GET instead of POST and have the results returned directly. Therefore, it would be great if one could redefine a method e.g. through the template,...

That would greatly improve the flexibility and allow users to extend the actinia-core API with tailor-made endpoints...

Any hint on how to achieve that? Is it possible and if yes, Where in the code would one have to look to get that in? Or is that a case for a plugin?

[anikaweinmann]

Cool idea.
We thought about how this could be implemented:
In a new actinia-plugin you can add a endpoint link in https://github.com/actinia-org/actinia-module-plugin/blob/main/actinia_module_plugin/endpoints.py#L69C25-L69C39 e.g. for ephemeral processing for example "/locations/<location>/execute/<module>". The way to do the processing can be similar to https://github.com/actinia-org/actinia-module-plugin/blob/main/actinia_module_plugin/core/modules/grass.py#L65.

The request would of this new processing endpoint would then be something like:

curl -U 'xxx:xxx' -X GET actinia.de/api/v3/locations/nc_spm_08/execute/v.db.select?map=xxx&columns=xxx