Using Pulumi Deployments
This page provides an overview of how to use Pulumi Deployments to automate your infrastructure deployments.
Getting Started with Deployments
Pulumi Deployments are configured on a per-stack basis. To use Deployments effectively, follow these steps:
- Configure Deployment Settings: First, set up your deployment settings which include source code location, cloud credentials, environment variables, and build requirements.
- Set Up Triggers: Configure how deployment triggers are initiated. A common pattern is to:
- Run a
pulumi preview
when a PR is created - Run a
pulumi up
when a PR is merged to main
- Run a
- Expand Your Usage: As you grow more comfortable with Deployments, consider using additional features:
- Drift detection to automatically detect when your infrastructure differs from its desired state
- Review stacks for temporary environments on PRs
- TTL stacks for ephemeral environments
- Post-deployment automation to create webhooks to trigger additional actions, like updating additional stacks
- Webhooks for custom automation
Automating at Scale
For teams managing many stacks or platforms serving multiple teams, you can automate Deployments at scale using:
- The Pulumi Cloud Provider: Manage deployment settings as code
- The REST API: Programmatically control all aspects of Deployments
Additional Resources
- Private Repositories and Packages: Configure access to private Git repositories and package feeds
Thank you for your feedback!
If you have a question about how to use Pulumi, reach out in Community Slack.
Open an issue on GitHub to report a problem or suggest an improvement.