For accounting purposes, we want detailed tracking of processing costs. For batch job it's trivial to use the batch job id to associate processing costs. For synchronous requests we use internal "request ids", but that is not exposed in a standard way to the end user.
This PR adds a "OpenEO-Identifier" header to the sync processing response, much like the "create batch job" endpoint
For accounting purposes, we want detailed tracking of processing costs. For batch job it's trivial to use the batch job id to associate processing costs. For synchronous requests we use internal "request ids", but that is not exposed in a standard way to the end user.
This PR adds a "OpenEO-Identifier" header to the sync processing response, much like the "create batch job" endpoint