Native Marketplace integrations now support custom environments
By Steven Van ·
Marketplace database and storage connections can now target custom environments like staging, not just production and preview, on Pro and Enterprise plans.
Resources connected through the Vercel Marketplace, such as Postgres or Redis databases, can now be scoped to custom environments instead of only production, preview, and development. A staging deployment can use its own staging database without adding those variables to Production or Preview in Project Settings.
The environment is chosen when connecting a resource, from the dashboard, the CLI, or the REST API. From the CLI, for example: vercel integration add neon --environment staging. Existing deployments keep their current variables; a new deployment is needed after connecting a resource or changing its environment scope. Custom environments are available on the Pro and Enterprise plans.
Read the announcement for details on the dashboard flow, the CLI --environment flag, and the REST API's envVarEnvironments field.