These endpoints proxy the creation and updation of maps_extended entries, while also updating the relevant submission / mapfix status.
Reviewed-on: #11
Co-authored-by: Rhys Lloyd <krakow20@gmail.com>
Co-committed-by: Rhys Lloyd <krakow20@gmail.com>
### Replacing Maps Service `openapi-internal.yaml` With gRPC
These are all the endpoints used by the validator. The plan is to delete `service_internal` and create `validator_controller` with equivalent gRPC functionality. This can then be extended in the future for public api & maptest integration by creating new grpc endpoints that the public api & game-rpc talk to. The gRPC extensions would be separate files (`mapfixes.proto`, `submissions.proto`, `maps.proto`) unlike `validator.proto` which has a bunch of dedicated endpoints that only the validator should use.
### Why?
To reduce the number of exposed apis. Without this there would need to be 4 (!) exposed apis (validator openapi, web openapi, public api, gRPC for game-rpc), with it, only 2 (web api, gRPC).
### Why didn't you do this in the first place?
I didn't know how. I think I have a handle on it now.
Reviewed-on: #8
Co-authored-by: Rhys Lloyd <krakow20@gmail.com>
Co-committed-by: Rhys Lloyd <krakow20@gmail.com>
