From bad54b28bcc59fe5d19ecaf486f52e6359009e68 Mon Sep 17 00:00:00 2001 From: Karen Arutyunov Date: Tue, 21 May 2024 13:48:43 +0300 Subject: Add support for build_unloaded() notification for tenant-associated services --- doc/manual.cli | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) (limited to 'doc') diff --git a/doc/manual.cli b/doc/manual.cli index 2b96393..9b85ae6 100644 --- a/doc/manual.cli +++ b/doc/manual.cli @@ -344,6 +344,7 @@ timestamp: [service-id]: [service-type]: [service-data]: +[service-action]: \ The \c{package} value can be repeated multiple times. The \c{timestamp} value @@ -356,7 +357,14 @@ required information via some custom protocol, and expect the CI service to notify it about the progress. In this case the third-party service type as well as optionally the third-party id and custom state data can be communicated to the underlying CI handler program via the respective -\c{service-*} manifest values. +\c{service-*} manifest values. Also note that normally a third-party service +has all the required information (repository URL, etc) available at the time +of the CI task initiation, in which case the \c{start} value is specified for +the \c{service-action} manifest value. If that's not the case, the CI task is +only created at the time of the initiation without calling the CI handler +program. In this case the CI handler is called later, when all the required +information is asynchronously gathered by the service. In this case the +\c{load} value is specified for the \c{service-action} manifest value. \h#ci-overrides-manifest|CI Overrides Manifest| -- cgit v1.1