We changed the `pulumi update` command to be `pulumi up` a while back
(`update` is an alias of `up`). This change just makes it so we refer to
the actual command, `pulumi up`, instead of the older `pulumi update`.
Instead of duplicating information about how to build Pulumi from
source in both `README.md` and `CONTRIBUTING.md`, just have the
`README.md` point at `CONTRIBUTING.md`.
Fixes#2197
This change spiffs up the README a little bit, by adding badges and
other goodies:
* Add a logo image, rather than just text.
* Add some badges
- Slack
- NPM version
- PyPI version
- GoDoc APIs
- License
I'm sure we can add more, but this livens things up a bit.
* Wordsmith the introductory text for SEO and some extra oomph.
* Add a Welcome section with important links to Getting Started,
Tutorials, Examples, A Tour of Pulumi, Reference Docs, and
Community Slack. Pin a nice image of our console to the right.
* Add a Getting Started section which extends the existing "how to
install" section slightly to cover a bit more ground. Ultimately,
pulumi.io is the source of truth here, but having it here seems handy.
Almost all of this has been superceded by official design docs which,
as part of pulumi/home#29 will be moving to pulumi/design-notes.
Those that aren't will be done as new design docs in the future, since
most of the remainder are vastly out of date and/or aspirational at best.
Resolvespulumi/pulumi#408.
This includes a few changes:
* The repo name -- and hence the Go modules -- changes from pulumi-fabric to pulumi.
* The Node.js SDK package changes from @pulumi/pulumi-fabric to just pulumi.
* The CLI is renamed from lumi to pulumi.
We are renaming Lumi to Pulumi Fabric. This change simply renames the
pulumi/lumi repo to pulumi/pulumi-fabric, without the CLI tools and other
changes that will follow soon afterwards.
We are now on our fourth vendoring tool: Govendor. This appears to
be about 10X faster than Dep, fails less frequently, and has a rich,
well documented set of commands (that make far more intuitive sense
to me, particularly when compared to Dep). I could never really get
Godep to work with vendor/ correctly, whereas Govendor did the trick
right away. Lastly, Terraform uses it, so we'll probably have fewer
headaches in that department also.
There isn't a pre-canned Glide distribution for amd64 linux, and the
integration with Glide and Travis isn't nearly as swanky as with Godep
(which essentially works out of the box). Furthermore, Godep has caught
up with Go's vendoring changes since last time I looked, which was the
primary reason I ended up going with Glide in the first place.
