secure
secrets
Set Multi Key Secret
Changed onStores multiple key-value pairs under a single secret name in the key store. NOTE: {secret_name} is legacy and is not used - calculated automatically
Args: secret_name (str): The secret name (legacy, not used - kept for backward compatibility). secret_keys (SecretKeyModel): The secret key/value pairs to set.
Returns: OperationResponse: The operation response.
put/api/v1/secrets/{secret_name}
Request
- Base URL/ (relative, and the document was published on a file host, not at the API’s origin)
- URL/api/v1/secrets/{secret_name}
- AuthHTTP bearer
Path parameters
secret_namestring required
Request body
Secret Key Model required
Example request
{
"TARGET_DB_PASSWORD": "password",
"TARGET_DB_USERNAME": "admin"
}Response
Secrets were set successfully
Changes
- info
added the non-success response with the status
- info
- breaking
added the new path request parameter
secret_name
- breaking