deploy.env.exportThe environment as .env text — plain values, references, secret names; no secret values
GET /deploy/api/apps/{id}/env/exportIAM deploy:ManageEnvChanges stateDestructive
Request syntax
GET /deploy/api/apps/{id}/env/exportPath parameters
idRequiredstring
Constraints: uuid
Response
200 with `data`: `content` (the .env text: plain values, op:// references, other secrets as ews-secret://NAME, and the variables bindings generate, as comments) and `count` (the number of variables set on the app).
A JSON response is wrapped as { "success": true, "data": … }; the CLI prints the whole body with --json.
Fields of data
contentAlwaysstring
The .env textcountAlwaysnumber
Number of variables set on the app
Checked against the handlers: every route test validates their answers against this schema.
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:ManageEnv 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 deploy env export idcurl -X GET "https://console.platform-development.deutschecloud.app/deploy/api/apps/id/env/export" \
-H "Authorization: EWS-ACCESS-KEY $ACCESS_KEY"Generated from the API description, the same one the API checks requests against and the CLI is built from. MCP tool: dcloud_deploy_env_export.