Переменные окружения проекта
env_varsDestructive
Project environment variables: list names, set them, remove them.
VALUES ARE NEVER READ BACK — not by you, not by the platform in its
response. Only names and lengths are returned. This is a deliberate rule
rather than an implementation limit: anything that reaches your answer
settles into the conversation history, and a secret that lands there
cannot be taken back. If the user asks "what is my key", say plainly
that you cannot show it and offer to set a new one.
`set` does not require knowing the other variables — the platform keeps
them. `unset` removes only the named ones.
A change needs a new deploy: variables are picked up at build time, not
on the fly. Say so, or the user will think nothing happened.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| keys | No | For `action="unset"`: names of the variables to remove. | |
| action | No | `list` — show the names (values are never returned), `set` — set the variables from `values`, `unset` — remove the variables listed in `keys`. | list |
| values | No | For `action="set"`: name → value pairs. The project's other variables are kept — no need to send them again. | |
| project | Yes | The project: its slug (`my-site`) or id, as listed by `my_projects`. The site address works too (`https://clear-garden-vypm.layero.app` or just `clear-garden-vypm`) — note that the address host is NOT always the slug. |
Output Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| changed | No | ||
| project | Yes | ||
| variables | Yes | ||
| next_action | Yes |