# client.deployments.values

> client.deployments.values — the deployments.values operations.

`client.deployments.values` — the `deployments.values` operations.

On `AsyncKindgi` every method is the same, awaited.

## `client.deployments.values.list()`

```python signature
list(
    deployment_id: str | UUID,
    /,
    *,
    project_id: str | UUID | None = None,
    timeout: float | None = None,
) -> DeploymentValueList
```

List the values a deployment needs in a project. `GET /v1/deployments/{deploymentId}/values`

Every value the deployment needs set in the project before it serves there: each tool's secrets and env values with no default, a model key for each agent version it ships or carries, and the pack service's own env. Each is read where a run in that project reads it, under the env the runtime serves: `foundAt` says where it's set, and `problem` why it isn't ready. Names only, never a value. In the deployment's own project, a value is found wherever it's set. In another project, the one a promotion would take it to, a tool's secret counts only at a scope the caller administers, as a promotion by the caller would record it, so the list says what that promotion's check would say. Needs what listing secrets in that project needs (`admin` on it), `read` on the project the deployment serves, and `read` on the tenant, as every deployments route does.