Update to FastAPI Cloud

{
  "description": "Manage FastAPI Cloud environment variables and secrets. Use when listing, reading, setting, deleting, or auditing FastAPI Cloud env vars, handling runtime secrets, or diagnosing missing configuration for a deployed FastAPI app.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 192
    }
  ],
  "name": "fastapicloud-env",
  "skill_md_contents": "---\nname: fastapicloud-env\ndescription: \"Manage FastAPI Cloud environment variables and secrets. Use when listing, reading, setting, deleting, or auditing FastAPI Cloud env vars, handling runtime secrets, or diagnosing missing configuration for a deployed FastAPI app.\"\n---\n\n# FastAPI Cloud Env\n\n## Overview\n\nInspect and manage FastAPI Cloud environment variables while protecting secret values. FastAPI Cloud CLI supports the `fastapi cloud env` commands and `--json` output used here.\n\n## CLI Baseline\n\nThe mutation workflow below requires FastAPI Cloud CLI `0.26.0` or newer. Start with the `fastapi cloud env ...` command needed for the task, such as:\n\n```bash\nuv run fastapi cloud env --help\n```\n\nOnly check the CLI version after a `uv run fastapi cloud ...` command fails because `fastapi`, `cloud`, or the requested subcommand is missing, or because the output suggests an incompatible CLI:\n\n```bash\nuv run fastapi cloud --version\nuv run fastapi cloud --help\n```\n\nIf `fastapi` is missing or the cloud command surface is stale, install or update `fastapi[standard]`; do not install `fastapi-cli` directly as the executable source. The `fastapi[standard]` extra provides the `fastapi` command and the FastAPI Cloud CLI integration. These commands change project files, so ask the user before running them in an existing project.\n\n```bash\nuv add -U \"fastapi[standard]\"\nuv lock --upgrade-package fastapi --upgrade-package fastapi-cloud-cli\n```\n\nIf the project cloud CLI reports a version older than `0.26.0`, update the project environment before using the mutation workflow below.\n\n## JSON Output\n\nUse `--json` whenever the command supports it.\n\n## Integrations First For Managed Services\n\nIf the user asks to connect a database, cache, observability platform, or another managed service—not to set a specific named variable—check FastAPI Cloud integrations first. A supported integration should manage its app configuration instead of requiring the user to copy provider credentials manually:\n\n```bash\nuv run fastapi cloud integrations providers list --json\n```\n\nUse the `fastapicloud-integrations` workflow when a matching provider is available. Fall back to manual environment variables only when no integration supports the service or the user explicitly prefers manual configuration.\n\n## Read First\n\n```bash\nuv run fastapi cloud env list --path . --json\nuv run fastapi cloud env get NAME --path . --json\n```\n\nUse `--app-id APP_ID` when the directory is not linked or the user names a specific app.\n\nThe CLI does not show secret values in `env list` or `env get` output. Do not try to recover secret values from local files, shell history, or other sources unless the user explicitly asks for that audit.\n\n## Mutations\n\nOnly set or delete env vars when the user explicitly asks. Do not echo secrets in chat or shell history.\n\n`env set` creates a variable or updates its value if it already exists. Both `env set` and `env delete` request an app redeploy by default. Use `--no-redeploy` when saving changes without deploying, or on intermediate changes when setting several variables before one final redeploy.\n\nFor secret values, prefer stdin:\n\n```bash\nuv run fastapi cloud env set NAME --value-stdin --secret --path . --json\n```\n\n`--secret` marks a new variable as secret. Existing variables keep their secret status, even when this flag is supplied or omitted. Read the existing variable first and use the returned `is_secret` field to verify its status; do not assume `--secret` converts an existing non-secret variable into a secret.\n\nFor non-secret values:\n\n```bash\nuv run fastapi cloud env set NAME VALUE --path . --json\n```\n\nFor deletion:\n\n```bash\nuv run fastapi cloud env delete NAME --path . --yes --json\n```\n\nDeletion succeeds even if the named variable is already absent.\n\nTo save or delete without redeploying:\n\n```bash\nuv run fastapi cloud env set NAME VALUE --no-redeploy --path . --json\nuv run fastapi cloud env delete NAME --no-redeploy --path . --yes --json\n```\n\nIntegration-managed variables cannot be changed through these commands. Follow the integrations workflow if the backend reports that a variable is managed by a connected resource.\n\n## Notes\n\n- Changes saved with `--no-redeploy` need a later deployment before the running app observes them. A successful env command does not establish that a redeployment has completed successfully.\n- When debugging missing config, inspect app logs after env changes.\n- Treat `.env` files as local-only; do not commit secrets.\n"
}