PiCloud

Files

MechaCat02 62710b5d81 feat(cli): §3 M3 — per-env approval gating ([project.environments])

A `[project.environments]` block maps an env name to `{ confirm = bool }`
(`ManifestProject.environments`, client-side only — `skip_serializing`).
`pic apply --env <e>` is refused before any request when `<e>` is
confirm-required unless it is explicitly `--approve <e>`d; a blanket `--yes`
does NOT cover a gated env (§4.2 "CI must opt in per environment"); an unlisted
or `confirm = false` env applies freely. `require_env_approval` gates both the
single (`run`) and tree (`run_tree`) apply paths; `--approve <env>` is a
repeatable flag. Per-env value overlays (`picloud.<env>.toml`) already merge
client-side, so this is the confirm-policy gate only.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

2026-07-07 20:28:28 +02:00

cmds

feat(cli): §3 M3 — per-env approval gating ([project.environments])

2026-07-07 20:28:28 +02:00

client.rs

feat(apply): §6 M2 — structural-divergence detection + declarative reparent

2026-07-07 20:23:10 +02:00

config.rs

feat(cli): real auth, delete commands, api-keys, JSON output, env override

2026-05-29 23:33:44 +02:00

discover.rs

feat(apply): §6 M1 — declarative group create (directory-nesting parentage)