From 44abc073c427fa214e4f2fdb38f9eb28172c6a3b Mon Sep 17 00:00:00 2001
From: pb <pierre.bayle@irt-saintexupery.com>
Date: Thu, 27 Feb 2025 16:53:39 +0100
Subject: [PATCH] First proposition of sequence for admiralty executions/setup

---
 docs/admiralty_setup.puml | 21 +++++++++++++++++++++
 1 file changed, 21 insertions(+)
 create mode 100644 docs/admiralty_setup.puml

diff --git a/docs/admiralty_setup.puml b/docs/admiralty_setup.puml
new file mode 100644
index 0000000..1638a32
--- /dev/null
+++ b/docs/admiralty_setup.puml
@@ -0,0 +1,21 @@
+@startuml
+
+boundary "oc-workflow" as workflow
+boundary "oc-monitord" as monitord
+boundary "local oc-datacenter" as locdc
+boundary "remote oc-datacenter" as rocdc
+
+workflow --> locdc : POST /booking/ {booking object}
+locdc --> locdc : create Namespace + ServiceAccount
+monitord --> monitord : retrieves a Workflow to execute
+monitord --> monitord : workflow needs repartited execution
+' monitord --> locdc : POST /admiralty/setup/:executions_id 
+monitord --> rocdc : POST /????? (route that use the same \nmethods as /booking/ to create NS & SA)
+monitord --> rocdc : POST /admiralty/source
+rocdc --> rocdc : create token for SA in NS
+rocdc --> rocdc : edit
+rocdc -> monitord : base64 encoded edited kubeconfig with token (**how to make it secure** ???)
+monitord --> locdc : POST /admiralty/secret/:execution_id
+monitord --> locdc : POST /admiralty/target/:execution_id
+' locdc -> monitord : OK
+@enduml
\ No newline at end of file