Create a service account
Give it the Secret Manager Admin role on the project you want to sync into, and download the JSON key.
Google Cloud Secret Manager Integration
Connect a service account and we push each variable into Secret Manager in your GCP project. Cloud Run, GKE and Cloud Functions read them exactly as before, we just keep the values current.
Follow this flow and your variables are synced in minutes.
Give it the Secret Manager Admin role on the project you want to sync into, and download the JSON key.
We read the project ID from it and check that the Secret Manager API is enabled before we let you connect.
Defaults to the environment name. Two environments syncing into one project need different prefixes, and we warn you if they match.
Manually, or automatically on every change if you turn that on.
Everything needed to operate Google Cloud Secret Manager secrets from EnvManager.
DATABASE_URL becomes a secret called PROD_DATABASE_URL, with the value as its latest version.
We compare against the current version first. Unchanged variables get no new version, so you are not paying for versions that are all identical.
When a value changes we disable the previous version. It stays in the console if you ever need to look back.
Secrets carry managed-by=envmanager and the environment name, so gcloud secrets list can filter down to exactly what we manage.
A service account usually sees one project anyway. Several projects? Add a connection for each.
API not enabled, wrong project, missing role: the validate step tells you which one it is instead of a generic "invalid credentials".
Enabling the API, creating the service account with the right role, and how labels and versions behave once you sync.
14-day free trial. Connect Google Cloud Secret Manager and sync your first variables in under 5 minutes.