Create a secret override at the job level
Job Secret
Create a secret override at the job level
- Allows you to override at job level a secret that has a higher scope.
- You only have to specify a value in the request body
- The system will create a new secret at job level with the same key as the one corresponding to the secret id in the path
- The response body will contain the newly created secret
- Information regarding the overridden_secret will be exposed in the “overridden_secret” field of the newly created secret
POST
Create a secret override at the job level
Documentation Index
Fetch the complete documentation index at: https://qovery-update-kubecost-tuto.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
Authorizations
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" '
Body
application/json
Response
Create secret override
key is case sensitive
Available options:
APPLICATION, BUILT_IN, ENVIRONMENT, PROJECT, CONTAINER, JOB, HELM, TERRAFORM type of the environment variable (VALUE, FILE, ALIAS, OVERRIDE, BUIT_IN, EXTERNAL_SECRET)
Available options:
VALUE, ALIAS, OVERRIDE, BUILT_IN, FILE, EXTERNAL_SECRET type of the service (application, database, job, gateway...)
Available options:
APPLICATION, CONTAINER, DATABASE, JOB, HELM, TERRAFORM Entity that created/own the variable (i.e: Qovery, Doppler)
optional variable description (255 characters maximum)
Maximum string length:
255