Qovery service variables

Variables one Qovery service reads, the narrowest scope Qovery offers.

Connection

What	This provider
Vendor	Qovery
Key	`qovery-service-variable`
Availability	`available`. You can connect it today.
Credential we hold	`qovery-token`
Values read back	yes
Activation	`on-next-deploy`

Direction	What it does
`import`	We read names and values out of the store into your environment.
`export`	We write names and values from your environment into the store.

on-next-deploy. A new value waits there and arrives with your next deploy.

Direction	Policies you can pick
`import`	`skip_existing`, `new_version`, `fail`
`export`	`create_only`, `overwrite`, `overwrite_and_prune`

How syncs work says what each one does.

Paste a credential from the vendor. We seal it and never show it again.

Field	Label	Kind	Required	What it is
`token`	API token	secret; we mask it here and seal it	yes	Qovery sends an API token with the Token scheme rather than Bearer.

You answer these once per environment you map.

Field	Label	Kind	Required	Advanced	What it is
`serviceId`	Service	text	yes	no	The service ID from its Qovery console URL.
`serviceType`	Service type	choice	yes	yes	Which family the service belongs to, since the ID alone does not say. One of Application, Container, Job. Starts at `application`.