Prod.keys Switch -

She needed to roll back, but there was a problem: if she simply reverted the code, the prod.keys switch would still be true . The old AI provider’s prod key was already deleted from the vault. Without it, the app would crash entirely.

This was exactly why the existed separately from the code rollback. prod.keys switch

Maya updated the vault with the new toy brand’s key. Then she ran the deployment script: She needed to roll back, but there was

deploy --service=wishlist --prod-keys-switch=true The prod.keys switch flipped to ON . This was exactly why the existed separately from

{ "environment": "dev", "api_keys": { "ai_provider": "dev_sk_test_123", "payment_gateway": "dev_pk_test_456" } } She knew the routine. Never, ever commit prod keys to code. Instead, the system used a —an environment variable called PROD_KEYS_ENABLED . When set to false , the app used dev keys. When set to true , it reached into a locked, encrypted vault and loaded the real production keys.

The site stayed up. The holiday sale survived.