Update a blueprint service
Persists new values for a deployed blueprint service. Intended to be called after reviewing the diff returned by GET /blueprint//update.
variables and spec_overrides follow JSON Merge Patch (RFC 7396) semantics: non-null value on a key upserts it, null value removes it, absent keys are left untouched, and passing null for the whole field leaves all existing values unchanged.
Note: name, tag, and icon are required on every call.
Authorizations
JWT tokens should be used with OIDC account (human to machine). JWT tokens used by the Qovery console to communicate with the API have a TTL. Curl Example ' curl https://console.qovery.com/organization -H "Authorization: Bearer $qovery_token" '
Path Parameters
Blueprint ID
Body
Display name for the service
"my-postgres"
Catalog tag identifying the target blueprint version
"aws/postgres/17/1.1.0"
Icon URL for the service
"https://cdn.qovery.com/icons/postgresql.svg"
RFC 7396 patch map keyed by variable name. Non-null value upserts the variable; null value removes it. Absent keys are left untouched. Omitting the field entirely is equivalent to an empty map — no variables are modified.
JSON Merge Patch (RFC 7396) applied to the stored spec_overrides (see BlueprintSpecOverrides for the list of valid fields). A non-null field value upserts the override; a null value removes it. Pass null or omit the field entirely to leave all existing overrides unchanged.
{
"engine_version": "1.13.3",
"credentials": "cluster",
"backend": "qovery"
}