Skip to main content
POST
Resolve a platform component configuration of the cluster

Authorizations

Authorization
string
header
required

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

clusterId
string<uuid>
required

Cluster ID

componentKey
string
required

Platform component key

Body

application/json
profileConfig
object

Configuration values keyed by their catalog field name

replaceProfileConfig
boolean
default:false

For an existing cluster, validate profileConfig as a complete draft instead of merging it with saved values. Omitted keys are reset to their catalog defaults. Template previews already use a complete draft and ignore this flag.

clusterInputs
object
componentOutputs
object

String values keyed first by component key and then by input key

Response

Resolved component configuration

clusterId
string<uuid>
required
componentKey
string
required
fields
object[]
required

Generic catalog field descriptor matching the shared q-core field response. Scalar fields retain their existing shape; objects and arrays describe nested configuration without flattening its values. Blueprint keeps its existing BlueprintManifestVariableField response contract through a dedicated adapter.

requirements
object[]
required
componentBindings
object[]
required
violations
object[]
required