From f75e76b3b78938ffcf35db1950759f3c1b29da0c Mon Sep 17 00:00:00 2001 From: "@permadeath.com" Date: Tue, 11 Aug 2026 14:23:06 -0400 Subject: [PATCH] docs: fix stale AWS_PROFILE claim in DEVELOPING.md The recent scripts/ merge dropped the forced AWS_PROFILE and now uses whatever working credentials the caller already has. The doc still said the opposite. --- DEVELOPING.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/DEVELOPING.md b/DEVELOPING.md index ae9c84e..1eb669b 100644 --- a/DEVELOPING.md +++ b/DEVELOPING.md @@ -2,7 +2,8 @@ Working on the running infrastructure. Assumes `AWS_PROFILE=lance-blue` and a checkout of this repo; run `tofu` commands from `envs/lance.blue`. The scripts -under `scripts/` set their own `AWS_PROFILE` and ignore yours. +under `scripts/` use whatever working credentials you already have — env var, +SSO session, instance role, named profile — and fail fast if there are none. ## A shell on the api host -- 2.51.2