secrets.environments.set-app-environmentSet which environment an app’s secret names resolve in (null: shared only)
PUT /secrets/api/apps/{appId}/environmentIAM deploy:UpdateAppChanges stateDestructive
Request syntax
PUT /secrets/api/apps/{appId}/environment
{
"environmentId": "string"
}Path parameters
appIdRequiredstring
Constraints: uuid
Request body
environmentIdRequiredstring
The environment the app’s secret names resolve in (its own secret, else the Default one), or null for Default values only. An unknown environment id is 404.
May be null.
Response
200 with { appId, environmentId }, the setting now in force. 404 for an unknown app or environment.
A JSON response is wrapped as { "success": true, "data": … }; the CLI prints the whole body with --json.
Errors
- 400The request does not pass the schema above. The body is { "error": …, "issues": […] }, one issue per field.
- 401No credentials, or an access key that is unknown, revoked or expired.
- 403The caller's policies do not allow deploy:UpdateApp on this resource. The body names the action and the resource, and the refusal is recorded in the audit log.
- 404The resource does not exist in your organization.
Examples
The required parameters only, with example values. Replace id and the other placeholders with your own.
dcloud secrets environments set-app-environment appId --environment-id examplecurl -X PUT "https://console.platform-development.deutschecloud.app/secrets/api/apps/appId/environment" \
-H "Authorization: EWS-ACCESS-KEY $ACCESS_KEY" \
-H "Content-Type: application/json" \
-d '{"environmentId":"example"}'Generated from the API description, the same one the API checks requests against and the CLI is built from. MCP tool: dcloud_secrets_environments_set-app-environment.