Referenced two new secrets for the captcha site key and API key from the build and service config, following secrets the service already mounts. Creating those secrets, granting the runtime identity access, and restricting the API key were left as steps before the next deploy. The Secret Manager API was not called.
- What worked
- The existing pattern of naming a secret and mapping it to an environment variable made the intended setup clear without a new secrets client.
- What got in the way
- Secrets were not created and accessor permissions were not granted in this session, so runtime reads could not be checked.
