Thse changes make a subtle but critical adjustment to the process the Pulumi engine uses to determine whether or not a difference exists between a resource's actual and desired states, and adjusts the way this difference is calculated and displayed accordingly. Today, the Pulumi engine get the first chance to decide whether or not there is a difference between a resource's actual and desired states. It does this by comparing the current set of inputs for a resource (i.e. the inputs from the running Pulumi program) with the last set of inputs used to update the resource. If there is no difference between the old and new inputs, the engine decides that no change is necessary without consulting the resource's provider. Only if there are changes does the engine consult the resource's provider for more information about the difference. This can be problematic for a number of reasons: - Not all providers do input-input comparison; some do input-state comparison - Not all providers are able to update the last deployed set of inputs when performing a refresh - Some providers--either intentionally or due to bugs--may see changes in resources whose inputs have not changed All of these situations are confusing at the very least, and the first is problematic with respect to correctness. Furthermore, the display code only renders diffs it observes rather than rendering the diffs observed by the provider, which can obscure the actual changes detected at runtime. These changes address both of these issues: - Rather than comparing the current inputs against the last inputs before calling a resource provider's Diff function, the engine calls the Diff function in all cases. - Providers may now return a list of properties that differ between the requested and actual state and the way in which they differ. This information will then be used by the CLI to render the diff appropriately. A provider may also indicate that a particular diff is between old and new inputs rather than old state and new inputs. Fixes #2453. |
||
---|---|---|
build | ||
cmd | ||
dist | ||
examples | ||
pkg | ||
scripts | ||
sdk | ||
tests | ||
.appveyor.yml | ||
.dockerignore | ||
.gitignore | ||
.golangci.yml | ||
.travis.yml | ||
.yarnrc | ||
build.proj | ||
CHANGELOG.md | ||
CODE-OF-CONDUCT.md | ||
CONTRIBUTING.md | ||
go.mod | ||
go.sum | ||
LICENSE | ||
main.go | ||
Makefile | ||
README.md | ||
tslint.json |
Pulumi's Infrastructure as Code SDK is the easiest way to create and deploy cloud software 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 Platform, and/or Kubernetes resources, using an 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.
For example, create three web servers:
let aws = require("@pulumi/aws");
let sg = new aws.ec2.SecurityGroup("web-sg", {
ingress: [{ protocol: "tcp", fromPort: 80, toPort: 80, cidrBlocks: ["0.0.0.0/0"]}],
});
for (let i = 0; i < 3; i++) {
new aws.ec2.Instance(`web-${i}`, {
ami: "ami-7172b611",
instanceType: "t2.micro",
securityGroups: [ sg.name ],
userData: `#!/bin/bash
echo "Hello, World!" > index.html
nohup python -m SimpleHTTPServer 80 &`,
});
}
Or a simple serverless timer that archives Hacker News every day at 8:30AM:
const cloud = require("@pulumi/cloud");
const snapshots = new cloud.Table("snapshots");
cloud.timer.daily("daily-yc-snapshot", { hourUTC: 8, minuteUTC: 30 }, () => {
const req = require("https").get("https://news.ycombinator.com", res => {
let content = "";
res.setEncoding("utf8");
res.on("data", chunk => content += chunk);
res.on("end", () => snapshots.insert({ date: Date.now(), content }));
});
req.end();
});
Many examples are available spanning containers, serverless, and infrastructure in pulumi/examples.
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.
Welcome
![](https://pulumi.io/images/quickstart/console.png)
-
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.
-
Roadmap: check out what's on the roadmap for the Pulumi project over the coming months.
Getting Started
Follow these steps to deploy your first Pulumi program, using AWS Serverless Lambdas, in minutes:
-
Install:
To install the latest Pulumi release, run the following (see full installation instructions for additional installation options):
$ 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
pulumi new
command:$ pulumi new hello-aws-javascript
The
new
command offers templates for all languages and clouds. Run it without an argument and it'll prompt you with available projects. This command created an AWS Serverless Lambda project written in JavaScript. -
Deploy to the Cloud:
Run
pulumi up
to get your code to the cloud:$ pulumi up
This makes all cloud resources needed to run your code. Simply make edits to your project, and subsequent
pulumi up
s 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
Please head on over to the project website for much more information, including tutorials, examples, and an interactive tour of the core Pulumi CLI and programming model concepts.
Platform
CLI
Architecture | Build Status |
---|---|
Linux/macOS x64 | |
Windows x64 |
Languages
Language | Status | Runtime | |
---|---|---|---|
![]() |
JavaScript | Stable | Node.js 8+ |
![]() |
TypeScript | Stable | Node.js 8+ |
![]() |
Python | Preview | Python 3.6+ |
![]() |
Go | Preview | Go 1.x |
Clouds
See Supported Clouds for the full list of supported cloud and infrastructure providers.
Libraries
There are several libraries that encapsulate best practices and common patterns:
Library | Status | Docs | Repo |
---|---|---|---|
AWS Serverless | Preview | Docs | pulumi/pulumi-aws-serverless |
AWS Infrastructure | Preview | Docs | pulumi/pulumi-aws-infra |
Pulumi Multi-Cloud Framework | Preview | Docs | pulumi/pulumi-cloud |
Contributing
Please See CONTRIBUTING.md for information on building Pulumi from source or contributing improvments.