From add3170119dc2b9f465505d69ba6284f47c8b69c Mon Sep 17 00:00:00 2001
From: Jedrzej Rybicki <j.rybicki@fz-juelich.de>
Date: Wed, 4 May 2022 10:03:50 +0200
Subject: [PATCH] vault specific connection creation
---
docs/apirequests.adoc | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/docs/apirequests.adoc b/docs/apirequests.adoc
index 3b5d9a6..29165b0 100644
--- a/docs/apirequests.adoc
+++ b/docs/apirequests.adoc
@@ -20,6 +20,11 @@ curl -X POST -u USER:PASS -H "Content-Type: application/json" \
There should be an object created in B2SHARE, each object in B2SHARE is identified by a +id+, which needs to be passed to the DLS workflow as a parameter (see below).
+Vault Connection is a little bit specific to set up. It cannot be setup through the UI, the connection type needs to be vaults (with s for secure connection), it can be done through API:
+curl -X POST -u USER:PASS -H "Content-Type: application/json" \
+ --data '{"connection_id": "my_vault","conn_type":"vaults", "host": "zam10039.zam.kfa-juelich.de", "password": VAULTPASS}' \
+ $DLS/connections
+
=== Credentials handling [[credentials]]
Credentials needed to access SSH-based storages should be passed over to the pipelines (both for up- and download) as pipelines parameters. Basically each DLS pipelines can be extended by tasks to handle those parameters and convert them into connections that can be used in the remainings of the pipeline. The code for that can be found in <a href='dags/conn_deco.py'>+dags/conn_deco.py+</a>.
--
GitLab