From 52f05efc23d395b0ea9a1e113e34d7b979ff2558 Mon Sep 17 00:00:00 2001 From: "Christophe Noel (Spacebel)" Date: Wed, 20 Dec 2023 16:19:54 +0100 Subject: [PATCH] Create REC_body-argo.adoc added argo --- .../deploy/REC_body-argo.adoc | 15 +++++++++++++++ 1 file changed, 15 insertions(+) create mode 100644 extensions/deploy_replace_undeploy/standard/recommendations/deploy-replace-undeploy/deploy/REC_body-argo.adoc diff --git a/extensions/deploy_replace_undeploy/standard/recommendations/deploy-replace-undeploy/deploy/REC_body-argo.adoc b/extensions/deploy_replace_undeploy/standard/recommendations/deploy-replace-undeploy/deploy/REC_body-argo.adoc new file mode 100644 index 00000000..6f2358c6 --- /dev/null +++ b/extensions/deploy_replace_undeploy/standard/recommendations/deploy-replace-undeploy/deploy/REC_body-argo.adoc @@ -0,0 +1,15 @@ +[[rec_deploy-replace-undeploy_deploy_body-argo]] +[recommendation] +==== +[%metadata] +label:: /rec/deploy-replace-undeploy/deploy/body-argo + +part:: If a process can be represented for the intended use as a <>, implementations should consider supporting the <> encoding for describing the process to be deployed to the API. + +part:: The media type `application/argo` shall be used to indicate that request body contains a processes description encoded as a <>. + +part:: If the Argo contains more than one workflow, an additional `w` query parameter may be used to reference the workflow id to be deployed. + +part:: The server should validate the Argo at the request time. In case, the server cannot find the `w` identifier within the workflow from the Argo provided, a 400 status code is expected with the type "worflow-not-found". + +====