Change Details

This diff introduces changes to the type for `deviceType` field from a string to an integer. The `deviceType` is an [[ https://github.com/CommE2E/comm/blob/e75f9264bacfe59fb36958e8dcbcf29331931ba4/shared/protos/tunnelbroker.proto#L49 | enum type in our proto file ]]. The values come from the gRPC requests as an integer enum representation, Rust Tonic proto file compiler also creates the enum representation as an integer. Before switching to Rust we are using the string as a storing type of the enum value in the database because of the enum matching was done using strings on the C++ side. Now it doesn't make sense to store the enum value as a string in a database, because the matching of the enum in Rust uses integer representation as well as in gRPC implementation itself. Linear task: [[ https://linear.app/comm/issue/ENG-2059/implement-tunnelbroker-grpc-newsession-api-handler-in-rust | ENG-2059 ]]

TBDThis diff introduces changes to the type for `deviceType` field from a string to an integer. The `deviceType` is an [[ https://github.com/CommE2E/comm/blob/e75f9264bacfe59fb36958e8dcbcf29331931ba4/shared/protos/tunnelbroker.proto#L49 | enum type in our proto file ]]. The values come from the gRPC requests as an integer enum representation, Rust Tonic proto file compiler also creates the enum representation as an integer. Before switching to Rust we are using the string as a storing type of the enum value in the database because of the enum matching was done using strings on the C++ side. Now it doesn't make sense to store the enum value as a string in a database, because the matching of the enum in Rust uses integer representation as well as in gRPC implementation itself. Linear task: [[ https://linear.app/comm/issue/ENG-2059/implement-tunnelbroker-grpc-newsession-api-handler-in-rust | ENG-2059 ]]