Go to file
joeduffy 7162f6ea52 Publish proper pre-release PyPI packages
The semantic versions we were using for pre-release PyPI packages wasn't
quite right.  We had been using local version identifiers, a la +, rather
than proper pre-release tags, which means that version specifications like
`pulumi==0.11.0` will match `0.11.0+dev.1521506136.g7f043fd.dirty`, in
addition to just `0.11.0`.  This is clearly not what we want.

This change moves us over to proper alpha and release candidate versions,
as specified in https://www.python.org/dev/peps/pep-0440/#pre-releases.
Namely, any `x.y.z-dev-123456789-abcdef` version will get translated into
an alpha `x.y.za12345679-abcdef`, and any `x.y.z-rc1` will get translated
into a proper release candidate `x.y.zrc1` version number.
2018-03-19 18:18:25 -07:00
build Use test-failures scripts from pulumi/home 2018-03-08 11:40:17 -08:00
cmd Assume --remote when --cloud-url is set (#1060) 2018-03-18 12:44:00 -07:00
examples Pass legacy config mapping from nodejs langhost 2018-03-13 23:16:38 -07:00
pkg Fix panic when getting logs for older stacks (#1053) 2018-03-15 13:26:43 -07:00
scripts Fix make_release.sh when run from outside scripts directory 2018-03-19 14:24:52 -07:00
sdk Publish proper pre-release PyPI packages 2018-03-19 18:18:25 -07:00
tests Assume --remote when --cloud-url is set (#1060) 2018-03-18 12:44:00 -07:00
.appveyor.yml Pass legacy config mapping from nodejs langhost 2018-03-13 23:16:38 -07:00
.gitignore Download and use a custom Node binary instead of linking against 2018-02-13 14:04:01 -08:00
.travis.yml Use a class for Output serialization to ensure that .apply exists on it. (#1040) 2018-03-12 16:27:00 -07:00
.yarnrc Pass --network-concurrency 1 to yarn 2018-01-29 11:49:42 -08:00
build.proj Add get-version.cmd and use it 2018-03-16 16:36:27 -07:00
CHANGELOG.md Use per stack key for local stacks instead of per project 2018-01-19 00:50:59 -08:00
CONTRIBUTING.md Remove a few outdated references (#997) 2018-03-04 13:34:20 -08:00
Gometalinter.json Add additional linting (#768) 2017-12-27 17:10:12 -08:00
Gopkg.lock Use os/user for home directory 2018-02-20 15:35:07 -08:00
Gopkg.toml Make some stack-related CLI improvements (#947) 2018-02-16 15:03:54 -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 Adopt new version strategy 2018-03-15 18:06:04 -07:00
README.md Update README.md to use a valid CLI command 2018-02-22 14:26:04 -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 preview --logtostderr -v=5

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