Reference
Qovery project variables
Variables every environment in a Qovery project inherits.
Variables every environment in a Qovery project inherits.
Connection
| What | This provider |
|---|---|
| Vendor | Qovery |
| Key | qovery-project-variable |
| Availability | available. You can connect it today. |
| Credential we hold | qovery-token |
| Values read back | yes |
| Activation | on-next-deploy |
Directions
| 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. |
Activation
on-next-deploy. A new value waits there and arrives with your next deploy.
Conflict policies
| 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.
Connect
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. |
Mapping fields
You answer these once per environment you map.
| Field | Label | Kind | Required | Advanced | What it is |
|---|---|---|---|---|---|
projectId | Project | text | yes | no | Every environment in this project reads what the sync writes here. |