Back

Create an API key and store it in a secret manager

A new scoped API key saved in your secret manager, with a masked summary of its location

Engineering
Prompt

Create a new API key in [service and project, e.g. Google Cloud project app-prod] and store it in [secret manager and location, e.g. Doppler project backend, config prd]. Name the key [key name, e.g. payments-service-prod] and restrict it to [scopes or limits, e.g. read-only, one API only] if the service allows it. First check whether a key or secret with that name already exists. If it does, stop and ask whether to rotate, reuse, or rename. Never overwrite an existing secret without my okay. Copy the key straight from the service into the secret manager as [secret name, e.g. PAYMENTS_API_KEY]. Don't paste it into chat, notes, or any file, and never show it to me in full. Stop and ask at any billing prompt, terms screen, or permission error. When done, give me a short summary: service, project, key name, restrictions applied, secret path, and the key's last four characters so I can confirm it matches.