Add reflection support for kuksa.val.v2

[rafaeling]

Release binaries generated locally went from 6.3 MB to 6.5 MB after reflection support was added for kuksa.val.v2

It helps to test kuksa.val.v2 with grpcurl until databroker-cli is updated, i.e:

grpcurl -d '{ "signal_id": { "path": "Vehicle.Speed" }, "data_point": { "timestamp": "2024-10-29T12:04:31.463835877Z", "value": { "float": 75.5 } }}' -plaintext localhost:55555 kuksa.val.v2.VAL.PublishValue

grpcurl -d '{ "signal_id": { "path": "Vehicle.Speed" } }' -plaintext localhost:55555 kuksa.val.v2.VAL.GetValue

grpcurl -d '{ "signal_paths": ["Vehicle.Speed"]}' -plaintext localhost:55555 kuksa.val.v2.VAL.Subscribe

[codecov]

Codecov Report

Attention: Patch coverage is 0% with 6 lines in your changes missing coverage. Please review.

Project coverage is 58.92%. Comparing base (62552a5) to head (8483c51).
Report is 4 commits behind head on feature/databroker-api-v2.

Files with missing lines	Patch %	Lines
databroker/src/grpc/server.rs	0.00%	6 Missing ⚠️

Additional details and impacted files

@@                      Coverage Diff                      @@
##           feature/databroker-api-v2      #89      +/-   ##
=============================================================
- Coverage                      58.94%   58.92%   -0.02%     
=============================================================
  Files                             33       33              
  Lines                          15867    15872       +5     
=============================================================
  Hits                            9353     9353              
- Misses                          6514     6519       +5     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[lukasmittag]

If we enable it shouldn't we enable it for the other interfaces as well not only v2?

[erikbosch]

Should we possibly add some info on how this can be used, either in the wiki (https://github.com/eclipse-kuksa/kuksa-databroker/wiki/Release-Testing ? ) or somewhere in https://github.com/eclipse-kuksa/kuksa-databroker/tree/main/doc

[rafaeling]

Should we possibly add some info on how this can be used, either in the wiki (https://github.com/eclipse-kuksa/kuksa-databroker/wiki/Release-Testing ? ) or somewhere in https://github.com/eclipse-kuksa/kuksa-databroker/tree/main/doc

I think it would be good to add it to the Release-Testing to ensure all errors are returned correctly.

[erikbosch]

Looks good to me. For me it is OK that we only have discovery for the new API. I tested with the command below and it reported what I expected.

erik@debian6:~/kuksa.val$ docker run --network=host fullstorydev/grpcurl  --plaintext -vv 127.0.0.1:55555 describe
kuksa.val.v2.VAL is a service:
service VAL {

But my approval is conditioned on that we add a short section in the release testing wiki, possibly just stating that you should run a command like above. Even better would be if we could have an automatic test, but that would require more work I think

[rafaeling]

Looks good to me. For me it is OK that we only have discovery for the new API. I tested with the command below and it reported what I expected.

erik@debian6:~/kuksa.val$ docker run --network=host fullstorydev/grpcurl  --plaintext -vv 127.0.0.1:55555 describe
kuksa.val.v2.VAL is a service:
service VAL {

But my approval is conditioned on that we add a short section in the release testing wiki, possibly just stating that you should run a command like above. Even better would be if we could have an automatic test, but that would require more work I think

@erikbosch there it is https://github.com/eclipse-kuksa/kuksa-databroker/wiki/Release-Testing#testing-databroker-kuksavalv2-api-methods-with-grpcurl