curl --request GET \
--url https://api.qovery.com/job/{jobId}/advancedSettings \
--header 'Authorization: Bearer <token>'{
"build.timeout_max_sec": 123,
"build.cpu_max_in_milli": 123,
"build.ram_max_in_gib": 123,
"build.disable_buildkit_cache": true,
"deployment.termination_grace_period_seconds": 123,
"deployment.affinity.node.required": {},
"job.delete_ttl_seconds_after_finished": 123,
"cronjob.concurrency_policy": "<string>",
"cronjob.failed_jobs_history_limit": 123,
"cronjob.success_jobs_history_limit": 123,
"security.service_account_name": "<string>",
"security.automount_service_account_token": true,
"security.read_only_root_filesystem": true
}Get list and values of the advanced settings of the job. Default values for each setting are available in our documentation
curl --request GET \
--url https://api.qovery.com/job/{jobId}/advancedSettings \
--header 'Authorization: Bearer <token>'{
"build.timeout_max_sec": 123,
"build.cpu_max_in_milli": 123,
"build.ram_max_in_gib": 123,
"build.disable_buildkit_cache": true,
"deployment.termination_grace_period_seconds": 123,
"deployment.affinity.node.required": {},
"job.delete_ttl_seconds_after_finished": 123,
"cronjob.concurrency_policy": "<string>",
"cronjob.failed_jobs_history_limit": 123,
"cronjob.success_jobs_history_limit": 123,
"security.service_account_name": "<string>",
"security.automount_service_account_token": true,
"security.read_only_root_filesystem": true
}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" '
Job ID
Advanced settings list
define the max timeout for the build
define the max cpu resources (in milli)
define the max ram resources (in gib)
disable buildkit registry cache during build
define how long in seconds an application is supposed to be stopped gracefully
Set pod placement on specific Kubernetes nodes labels
Show child attributes
Allows you to set an existing Kubernetes service account name
Automount Kubernetes service account token to have access to Kubernetes API from pods
Mounts the container's root filesystem as read-only
Was this page helpful?