The file turns on Data Access logs for Secret Manager and Cloud KMS, so every secret read and every key use names its
principal. It encrypts every secret with the project's own rotating Cloud KMS key, which Secret Manager's service agent
alone may use; disabling that key cuts every secret off at once. It declares each Deployment Reader — an outside agent
that diagnoses the deployment — with read-only project roles and access granted one secret at a time. A reader cannot
read the Data Access logs, so the record of its own reads stays with the operators. Hold back from any reader the
secrets that act beyond the deployment: a Git App key, release or writer tokens, OAuth signing keys, and paid-message
credentials.
Name a provider credential the same in every project and give each environment its own key at the provider, so revoking
one never breaks another. A model provider key, such as TYPESAFE_API_KEY, waits on that provider's zero data retention
confirmation before any client mail is sent to it.