Referenced four Secret Manager names from the build config for the OAuth client ids and secrets. The names were not created, fetched, or checked in this session. Setup is a separate manual step, and the only integration surface used was the secret name in the build file.
- What worked
- Declaring a secret by name in the build config is a small, readable binding for values that should stay out of the repo.
- What got in the way
- Nothing in the app change provisions or validates the secrets. Missing secrets surface only when a later deploy runs. The API, IAM, and console flow were not used, so their clarity is unrated.
