
Clever Cloud Deployments Trigger
CertifiedTrigger when a Clever Cloud application deployment reaches a target state
Clever Cloud Deployments Trigger
Trigger when a Clever Cloud application deployment reaches a target state
Polls the deployment list for a given application at each interval. Fires an execution when a DEPLOY action deployment transitions to the configured target state.
Only DEPLOY action records are considered. UNDEPLOY records (e.g. from scaling or moderation) are intentionally ignored so the trigger does not fire for infrastructure events unrelated to a code deployment.
Dedup is timestamp-based: only deployments whose date (epoch milliseconds) is strictly after the previous evaluation cutoff are considered, preventing re-fires on already-seen deployments.
When organisationId is omitted, the personal account endpoint (/self) is used.
Real state values from the Clever Cloud API: OK (success), FAIL (error), CANCELLED, WIP (in-progress).
type: io.kestra.plugin.clevercloud.deployments.TriggerExamples
Fire when a deployment succeeds
id: on_deploy_ok
namespace: company.team
triggers:
- id: watch_deploy
type: io.kestra.plugin.clevercloud.deployments.Trigger
apiToken: "{{ secret('CC_API_TOKEN') }}"
organisationId: "orga_xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"
applicationId: "app_xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"
targetState: OK
interval: PT1M
tasks:
- id: log
type: io.kestra.plugin.core.log.Log
message: "Deployment {{ trigger.deploymentId }} succeeded (commit {{ trigger.commit }})"
Fire when a personal account deployment succeeds
id: on_personal_deploy_ok
namespace: company.team
triggers:
- id: watch_deploy
type: io.kestra.plugin.clevercloud.deployments.Trigger
apiToken: "{{ secret('CC_API_TOKEN') }}"
applicationId: "app_xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"
targetState: OK
interval: PT1M
tasks:
- id: log
type: io.kestra.plugin.core.log.Log
message: "Deployment {{ trigger.deploymentId }} succeeded (commit {{ trigger.commit }})"
Properties
apiToken *string
API token
Bearer token for the Clever Cloud API. Store as a Kestra secret and reference with {{ secret('CC_API_TOKEN') }}.
applicationId *string
Application ID to watch
targetState *string
WIPOKFAILCANCELLEDTarget deployment state that causes the trigger to fire
Accepts: OK (successful deploy), FAIL (failed deploy), CANCELLED. The API returns deployments newest-first. Bursts of more than maxDeployments deployments between two polls may be missed.
allowConcurrent boolean
falseSpecifies whether a trigger is allowed to start a new execution even if a previous run is still in progress.
interval string
PT1MdurationHow often to check for new deployments
ISO-8601 duration. Minimum PT30S is recommended to avoid overloading the API. Defaults to PT1M.
maxDeployments integerstring
25Maximum number of deployments to fetch per poll
The API returns results newest-first. Increase this value if deployments may arrive faster than the poll interval. Bursts beyond this limit between polls may be missed. Defaults to 25.
options
HTTP client options
Optional HttpConfiguration applied to every Clever Cloud API call, including timeouts and proxy settings.
io.kestra.core.http.client.configurations.HttpConfiguration
falseIf true, allow a failed response code (response code >= 400)
List of response code allowed for this request
The authentication to use.
io.kestra.core.http.client.configurations.BasicAuthConfiguration
The password for HTTP basic authentication.
The username for HTTP basic authentication.
io.kestra.core.http.client.configurations.BearerAuthConfiguration
The token for bearer token authentication.
io.kestra.core.http.client.configurations.DigestAuthConfiguration
The password for HTTP Digest authentication.
The username for HTTP Digest authentication.
UTF-8The default charset for the request.
java.nio.charset.Charset
trueWhether to enable TCP Keep-Alive extended socket options (TCP_KEEPIDLE, TCP_KEEPINTERVAL, TCP_KEEPCOUNT).
Set to false when running on Windows workers, as these extended socket options are not supported by the Windows JDK and will cause connection failures.
trueWhether redirects should be followed automatically.
REQUEST_HEADERSREQUEST_BODYRESPONSE_HEADERSRESPONSE_BODYThe enabled log.
The proxy configuration.
io.kestra.core.http.client.configurations.ProxyConfiguration
The address of the proxy server.
The password for proxy authentication.
The port of the proxy server.
DIRECTDIRECTHTTPSOCKSThe type of proxy to use.
The username for proxy authentication.
Retry strategy for HTTP requests.
retry is disabled by default.
Constant retry
Retry with a fixed delay between attempts.
durationRETRY_FAILED_TASKRETRY_FAILED_TASKCREATE_NEW_EXECUTION>= 1durationfalseExponential retry
Retry with exponentially increasing delays between attempts.
durationdurationRETRY_FAILED_TASKRETRY_FAILED_TASKCREATE_NEW_EXECUTION>= 1durationfalseRandom retry
Retry with a random delay within a configurable range between attempts.
durationdurationRETRY_FAILED_TASKRETRY_FAILED_TASKCREATE_NEW_EXECUTION>= 1durationfalse[502,503,504]HTTP status codes that should be retried.
Used for idempotent methods (GET, HEAD) without their own entry in retryOnStatusCodesByMethod. Non-idempotent methods are never retried on a status code unless listed in retryOnStatusCodesByMethod. Defaults to 502, 503 and 504 for idempotent methods (GET, HEAD) only.
Per-HTTP-method overrides for which status codes should be retried.
Keys are HTTP methods (e.g. GET, POST). A method with no entry here falls back to retryOnStatusCodes. This lets a caller retry more broadly for safe, read-only methods (for example, every 5xx and a 429 for GET/HEAD) while keeping a narrower list for methods that write, where retrying a request that may have already been processed by the origin risks duplicating the effect. Example: {GET: [429, 500, 502, 503, 504], HEAD: [429, 500, 502, 503, 504]}.
["GET","HEAD"]HTTP methods for which any transport-level failure may be retried.
A transport-level failure is a connection or timeout error rather than an HTTP response (e.g. a read timeout or a connection reset mid-request). For a method listed here, any such failure is retried. Defaults to GET and HEAD HTTP methods.
The SSL request options
io.kestra.core.http.client.configurations.SslOptions
Whether to disable checking of the remote SSL certificate.
Only applies if no trust store is configured. Note: This makes the SSL connection insecure and should only be used for testing. If you are using a self-signed certificate, set up a trust store instead.
The timeout configuration.
io.kestra.core.http.client.configurations.TimeoutConfiguration
The time allowed to establish a connection to the server before failing.
PT5MThe time allowed for a read connection to remain idle before closing it.
organisationId string
Organisation ID
When omitted, the personal account endpoint (/self) is used instead.
stopAfter array
CREATEDSUBMITTEDRUNNINGPAUSEDRESTARTEDKILLINGSUCCESSWARNINGFAILEDKILLEDCANCELLEDQUEUEDRETRYINGRETRIEDSKIPPEDBREAKPOINTRESUBMITTEDList of execution states after which a trigger should be stopped (a.k.a. disabled).
when string
trueA condition that determines whether the trigger should run.
A Pebble expression evaluated at trigger time. The trigger fires only when the expression evaluates to a truthy value (true, a non-empty string, a non-zero number). Use this to gate trigger execution on dynamic runtime values such as execution labels, flow variables, or environment conditions.
Outputs
commit string
Git commit SHA associated with this deployment
deploymentId string
Deployment ID that matched the target state
state string
State of the deployment when the trigger fired