QOqovery
Container Secret

Create a secret alias at the container level

  • Allows you to add an alias at container level on an existing secret having higher scope, in order to customize its key.
  • You only have to specify a key in the request body
  • The system will create a new secret at container level with the same value as the one corresponding to the secret id in the path
  • The response body will contain the newly created secret
  • Information regarding the aliased_secret will be exposed in the "aliased_secret" field of the newly created secret
  • You can't create an alias on an alias
post/container/{containerId}/secret/{secretId}/alias

Request

Path parameters

containerIdstring uuid required

Container ID

secretIdstring uuid required

Secret ID

Request body

keystring required
descriptionstring nullable

optional variable description (255 characters maximum)

enable_interpolation_in_fileboolean nullable

Response

Create secret alias

idstring uuid required
created_atstring date-time required
updated_atstring date-time
keystring required

key is case sensitive

scope'APPLICATION' | 'BUILT_IN' | 'ENVIRONMENT' | 'PROJECT' | 'CONTAINER' | 'JOB' | 'HELM' | 'TERRAFORM' required
variable_type'VALUE' | 'ALIAS' | 'OVERRIDE' | 'BUILT_IN' | 'FILE'

type of the environment variable (VALUE, FILE, ALIAS, OVERRIDE or BUIT_IN)

service_idstring uuid
service_namestring
service_type'APPLICATION' | 'CONTAINER' | 'DATABASE' | 'JOB' | 'HELM' | 'TERRAFORM'

type of the service (application, database, job, gateway...)

owned_bystring

Entity that created/own the variable (i.e: Qovery, Doppler)

descriptionstring nullable

optional variable description (255 characters maximum)

enable_interpolation_in_fileboolean nullable

Example response

{
  "aliased_secret": {
    "key": "QOVERY_DATABASE_PSQL_NAME"
  }
}

Changes

No recorded changes to this operation across all 1 revision of this API.