Reference
Qovery project variables
Variables every environment in a Qovery project inherits.
Variables every environment in a Qovery project inherits.
The connection
| What | This provider |
|---|---|
| Vendor | Qovery |
| Key | qovery-project-variable |
| Availability | available. You can connect it today. |
| Credential penv holds | qovery-token |
| Values read back | yes |
| Activation | on-next-deploy |
What it moves
| Direction | What it does |
|---|---|
import | Reads names and values out of the store into penv. |
export | Writes names and values from penv into the store. |
When a written value goes live
on-next-deploy. A new value waits there and arrives with your next deploy.
What happens to a name that exists
| 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.
How you connect
You paste a credential you already hold. penv seals it and never shows it again.
| Field | Label | Kind | Required | What it is |
|---|---|---|---|---|
token | API token | secret, masked here and sealed | yes | Qovery sends an API token with the Token scheme rather than Bearer. |
What a mapping asks for
Answered 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. |