Pulumi Deployment Settings
Deployment settings refer to the full set of configuration required to run a Pulumi Deployment, defined on a per-stack basis. These settings can be managed through the Pulumi Cloud UI, via the REST API, or defined as code with the Pulumi Cloud provider.
Creating deployment settings
You can create and manage deployment settings in several ways:
From the Pulumi Cloud UI
From the Pulumi Cloud console, a stack’s deployment settings can be accessed via the Settings > Deploy tab. Once the settings are defined via the UI, they apply to all Deployment triggers, including push-to-deploy (if you have a VCS integration configured), click-to-deploy and the REST API.
From the API
Alternatively, a stack’s deployment settings may be defined and subsequently modified using the REST API. For more information, see Patch Settings in the Pulumi Deployments REST API docs.
Defined as code with the Pulumi Cloud provider
Finally, a stack’s deployment settings may be defined as a resource within the stack itself using the Pulumi Cloud provider. This lets you securely store your settings in source control alongside your code. For more information, see the pulumiservice.DeploymentSettings resource docs in the Pulumi Registry.
pulumiService.DeploymentSettings resource that defines settings for the current stack), as this would require two deployments for the settings changes to take effect. Instead, create a separate Pulumi program that defines Deployment Settings for multiple stacks that share similar configuration.In this section
- Source settings — where a deployment gets the Pulumi program it runs: a version control integration, a Git URL, a template, or none.
- Path filtering — trigger deployments only when a push changes files you care about, especially useful for monorepos.
- Tag filtering — trigger deployments when a matching git tag is pushed, for release-based workflows.
- Deployment runner pools — choose where deployments run, and assign the organization role a deployment uses.
- Pre-run commands — run arbitrary shell commands before a deployment starts, for setup or authentication.
- Skipping automatic dependency installation — take control of the dependency installation step yourself.
- Skipping intermediate deployments — collapse a backlog of queued deployments into a single run.
- Custom executor images — override the default image to pin a Pulumi version or add your own tools.
- Dependency caching — speed up deployments by caching downloaded dependencies between runs.
- Environment variables — the variables Pulumi sets automatically, and how to define your own.
To authenticate with cloud providers using short-lived credentials instead of static secrets, see the OIDC setup guide. For task-oriented walkthroughs — supplying cloud credentials, building custom images, and more — see the Deployments guides.