List application env secrets
list_application_env_secretsRead the environment secrets an Application's generated manifests declare: every key, whether it has a value yet, which keys are still missing, the Kubernetes Secrets the deploy renders them into (secret_names - a monorepo's components each read one named after themselves, so there can be more than one), and whether what is RUNNING already carries the current values (apply_state: applied, pending, unknown, or not_deployed). Read requirements_state BEFORE missing_keys: an empty missing_keys means 'nothing is missing' only under 'known'. Under 'unknown' Ankra could not establish what the Application needs - no manifest is recorded yet, or the manifests read an env Secret it does not fill (unfilled_secrets names it) - and neither missing_keys nor any key's required flag is a claim about the Application, so do not report it as fully configured. This is the read to reach for when a deployed Application crashes on startup or reports missing configuration - a key with no value, or an apply_state of 'pending', explains it. A secret's value is never returned by this or any other route: secrets are reported by key and state only. The Application's shared plain values (configuration that is not a credential, sealed into the same Secret) are listed in plain_values with their values, and a key a plain value fills is set, not missing; plain_values is null when they could not be read, and plain_values_unreadable says why - never report that as the Application having none. Read-only.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"application_id": "<application_id>"
},
"name": "list_application_env_secrets"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| application_id | Yes | The Application's id. |