Path Filtering

When using a VCS integration and push-to-deploy, you may want a deployment to trigger only when a push changes files you care about. You can do this with path filters. This is especially useful for monorepos, where a single repository holds multiple Pulumi programs and you want each stack to deploy only when its own files change.

Writing filters

Each filter is a glob pattern matched against the full path of every file changed by a push, relative to the repository root. A pattern must match the entire path:

• infrastructure/Pulumi.dev.yaml matches only that one file.
• infrastructure/** matches every file anywhere under the infrastructure/ directory.

A filter is an include filter by default. Prefix it with ! to make it an exclude filter:

• infrastructure/** — include changes under infrastructure/.
• !infrastructure/docs/** — exclude changes under infrastructure/docs/.

How filters are evaluated

A push triggers a deployment when at least one changed file matches the filters. An individual file matches when both of these are true:

1. It matches at least one include filter (or no include filters are configured), and
2. It does not match any exclude filter.

A few consequences worth knowing:

• No filters: every push triggers a deployment.
• Only exclude filters: every file is included unless an exclude filter matches it.
• Exclude always wins. If a file matches an exclude filter, it is excluded even when it also matches an include filter. The order in which you list filters does not matter.

!foo/**
foo/bar/**