9a8f8881c0
This change supports displaying manifest information for a stack and changes the way we handle Snapshots in our backend. Previously, every call to GetStack would synthesize a Snapshot by taking the set of resources returned from the `/api/stacks/<owner>/<name>` endpoint, combined with an empty manfiest (since the service was not returning the manifest). This wasn't great for two reasons: 1. We didn't have manifest information, so we couldn't display any of its information (most important the last updated time). 2. This strategy required that the service return all the resources for a stack anytime GetStack was called. While the CLI did not often need this detailed information the fact that we forced the Service to produce it (which in the case of stack managed PPC would require the service to talk to yet another service) creates a bunch of work that we end up ignoring. I've refactored the code such that `backend.Stack`'s `Snapshot()` method now lazily requests the information from the service such that we can construct a `Snapshot()` on demand and only pay the cost when we actually need it. I think making more of this stuff lazy is the long term direction we want to follow. Unfortunately, right now, it means in cases where we do need this data we end up fetching it twice. The service does it once when we call GetStack and then we do it again when we actually need to get at the Snapshot. However, once we land this change, we can update the service to no longer return resources on the apistack.Stack type. The CLI no longer needs this property. We'll likely want to continue in a direction where `apistack.Stack` can be created quickly by the service (without expensive database queries or fetching remote resources) and just add additional endpoints that let us get at the specific information we want in the specific cases when we want it instead of forcing us to return a bunch of data that we often ignore. Fixes pulumi/pulumi-service#371 |
||
|---|---|---|
| build | ||
| cmd | ||
| dist | ||
| examples | ||
| pkg | ||
| scripts | ||
| sdk | ||
| tests | ||
| .appveyor.yml | ||
| .gitignore | ||
| .travis.yml | ||
| .yarnrc | ||
| build.proj | ||
| CHANGELOG.md | ||
| CONTRIBUTING.md | ||
| Gometalinter.json | ||
| Gopkg.lock | ||
| Gopkg.toml | ||
| LICENSE | ||
| main.go | ||
| Makefile | ||
| README.md | ||
| tslint.json | ||
Pulumi
Pulumi is a framework and toolset for creating reusable cloud services.
This repo contains the core SDKs, CLI, and libraries, most notably the Pulumi Engine itself.
If you are learning about Pulumi for the first time, please visit our docs website.
Build Status
| Architecture | Build Status |
|---|---|
| Linux/macOS x64 |  |
| Windows x64 |
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:
- Go: https://golang.org/dl
- Dep:
$ go get -u github.com/golang/dep/cmd/dep - GoMetaLinter:
$ go get -u github.com/alecthomas/gometalinter$ gometalinter --install
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.