Add TypeUUID to Messages

This allows messages to be identified by their UUID. This means that
messages are no longer identified by the internal TypeId as provided
from rustc but our choosing. This allows for more powerful features
along the line, such as external programs being able to specify messages
at all.

Signed-off-by: Marcel Müller <m.mueller@ifm.com>

2 files changed, 10 insertions, 4 deletions

diff --git a/crates/core/tedge_api/examples/heartbeat.rs b/crates/core/tedge_api/examples/heartbeat.rs
index b253009b..8d64232a 100644
--- a/crates/core/tedge_api/examples/heartbeat.rs
+++ b/crates/core/tedge_api/examples/heartbeat.rs
@@ -10,17 +10,20 @@ use tedge_api::{
     PluginError,
 };
 use tokio::sync::RwLock;
+use type_uuid::TypeUuid;
 
+#[derive(Debug, TypeUuid)]
+#[uuid = "94916be9-17ba-4bca-a3a0-408d33136fed"]
 /// A message that represents a heartbeat that gets sent to plugins
-#[derive(Debug)]
 struct Heartbeat;
 impl Message for Heartbeat {}
 impl AcceptsReplies for Heartbeat {
     type Reply = HeartbeatStatus;
 }
 
+#[derive(Debug, TypeUuid)]
+#[uuid = "a6d03c65-51bf-4f89-b383-c67c9ed8533b"]
 /// The reply for a heartbeat
-#[derive(Debug)]
 enum HeartbeatStatus {
     Alive,
     Degraded,
diff --git a/crates/core/tedge_api/examples/universal_log.rs b/crates/core/tedge_api/examples/universal_log.rs
index 34090040..064ffa22 100644
--- a/crates/core/tedge_api/examples/universal_log.rs
+++ b/crates/core/tedge_api/examples/universal_log.rs
@@ -10,13 +10,16 @@ use tedge_api::{
     PluginError,
 };
 use tokio::sync::RwLock;
+use type_uuid::TypeUuid;
 
 /// A message that represents a heartbeat that gets sent to plugins
-#[derive(Debug)]
+#[derive(Debug, TypeUuid)]
+#[uuid = "1f807f7b-888f-4881-a1b5-16380e32f8c2"] 
 struct Heartbeat;
 impl Message for Heartbeat {}
 
-#[derive(Debug)]
+#[derive(Debug, TypeUuid)]
+#[uuid = "346e233f-c24a-47e0-a15b-3ec0d1e19019"] 
 struct RandomData;
 impl Message for RandomData {}