Go to file
Matthew Riley 660e08b2f7 Do a better job of uploading failed test artifacts to S3
Uploading a bunch of tiny files is inefficient. Worse, it results in a ton of
paths printed to `stdout` -- enough that we could hit Travis' 4MB limit and
kill the job before we'd finished uploading.

Now we create a `.tar.gz` and upload that one, compressed file.

We also noticed that copied files might not be accessible from the `dev`
account, even though that account owns the `eng.pulumi.com` bucket. When
files are uploaded by one AWS account to a bucket owned by another, the
objects are, by default, only readable by the first account (the writer).
Change the ACL so the account that owns the bucket also has full access.
2018-02-15 22:01:25 -08:00
build Copy the package.json with its semver expanded (#864) 2018-01-31 10:34:21 -08:00
cmd Rename package to project (#935) 2018-02-14 13:56:16 -08:00
dist/sdk/nodejs Missed a pulumi-langhost-nodejs batch wrapper 2018-02-09 21:25:32 -08:00
examples Rename pulumi package to @pulumi/pulumi (#917) 2018-02-12 13:13:13 -08:00
pkg Rename package to project (#935) 2018-02-14 13:56:16 -08:00
scripts Revert "Revert Windows changes to unblock npm ingestion" 2018-02-13 15:07:07 -08:00
sdk Use relative path in langhost launcher 2018-02-14 17:55:48 -08:00
tests Yarn link pulumi in history tests 2018-02-14 17:55:48 -08:00
.appveyor.yml Build release branches in CI 2018-02-09 13:42:16 -08:00
.gitignore Download and use a custom Node binary instead of linking against 2018-02-13 14:04:01 -08:00
.gitmodules Remove stale submodules 2017-05-15 10:33:22 -07:00
.travis.yml Do a better job of uploading failed test artifacts to S3 2018-02-15 22:01:25 -08:00
.yarnrc Pass --network-concurrency 1 to yarn 2018-01-29 11:49:42 -08:00
build.proj Fix download_node.ps1; remove ensure_custom_v8 2018-02-13 16:00:02 -08:00
CHANGELOG.md Use per stack key for local stacks instead of per project 2018-01-19 00:50:59 -08:00
CONTRIBUTING.md Adopt new pulumi/home repo name 2017-09-21 14:09:35 -07:00
Gometalinter.json Add additional linting (#768) 2017-12-27 17:10:12 -08:00
Gopkg.lock Add "pulumi history" command (#826) 2018-01-24 18:22:41 -08:00
Gopkg.toml Lock gRPC to v1.7.2 2017-12-27 06:35:52 -08:00
LICENSE Clarify aspects of using the DCO 2017-06-26 14:46:34 -07:00
main.go Add a manifest to checkpoint files (#630) 2017-12-01 13:50:32 -08:00
Makefile Delete the old IDL compiler (#801) 2018-01-13 15:11:52 -08:00
README.md Updates to the readme: fix up some documentation regarding the Makefile (#861) 2018-01-30 16:31:02 -08:00
tslint.json Enable 'use const' linter rule. (#405) 2017-10-10 14:50:55 -07:00

Pulumi Fabric

The Pulumi Fabric ("Pulumi") is a framework and toolset for creating reusable cloud services.

If you are learning about Pulumi for the first time, please visit our docs website.

Build Status

Architecture Build Status
Linux x64 Linux x64 Build Status
Windows x64 Windows x64 Build Status

Installing

To install Pulumi from source, simply run:

$ go get -u github.com/pulumi/pulumi

A GOPATH must be set. A good default value is ~/go. In fact, this is the default in Go 1.8.

This installs the pulumi binary to $GOPATH/bin.

To do anything interesting with Pulumi, you will need an SDK for your language of choice. Please see sdk/README.md for information about how to obtain, install, and use such an SDK.

Development

This section is for Pulumi developers.

Prerequisites

Pulumi is written in Go, uses Dep for dependency management, and GoMetaLinter for linting:

Building and Testing

To build Pulumi, ensure $GOPATH is set, and clone into a standard Go workspace:

$ git clone git@github.com: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:

$ make

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.

Debugging

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.

The pulumi command line has two flags that control this logging and that can come in handy when debugging problems. The --logtostderr flag spews directly to stderr, rather than the default of logging to files in your temp directory. And the --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 eval --logtostderr -v=5

is a pretty standard starting point during debugging that will show a fairly comprehensive trace log of a compilation.