The Pulumi Cloud Development Platform is the easiest way to create and deploy cloud programs that use containers, serverless functions, hosted services, and infrastructure, on any cloud.
Simply write code in your favorite language and Pulumi automatically provisions and manages your AWS, Azure, Google Cloud, and/or Kubernetes resources, using an immutable infrastructure-as-code approach. Skip the YAML, and use standard language features like loops, functions, classes, and package management that you already know and love.
Pulumi is open source under the Apache 2.0 license, supports many languages and clouds, and is easy to extend. This
repo contains the
pulumi CLI, language SDKs, and core Pulumi engine, and individual libraries are in their own repos.
Getting Started: get up and running quickly.
Tutorials: walk through end-to-end workflows for creating containers, serverless functions, and other cloud services and infrastructure.
Examples: browse a number of useful examples across many languages, clouds, and scenarios including containers, serverless, and infrastructure.
A Tour of Pulumi: interactively walk through the core Pulumi concepts, one at a time, covering the entire CLI and programming model surface area in a handful of bite-sized chunks.
Reference Docs: read conceptual documentation, in addition to details on how to configure Pulumi to deploy into your AWS, Azure, or Google Cloud accounts, and/or Kubernetes cluster.
Community Slack: join us over at our community Slack channel. Any and all discussion or questions are welcome.
Follow these steps to deploy your first Pulumi program, using AWS Serverless Lambdas, in minutes:
To install the latest Pulumi release, run:
$ curl -fsSL https://get.pulumi.com/ | sh
Configure your Cloud Provider so that Pulumi can deploy into it.
Create a Project:
After installing, you can get started with the
Deploy to the Cloud:
pulumi updateto get your code to the cloud:
$ pulumi update
This makes all cloud resources needed to run your code. Simply make edits to your project, and subsequent
pulumi updates will compute the minimal diff to deploy your changes.
Use Your Program:
Now that your code is deployed, you can interact with it. In the above example, we can curl the endpoint:
$ curl $(pulumi stack output url)
Access the Logs:
If you're using containers or functions, Pulumi's unified logging command will show all of your logs:
$ pulumi logs -f
Destroy your Resources:
After you're done, you can remove all resources created by your program:
$ pulumi destroy -y
|Amazon Web Services||Stable||Docs|
|Google Cloud Platform||Preview||Docs|
There are several libraries that encapsulate best practices and common patterns:
|Pulumi Multi-Cloud Framework||Preview||Docs||pulumi/pulumi-cloud|
If you'd like to contribute to Pulumi and/or build from source, this section is for you.
Pulumi is written in Go, uses Dep for dependency management, and GoMetaLinter for linting:
- Go: https://golang.org/dl
$ go get -u github.com/golang/dep/cmd/dep
$ go get -u github.com/alecthomas/gometalinter
$ gometalinter --install
Building and Testing
To install the pre-built SDK, please run
curl -fsSL https://get.pulumi.com/ | sh, or see detailed installation instructions on the project page. Read on if you want to install from source.
To build a complete Pulumi SDK, ensure
$GOPATH is set, and clone into a standard Go workspace:
$ git clone firstname.lastname@example.org:pulumi/pulumi $GOPATH/src/github.com/pulumi/pulumi $ cd $GOPATH/src/github.com/pulumi/pulumi
The first time you build, you must
make ensure to install dependencies and perform other machine setup:
$ make ensure
In the future, you can synch dependencies simply by running
dep ensure explicitly:
$ dep ensure
At this point you can run
make to build and run tests:
This installs the
pulumi binary into
$GOPATH/bin, which may now be run provided
make exited successfully.
The Makefile also supports just running tests (
make test_all or
make test_fast), just running the linter
make lint), just running Govet (
make vet), and so on. Please just refer to the Makefile for the full list of targets.
The Pulumi tools have extensive logging built in. In fact, we encourage liberal logging in new code, and adding new logging when debugging problems. This helps to ensure future debugging endeavors benefit from your sleuthing.
All logging is done using Google's Glog library. It is relatively bare-bones, and adds basic leveled logging, stack dumping, and other capabilities beyond what Go's built-in logging routines offer.
pulumi command line has two flags that control this logging and that can come in handy when debugging problems.
--logtostderr flag spews directly to stderr, rather than the default of logging to files in your temp directory.
--verbose=n flag (
-v=n for short) sets the logging level to
n. Anything greater than 3 is reserved for
debug-level logging, greater than 5 is going to be quite verbose, and anything beyond 7 is extremely noisy.
For example, the command
$ pulumi preview --logtostderr -v=5
is a pretty standard starting point during debugging that will show a fairly comprehensive trace log of a compilation.