2017-08-02 03:37:06 +02:00
|
|
|
# This file is autogenerated, do not edit; changes may be undone by the next 'dep ensure'.
|
|
|
|
|
|
|
|
|
2018-04-10 21:03:11 +02:00
|
|
|
[[projects]]
|
|
|
|
branch = "master"
|
|
|
|
name = "github.com/Azure/go-ansiterm"
|
|
|
|
packages = [
|
|
|
|
".",
|
|
|
|
"winterm"
|
|
|
|
]
|
|
|
|
revision = "d6e3b3328b783f23731bc4d058875b0371ff8109"
|
|
|
|
|
2018-04-20 00:55:24 +02:00
|
|
|
[[projects]]
|
|
|
|
name = "github.com/Nvveen/Gotty"
|
|
|
|
packages = ["."]
|
|
|
|
revision = "a8b993ba6abdb0e0c12b0125c603323a71c7790c"
|
|
|
|
source = "https://github.com/ijc25/Gotty"
|
|
|
|
|
2018-04-10 21:03:11 +02:00
|
|
|
[[projects]]
|
|
|
|
name = "github.com/Sirupsen/logrus"
|
|
|
|
packages = ["."]
|
|
|
|
revision = "c155da19408a8799da419ed3eeb0cb5db0ad5dbc"
|
|
|
|
version = "v1.0.5"
|
|
|
|
|
2017-11-09 02:08:51 +01:00
|
|
|
[[projects]]
|
|
|
|
name = "github.com/apache/thrift"
|
|
|
|
packages = ["lib/go/thrift"]
|
|
|
|
revision = "b2a4d4ae21c789b689dd162deb819665567f481c"
|
|
|
|
version = "0.10.0"
|
|
|
|
|
2017-11-09 21:38:03 +01:00
|
|
|
[[projects]]
|
|
|
|
name = "github.com/aws/aws-sdk-go"
|
Make some stack-related CLI improvements (#947)
This change includes a handful of stack-related CLI formatting
improvements that I've been noodling on in the background for a while,
based on things that tend to trip up demos and the inner loop workflow.
This includes:
* If `pulumi stack select` is run by itself, use an interactive
CLI menu to let the user select an existing stack, or choose to
create a new one. This looks as follows
$ pulumi stack select
Please choose a stack, or choose to create a new one:
abcdef
babblabblabble
> currentlyselected
defcon
<create a new stack>
and is navigated in the usual way (key up, down, enter).
* If a stack name is passed that does not exist, prompt the user
to ask whether s/he wants to create one on-demand. This hooks
interesting moments in time, like `pulumi stack select foo`,
and cuts down on the need to run additional commands.
* If a current stack is required, but none is currently selected,
then pop the same interactive menu shown above to select one.
Depending on the command being run, we may or may not show the
option to create a new stack (e.g., that doesn't make much sense
when you're running `pulumi destroy`, but might when you're
running `pulumi stack`). This again lets you do with a single
command what would have otherwise entailed an error with multiple
commands to recover from it.
* If you run `pulumi stack init` without any additional arguments,
we interactively prompt for the stack name. Before, we would
error and you'd then need to run `pulumi stack init <name>`.
* Colorize some things nicely; for example, now all prompts will
by default become bright white.
2018-02-17 00:03:54 +01:00
|
|
|
packages = [
|
|
|
|
"aws",
|
|
|
|
"aws/awserr",
|
|
|
|
"aws/awsutil",
|
|
|
|
"aws/client",
|
|
|
|
"aws/client/metadata",
|
|
|
|
"aws/corehandlers",
|
|
|
|
"aws/credentials",
|
|
|
|
"aws/credentials/ec2rolecreds",
|
|
|
|
"aws/credentials/endpointcreds",
|
|
|
|
"aws/credentials/stscreds",
|
|
|
|
"aws/defaults",
|
|
|
|
"aws/ec2metadata",
|
|
|
|
"aws/endpoints",
|
|
|
|
"aws/request",
|
|
|
|
"aws/session",
|
|
|
|
"aws/signer/v4",
|
|
|
|
"internal/shareddefaults",
|
|
|
|
"private/protocol",
|
|
|
|
"private/protocol/json/jsonutil",
|
|
|
|
"private/protocol/jsonrpc",
|
|
|
|
"private/protocol/query",
|
|
|
|
"private/protocol/query/queryutil",
|
|
|
|
"private/protocol/rest",
|
|
|
|
"private/protocol/restxml",
|
|
|
|
"private/protocol/xml/xmlutil",
|
|
|
|
"service/cloudwatchlogs",
|
|
|
|
"service/s3",
|
|
|
|
"service/sts"
|
|
|
|
]
|
2017-11-09 21:38:03 +01:00
|
|
|
revision = "e6c5e190452424b404ecdb81d6e3991d46b18e9d"
|
|
|
|
version = "v1.12.26"
|
|
|
|
|
2017-10-19 00:37:18 +02:00
|
|
|
[[projects]]
|
|
|
|
name = "github.com/bgentry/speakeasy"
|
|
|
|
packages = ["."]
|
|
|
|
revision = "4aabc24848ce5fd31929f7d1e4ea74d3709c14cd"
|
|
|
|
version = "v0.1.0"
|
|
|
|
|
Implement basic plugin management
This change implements basic plugin management, but we do not yet
actually use the plugins for anything (that comes next).
Plugins are stored in `~/.pulumi/plugins`, and are expected to be
in the format `pulumi-<KIND>-<NAME>-v<VERSION>[.exe]`. The KIND is
one of `analyzer`, `language`, or `resource`, the NAME is a hyphen-
delimited name (e.g., `aws` or `foo-bar`), and VERSION is the
plugin's semantic version (e.g., `0.9.11`, `1.3.7-beta.a736cf`, etc).
This commit includes four new CLI commands:
* `pulumi plugin` is the top-level plugin command. It does nothing
but show the help text for associated child commands.
* `pulumi plugin install` can be used to install plugins manually.
If run with no additional arguments, it will compute the set of
plugins used by the current project, and download them all. It
may be run to explicitly download a single plugin, however, by
invoking it as `pulumi plugin install KIND NAME VERSION`. For
example, `pulumi plugin install resource aws v0.9.11`. By default,
this command uses the cloud backend in the usual way to perform the
download, although a separate URL may be given with --cloud-url,
just like all other commands that interact with our backend service.
* `pulumi plugin ls` lists all plugins currently installed in the
plugin cache. It displays some useful statistics, like the size
of the plugin, when it was installed, when it was last used, and
so on. It sorts the display alphabetically by plugin name, and
for plugins with multiple versions, it shows the newest at the top.
The command also summarizes how much disk space is currently being
consumed by the plugin cache. There are no filtering capabilities yet.
* `pulumi plugin prune` will delete plugins from the cache. By
default, when run with no arguments, it will delete everything.
It may be run with additional arguments, KIND, NAME, and VERSION,
each one getting more specific about what it will delete. For
instance, `pulumi plugin prune resource aws` will delete all AWS
plugin versions, while `pulumi plugin prune resource aws <0.9`
will delete all AWS plugins before version 0.9. Unless --yes is
passed, the command will confirm the deletion with a count of how
many plugins will be affected by the command.
We do not yet actually download plugins on demand yet. That will
come in a subsequent change.
2018-02-04 19:51:29 +01:00
|
|
|
[[projects]]
|
|
|
|
name = "github.com/blang/semver"
|
|
|
|
packages = ["."]
|
|
|
|
revision = "2ee87856327ba09384cabd113bc6b5d174e9ec0f"
|
|
|
|
version = "v3.5.1"
|
|
|
|
|
2018-03-30 07:24:26 +02:00
|
|
|
[[projects]]
|
|
|
|
name = "github.com/cheggaaa/pb"
|
|
|
|
packages = ["."]
|
|
|
|
revision = "657164d0228d6bebe316fdf725c69f131a50fb10"
|
|
|
|
version = "v1.0.18"
|
|
|
|
|
2017-11-09 02:08:51 +01:00
|
|
|
[[projects]]
|
|
|
|
branch = "master"
|
|
|
|
name = "github.com/codahale/hdrhistogram"
|
|
|
|
packages = ["."]
|
|
|
|
revision = "3a0bb77429bd3a61596f5e8a3172445844342120"
|
|
|
|
|
2018-04-28 20:18:21 +02:00
|
|
|
[[projects]]
|
|
|
|
name = "github.com/cpuguy83/go-md2man"
|
|
|
|
packages = ["md2man"]
|
|
|
|
revision = "20f5889cbdc3c73dbd2862796665e7c465ade7d1"
|
|
|
|
version = "v1.0.8"
|
|
|
|
|
2017-08-02 03:37:06 +02:00
|
|
|
[[projects]]
|
|
|
|
name = "github.com/davecgh/go-spew"
|
|
|
|
packages = ["spew"]
|
|
|
|
revision = "346938d642f2ec3594ed81d874461961cd0faa76"
|
|
|
|
version = "v1.1.0"
|
|
|
|
|
Implement basic plugin management
This change implements basic plugin management, but we do not yet
actually use the plugins for anything (that comes next).
Plugins are stored in `~/.pulumi/plugins`, and are expected to be
in the format `pulumi-<KIND>-<NAME>-v<VERSION>[.exe]`. The KIND is
one of `analyzer`, `language`, or `resource`, the NAME is a hyphen-
delimited name (e.g., `aws` or `foo-bar`), and VERSION is the
plugin's semantic version (e.g., `0.9.11`, `1.3.7-beta.a736cf`, etc).
This commit includes four new CLI commands:
* `pulumi plugin` is the top-level plugin command. It does nothing
but show the help text for associated child commands.
* `pulumi plugin install` can be used to install plugins manually.
If run with no additional arguments, it will compute the set of
plugins used by the current project, and download them all. It
may be run to explicitly download a single plugin, however, by
invoking it as `pulumi plugin install KIND NAME VERSION`. For
example, `pulumi plugin install resource aws v0.9.11`. By default,
this command uses the cloud backend in the usual way to perform the
download, although a separate URL may be given with --cloud-url,
just like all other commands that interact with our backend service.
* `pulumi plugin ls` lists all plugins currently installed in the
plugin cache. It displays some useful statistics, like the size
of the plugin, when it was installed, when it was last used, and
so on. It sorts the display alphabetically by plugin name, and
for plugins with multiple versions, it shows the newest at the top.
The command also summarizes how much disk space is currently being
consumed by the plugin cache. There are no filtering capabilities yet.
* `pulumi plugin prune` will delete plugins from the cache. By
default, when run with no arguments, it will delete everything.
It may be run with additional arguments, KIND, NAME, and VERSION,
each one getting more specific about what it will delete. For
instance, `pulumi plugin prune resource aws` will delete all AWS
plugin versions, while `pulumi plugin prune resource aws <0.9`
will delete all AWS plugins before version 0.9. Unless --yes is
passed, the command will confirm the deletion with a count of how
many plugins will be affected by the command.
We do not yet actually download plugins on demand yet. That will
come in a subsequent change.
2018-02-04 19:51:29 +01:00
|
|
|
[[projects]]
|
|
|
|
name = "github.com/djherbis/times"
|
|
|
|
packages = ["."]
|
|
|
|
revision = "95292e44976d1217cf3611dc7c8d9466877d3ed5"
|
|
|
|
version = "v1.0.1"
|
|
|
|
|
2018-04-10 21:03:11 +02:00
|
|
|
[[projects]]
|
|
|
|
name = "github.com/docker/docker"
|
|
|
|
packages = [
|
|
|
|
"pkg/term",
|
|
|
|
"pkg/term/windows"
|
|
|
|
]
|
|
|
|
revision = "092cba3727bb9b4a2f0e922cd6c0f93ea270e363"
|
|
|
|
version = "v1.13.1"
|
|
|
|
|
2017-12-14 20:51:58 +01:00
|
|
|
[[projects]]
|
|
|
|
branch = "master"
|
|
|
|
name = "github.com/dustin/go-humanize"
|
|
|
|
packages = ["."]
|
|
|
|
revision = "bb3d318650d48840a39aa21a027c6630e198e626"
|
|
|
|
|
2017-11-09 21:38:03 +01:00
|
|
|
[[projects]]
|
|
|
|
name = "github.com/go-ini/ini"
|
|
|
|
packages = ["."]
|
|
|
|
revision = "a343d9870e3952dd8a0b894f9e221e210189fefe"
|
|
|
|
version = "v1.31.0"
|
|
|
|
|
2017-08-02 03:37:06 +02:00
|
|
|
[[projects]]
|
|
|
|
branch = "master"
|
|
|
|
name = "github.com/golang/glog"
|
|
|
|
packages = ["."]
|
|
|
|
revision = "23def4e6c14b4da8ac2ed8007337bc5eb5007998"
|
|
|
|
|
|
|
|
[[projects]]
|
|
|
|
branch = "master"
|
|
|
|
name = "github.com/golang/protobuf"
|
Make some stack-related CLI improvements (#947)
This change includes a handful of stack-related CLI formatting
improvements that I've been noodling on in the background for a while,
based on things that tend to trip up demos and the inner loop workflow.
This includes:
* If `pulumi stack select` is run by itself, use an interactive
CLI menu to let the user select an existing stack, or choose to
create a new one. This looks as follows
$ pulumi stack select
Please choose a stack, or choose to create a new one:
abcdef
babblabblabble
> currentlyselected
defcon
<create a new stack>
and is navigated in the usual way (key up, down, enter).
* If a stack name is passed that does not exist, prompt the user
to ask whether s/he wants to create one on-demand. This hooks
interesting moments in time, like `pulumi stack select foo`,
and cuts down on the need to run additional commands.
* If a current stack is required, but none is currently selected,
then pop the same interactive menu shown above to select one.
Depending on the command being run, we may or may not show the
option to create a new stack (e.g., that doesn't make much sense
when you're running `pulumi destroy`, but might when you're
running `pulumi stack`). This again lets you do with a single
command what would have otherwise entailed an error with multiple
commands to recover from it.
* If you run `pulumi stack init` without any additional arguments,
we interactively prompt for the stack name. Before, we would
error and you'd then need to run `pulumi stack init <name>`.
* Colorize some things nicely; for example, now all prompts will
by default become bright white.
2018-02-17 00:03:54 +01:00
|
|
|
packages = [
|
|
|
|
"proto",
|
|
|
|
"protoc-gen-go/descriptor",
|
|
|
|
"ptypes",
|
|
|
|
"ptypes/any",
|
|
|
|
"ptypes/duration",
|
|
|
|
"ptypes/empty",
|
|
|
|
"ptypes/struct",
|
|
|
|
"ptypes/timestamp"
|
|
|
|
]
|
2017-11-09 02:08:51 +01:00
|
|
|
revision = "1643683e1b54a9e88ad26d98f81400c8c9d9f4f9"
|
|
|
|
|
2017-12-22 02:16:45 +01:00
|
|
|
[[projects]]
|
|
|
|
branch = "master"
|
|
|
|
name = "github.com/google/go-querystring"
|
|
|
|
packages = ["query"]
|
|
|
|
revision = "53e6ce116135b80d037921a7fdd5138cf32d7a8a"
|
|
|
|
|
2018-05-08 03:23:03 +02:00
|
|
|
[[projects]]
|
|
|
|
name = "github.com/gorilla/context"
|
|
|
|
packages = ["."]
|
|
|
|
revision = "1ea25387ff6f684839d82767c1733ff4d4d15d0a"
|
|
|
|
version = "v1.1"
|
|
|
|
|
|
|
|
[[projects]]
|
|
|
|
name = "github.com/gorilla/mux"
|
|
|
|
packages = ["."]
|
|
|
|
revision = "53c1911da2b537f792e7cafcb446b05ffe33b996"
|
|
|
|
version = "v1.6.1"
|
|
|
|
|
2017-11-09 02:08:51 +01:00
|
|
|
[[projects]]
|
|
|
|
branch = "master"
|
|
|
|
name = "github.com/grpc-ecosystem/grpc-opentracing"
|
|
|
|
packages = ["go/otgrpc"]
|
|
|
|
revision = "01f8541d537215b2867e2745a1eb85c58c7c6b81"
|
2017-08-02 03:37:06 +02:00
|
|
|
|
2017-10-31 01:35:36 +01:00
|
|
|
[[projects]]
|
|
|
|
branch = "master"
|
|
|
|
name = "github.com/hashicorp/errwrap"
|
|
|
|
packages = ["."]
|
|
|
|
revision = "7554cd9344cec97297fa6649b055a8c98c2a1e55"
|
|
|
|
|
|
|
|
[[projects]]
|
|
|
|
branch = "master"
|
|
|
|
name = "github.com/hashicorp/go-multierror"
|
|
|
|
packages = ["."]
|
|
|
|
revision = "83588e72410abfbe4df460eeb6f30841ae47d4c4"
|
|
|
|
|
2017-08-02 03:37:06 +02:00
|
|
|
[[projects]]
|
|
|
|
name = "github.com/inconshreveable/mousetrap"
|
|
|
|
packages = ["."]
|
|
|
|
revision = "76626ae9c91c4f2a10f34cad8ce83ea42c93bb75"
|
|
|
|
version = "v1.0"
|
|
|
|
|
2018-01-25 03:22:41 +01:00
|
|
|
[[projects]]
|
|
|
|
branch = "master"
|
|
|
|
name = "github.com/jbenet/go-context"
|
|
|
|
packages = ["io"]
|
|
|
|
revision = "d14ea06fba99483203c19d92cfcd13ebe73135f4"
|
|
|
|
|
2017-11-09 21:38:03 +01:00
|
|
|
[[projects]]
|
|
|
|
name = "github.com/jmespath/go-jmespath"
|
|
|
|
packages = ["."]
|
|
|
|
revision = "0b12d6b5"
|
|
|
|
|
2018-01-25 03:22:41 +01:00
|
|
|
[[projects]]
|
|
|
|
name = "github.com/kevinburke/ssh_config"
|
|
|
|
packages = ["."]
|
|
|
|
revision = "fa48d7ff1cfb9f26c514b80d520880394293bf08"
|
|
|
|
version = "0.2"
|
|
|
|
|
Make some stack-related CLI improvements (#947)
This change includes a handful of stack-related CLI formatting
improvements that I've been noodling on in the background for a while,
based on things that tend to trip up demos and the inner loop workflow.
This includes:
* If `pulumi stack select` is run by itself, use an interactive
CLI menu to let the user select an existing stack, or choose to
create a new one. This looks as follows
$ pulumi stack select
Please choose a stack, or choose to create a new one:
abcdef
babblabblabble
> currentlyselected
defcon
<create a new stack>
and is navigated in the usual way (key up, down, enter).
* If a stack name is passed that does not exist, prompt the user
to ask whether s/he wants to create one on-demand. This hooks
interesting moments in time, like `pulumi stack select foo`,
and cuts down on the need to run additional commands.
* If a current stack is required, but none is currently selected,
then pop the same interactive menu shown above to select one.
Depending on the command being run, we may or may not show the
option to create a new stack (e.g., that doesn't make much sense
when you're running `pulumi destroy`, but might when you're
running `pulumi stack`). This again lets you do with a single
command what would have otherwise entailed an error with multiple
commands to recover from it.
* If you run `pulumi stack init` without any additional arguments,
we interactively prompt for the stack name. Before, we would
error and you'd then need to run `pulumi stack init <name>`.
* Colorize some things nicely; for example, now all prompts will
by default become bright white.
2018-02-17 00:03:54 +01:00
|
|
|
[[projects]]
|
|
|
|
name = "github.com/mattn/go-colorable"
|
|
|
|
packages = ["."]
|
|
|
|
revision = "167de6bfdfba052fa6b2d3664c8f5272e23c9072"
|
|
|
|
version = "v0.0.9"
|
|
|
|
|
|
|
|
[[projects]]
|
|
|
|
name = "github.com/mattn/go-isatty"
|
|
|
|
packages = ["."]
|
|
|
|
revision = "0360b2af4f38e8d38c7fce2a9f4e702702d73a39"
|
|
|
|
version = "v0.0.3"
|
|
|
|
|
2017-12-03 00:17:59 +01:00
|
|
|
[[projects]]
|
|
|
|
name = "github.com/mattn/go-runewidth"
|
|
|
|
packages = ["."]
|
|
|
|
revision = "9e777a8366cce605130a531d2cd6363d07ad7317"
|
|
|
|
version = "v0.0.2"
|
|
|
|
|
Make some stack-related CLI improvements (#947)
This change includes a handful of stack-related CLI formatting
improvements that I've been noodling on in the background for a while,
based on things that tend to trip up demos and the inner loop workflow.
This includes:
* If `pulumi stack select` is run by itself, use an interactive
CLI menu to let the user select an existing stack, or choose to
create a new one. This looks as follows
$ pulumi stack select
Please choose a stack, or choose to create a new one:
abcdef
babblabblabble
> currentlyselected
defcon
<create a new stack>
and is navigated in the usual way (key up, down, enter).
* If a stack name is passed that does not exist, prompt the user
to ask whether s/he wants to create one on-demand. This hooks
interesting moments in time, like `pulumi stack select foo`,
and cuts down on the need to run additional commands.
* If a current stack is required, but none is currently selected,
then pop the same interactive menu shown above to select one.
Depending on the command being run, we may or may not show the
option to create a new stack (e.g., that doesn't make much sense
when you're running `pulumi destroy`, but might when you're
running `pulumi stack`). This again lets you do with a single
command what would have otherwise entailed an error with multiple
commands to recover from it.
* If you run `pulumi stack init` without any additional arguments,
we interactively prompt for the stack name. Before, we would
error and you'd then need to run `pulumi stack init <name>`.
* Colorize some things nicely; for example, now all prompts will
by default become bright white.
2018-02-17 00:03:54 +01:00
|
|
|
[[projects]]
|
|
|
|
branch = "master"
|
|
|
|
name = "github.com/mgutz/ansi"
|
|
|
|
packages = ["."]
|
|
|
|
revision = "9520e82c474b0a04dd04f8a40959027271bab992"
|
|
|
|
|
2018-01-25 03:22:41 +01:00
|
|
|
[[projects]]
|
|
|
|
branch = "master"
|
|
|
|
name = "github.com/mitchellh/go-homedir"
|
|
|
|
packages = ["."]
|
|
|
|
revision = "b8bc1bf767474819792c23f32d8286a45736f1c6"
|
|
|
|
|
2017-10-31 01:35:36 +01:00
|
|
|
[[projects]]
|
|
|
|
branch = "master"
|
|
|
|
name = "github.com/mitchellh/go-ps"
|
|
|
|
packages = ["."]
|
|
|
|
revision = "4fdf99ab29366514c69ccccddab5dc58b8d84062"
|
|
|
|
|
2017-11-28 21:54:36 +01:00
|
|
|
[[projects]]
|
|
|
|
name = "github.com/moby/moby"
|
|
|
|
packages = ["api/types/time"]
|
|
|
|
revision = "092cba3727bb9b4a2f0e922cd6c0f93ea270e363"
|
|
|
|
version = "v1.13.1"
|
|
|
|
|
2017-11-09 02:08:51 +01:00
|
|
|
[[projects]]
|
|
|
|
name = "github.com/opentracing/opentracing-go"
|
Make some stack-related CLI improvements (#947)
This change includes a handful of stack-related CLI formatting
improvements that I've been noodling on in the background for a while,
based on things that tend to trip up demos and the inner loop workflow.
This includes:
* If `pulumi stack select` is run by itself, use an interactive
CLI menu to let the user select an existing stack, or choose to
create a new one. This looks as follows
$ pulumi stack select
Please choose a stack, or choose to create a new one:
abcdef
babblabblabble
> currentlyselected
defcon
<create a new stack>
and is navigated in the usual way (key up, down, enter).
* If a stack name is passed that does not exist, prompt the user
to ask whether s/he wants to create one on-demand. This hooks
interesting moments in time, like `pulumi stack select foo`,
and cuts down on the need to run additional commands.
* If a current stack is required, but none is currently selected,
then pop the same interactive menu shown above to select one.
Depending on the command being run, we may or may not show the
option to create a new stack (e.g., that doesn't make much sense
when you're running `pulumi destroy`, but might when you're
running `pulumi stack`). This again lets you do with a single
command what would have otherwise entailed an error with multiple
commands to recover from it.
* If you run `pulumi stack init` without any additional arguments,
we interactively prompt for the stack name. Before, we would
error and you'd then need to run `pulumi stack init <name>`.
* Colorize some things nicely; for example, now all prompts will
by default become bright white.
2018-02-17 00:03:54 +01:00
|
|
|
packages = [
|
|
|
|
".",
|
|
|
|
"ext",
|
|
|
|
"log"
|
|
|
|
]
|
2017-11-09 02:08:51 +01:00
|
|
|
revision = "1949ddbfd147afd4d964a9f00b24eb291e0e7c38"
|
|
|
|
version = "v1.0.2"
|
|
|
|
|
2018-01-25 03:22:41 +01:00
|
|
|
[[projects]]
|
|
|
|
name = "github.com/pelletier/go-buffruneio"
|
|
|
|
packages = ["."]
|
|
|
|
revision = "c37440a7cf42ac63b919c752ca73a85067e05992"
|
|
|
|
version = "v0.2.0"
|
|
|
|
|
2017-08-02 03:37:06 +02:00
|
|
|
[[projects]]
|
|
|
|
name = "github.com/pkg/errors"
|
|
|
|
packages = ["."]
|
|
|
|
revision = "645ef00459ed84a119197bfb8d8205042c6df63d"
|
|
|
|
version = "v0.8.0"
|
|
|
|
|
|
|
|
[[projects]]
|
|
|
|
name = "github.com/pmezard/go-difflib"
|
|
|
|
packages = ["difflib"]
|
|
|
|
revision = "792786c7400a136282c1664665ae0a8db921c6c2"
|
|
|
|
version = "v1.0.0"
|
|
|
|
|
|
|
|
[[projects]]
|
|
|
|
branch = "master"
|
|
|
|
name = "github.com/reconquest/loreley"
|
|
|
|
packages = ["."]
|
|
|
|
revision = "2ab6b7470a54bfa9b5b0289f9b4e8fc4839838f7"
|
|
|
|
|
2018-04-28 20:18:21 +02:00
|
|
|
[[projects]]
|
|
|
|
name = "github.com/russross/blackfriday"
|
|
|
|
packages = ["."]
|
|
|
|
revision = "55d61fa8aa702f59229e6cff85793c22e580eaf5"
|
|
|
|
version = "v1.5.1"
|
|
|
|
|
2017-11-21 02:22:51 +01:00
|
|
|
[[projects]]
|
|
|
|
branch = "master"
|
|
|
|
name = "github.com/sabhiram/go-gitignore"
|
|
|
|
packages = ["."]
|
|
|
|
revision = "362f9845770f1606d61ba3ddf9cfb1f0780d2ffe"
|
|
|
|
|
2017-10-25 19:20:08 +02:00
|
|
|
[[projects]]
|
|
|
|
branch = "master"
|
|
|
|
name = "github.com/sergi/go-diff"
|
|
|
|
packages = ["diffmatchpatch"]
|
2017-11-09 02:08:51 +01:00
|
|
|
revision = "2fc9cd33b5f86077aa3e0f442fa0476a9fa9a1dc"
|
2017-10-25 19:20:08 +02:00
|
|
|
|
2018-05-25 03:48:03 +02:00
|
|
|
[[projects]]
|
|
|
|
branch = "master"
|
|
|
|
name = "github.com/skratchdot/open-golang"
|
|
|
|
packages = ["open"]
|
|
|
|
revision = "75fb7ed4208cf72d323d7d02fd1a5964a7a9073c"
|
|
|
|
|
2017-08-02 03:37:06 +02:00
|
|
|
[[projects]]
|
|
|
|
branch = "master"
|
|
|
|
name = "github.com/spf13/cobra"
|
2018-04-28 20:18:21 +02:00
|
|
|
packages = [
|
|
|
|
".",
|
|
|
|
"doc"
|
|
|
|
]
|
2017-11-09 02:08:51 +01:00
|
|
|
revision = "f63432717259fda2ff0da668dccdfaa3de837ee6"
|
2017-08-02 03:37:06 +02:00
|
|
|
|
|
|
|
[[projects]]
|
|
|
|
name = "github.com/spf13/pflag"
|
|
|
|
packages = ["."]
|
|
|
|
revision = "e57e3eeb33f795204c1ca35f56c44f83227c6e66"
|
|
|
|
version = "v1.0.0"
|
|
|
|
|
2017-10-25 19:20:08 +02:00
|
|
|
[[projects]]
|
|
|
|
name = "github.com/src-d/gcfg"
|
Make some stack-related CLI improvements (#947)
This change includes a handful of stack-related CLI formatting
improvements that I've been noodling on in the background for a while,
based on things that tend to trip up demos and the inner loop workflow.
This includes:
* If `pulumi stack select` is run by itself, use an interactive
CLI menu to let the user select an existing stack, or choose to
create a new one. This looks as follows
$ pulumi stack select
Please choose a stack, or choose to create a new one:
abcdef
babblabblabble
> currentlyselected
defcon
<create a new stack>
and is navigated in the usual way (key up, down, enter).
* If a stack name is passed that does not exist, prompt the user
to ask whether s/he wants to create one on-demand. This hooks
interesting moments in time, like `pulumi stack select foo`,
and cuts down on the need to run additional commands.
* If a current stack is required, but none is currently selected,
then pop the same interactive menu shown above to select one.
Depending on the command being run, we may or may not show the
option to create a new stack (e.g., that doesn't make much sense
when you're running `pulumi destroy`, but might when you're
running `pulumi stack`). This again lets you do with a single
command what would have otherwise entailed an error with multiple
commands to recover from it.
* If you run `pulumi stack init` without any additional arguments,
we interactively prompt for the stack name. Before, we would
error and you'd then need to run `pulumi stack init <name>`.
* Colorize some things nicely; for example, now all prompts will
by default become bright white.
2018-02-17 00:03:54 +01:00
|
|
|
packages = [
|
|
|
|
".",
|
|
|
|
"scanner",
|
|
|
|
"token",
|
|
|
|
"types"
|
|
|
|
]
|
2017-10-25 19:20:08 +02:00
|
|
|
revision = "f187355171c936ac84a82793659ebb4936bc1c23"
|
|
|
|
version = "v1.3.0"
|
|
|
|
|
2017-08-02 03:37:06 +02:00
|
|
|
[[projects]]
|
|
|
|
name = "github.com/stretchr/testify"
|
|
|
|
packages = ["assert"]
|
|
|
|
revision = "69483b4bd14f5845b5a1e55bca19e954e827f1d0"
|
|
|
|
version = "v1.1.4"
|
|
|
|
|
2017-11-09 02:08:51 +01:00
|
|
|
[[projects]]
|
|
|
|
name = "github.com/uber/jaeger-client-go"
|
Make some stack-related CLI improvements (#947)
This change includes a handful of stack-related CLI formatting
improvements that I've been noodling on in the background for a while,
based on things that tend to trip up demos and the inner loop workflow.
This includes:
* If `pulumi stack select` is run by itself, use an interactive
CLI menu to let the user select an existing stack, or choose to
create a new one. This looks as follows
$ pulumi stack select
Please choose a stack, or choose to create a new one:
abcdef
babblabblabble
> currentlyselected
defcon
<create a new stack>
and is navigated in the usual way (key up, down, enter).
* If a stack name is passed that does not exist, prompt the user
to ask whether s/he wants to create one on-demand. This hooks
interesting moments in time, like `pulumi stack select foo`,
and cuts down on the need to run additional commands.
* If a current stack is required, but none is currently selected,
then pop the same interactive menu shown above to select one.
Depending on the command being run, we may or may not show the
option to create a new stack (e.g., that doesn't make much sense
when you're running `pulumi destroy`, but might when you're
running `pulumi stack`). This again lets you do with a single
command what would have otherwise entailed an error with multiple
commands to recover from it.
* If you run `pulumi stack init` without any additional arguments,
we interactively prompt for the stack name. Before, we would
error and you'd then need to run `pulumi stack init <name>`.
* Colorize some things nicely; for example, now all prompts will
by default become bright white.
2018-02-17 00:03:54 +01:00
|
|
|
packages = [
|
|
|
|
".",
|
|
|
|
"internal/spanlog",
|
|
|
|
"log",
|
|
|
|
"thrift-gen/agent",
|
|
|
|
"thrift-gen/jaeger",
|
|
|
|
"thrift-gen/sampling",
|
|
|
|
"thrift-gen/zipkincore",
|
|
|
|
"transport/zipkin",
|
|
|
|
"utils"
|
|
|
|
]
|
2017-11-09 02:08:51 +01:00
|
|
|
revision = "3e3870040def0ebdaf65a003863fa64f5cb26139"
|
|
|
|
version = "v2.9.0"
|
|
|
|
|
|
|
|
[[projects]]
|
|
|
|
name = "github.com/uber/jaeger-lib"
|
|
|
|
packages = ["metrics"]
|
|
|
|
revision = "3b2a9ad2a045881ab7a0f81d465be54c8292ee4f"
|
|
|
|
version = "v1.1.0"
|
|
|
|
|
2018-01-25 03:22:41 +01:00
|
|
|
[[projects]]
|
|
|
|
branch = "master"
|
|
|
|
name = "github.com/xanzy/ssh-agent"
|
|
|
|
packages = ["."]
|
|
|
|
revision = "ba9c9e33906f58169366275e3450db66139a31a9"
|
|
|
|
|
2017-08-02 03:37:06 +02:00
|
|
|
[[projects]]
|
|
|
|
branch = "master"
|
|
|
|
name = "golang.org/x/crypto"
|
Make some stack-related CLI improvements (#947)
This change includes a handful of stack-related CLI formatting
improvements that I've been noodling on in the background for a while,
based on things that tend to trip up demos and the inner loop workflow.
This includes:
* If `pulumi stack select` is run by itself, use an interactive
CLI menu to let the user select an existing stack, or choose to
create a new one. This looks as follows
$ pulumi stack select
Please choose a stack, or choose to create a new one:
abcdef
babblabblabble
> currentlyselected
defcon
<create a new stack>
and is navigated in the usual way (key up, down, enter).
* If a stack name is passed that does not exist, prompt the user
to ask whether s/he wants to create one on-demand. This hooks
interesting moments in time, like `pulumi stack select foo`,
and cuts down on the need to run additional commands.
* If a current stack is required, but none is currently selected,
then pop the same interactive menu shown above to select one.
Depending on the command being run, we may or may not show the
option to create a new stack (e.g., that doesn't make much sense
when you're running `pulumi destroy`, but might when you're
running `pulumi stack`). This again lets you do with a single
command what would have otherwise entailed an error with multiple
commands to recover from it.
* If you run `pulumi stack init` without any additional arguments,
we interactively prompt for the stack name. Before, we would
error and you'd then need to run `pulumi stack init <name>`.
* Colorize some things nicely; for example, now all prompts will
by default become bright white.
2018-02-17 00:03:54 +01:00
|
|
|
packages = [
|
|
|
|
"cast5",
|
|
|
|
"curve25519",
|
|
|
|
"ed25519",
|
|
|
|
"ed25519/internal/edwards25519",
|
|
|
|
"openpgp",
|
|
|
|
"openpgp/armor",
|
|
|
|
"openpgp/elgamal",
|
|
|
|
"openpgp/errors",
|
|
|
|
"openpgp/packet",
|
|
|
|
"openpgp/s2k",
|
|
|
|
"pbkdf2",
|
|
|
|
"ssh",
|
|
|
|
"ssh/agent",
|
|
|
|
"ssh/knownhosts",
|
|
|
|
"ssh/terminal"
|
|
|
|
]
|
2017-11-09 02:08:51 +01:00
|
|
|
revision = "6a293f2d4b14b8e6d3f0539e383f6d0d30fce3fd"
|
2017-08-02 03:37:06 +02:00
|
|
|
|
|
|
|
[[projects]]
|
|
|
|
branch = "master"
|
|
|
|
name = "golang.org/x/net"
|
Make some stack-related CLI improvements (#947)
This change includes a handful of stack-related CLI formatting
improvements that I've been noodling on in the background for a while,
based on things that tend to trip up demos and the inner loop workflow.
This includes:
* If `pulumi stack select` is run by itself, use an interactive
CLI menu to let the user select an existing stack, or choose to
create a new one. This looks as follows
$ pulumi stack select
Please choose a stack, or choose to create a new one:
abcdef
babblabblabble
> currentlyselected
defcon
<create a new stack>
and is navigated in the usual way (key up, down, enter).
* If a stack name is passed that does not exist, prompt the user
to ask whether s/he wants to create one on-demand. This hooks
interesting moments in time, like `pulumi stack select foo`,
and cuts down on the need to run additional commands.
* If a current stack is required, but none is currently selected,
then pop the same interactive menu shown above to select one.
Depending on the command being run, we may or may not show the
option to create a new stack (e.g., that doesn't make much sense
when you're running `pulumi destroy`, but might when you're
running `pulumi stack`). This again lets you do with a single
command what would have otherwise entailed an error with multiple
commands to recover from it.
* If you run `pulumi stack init` without any additional arguments,
we interactively prompt for the stack name. Before, we would
error and you'd then need to run `pulumi stack init <name>`.
* Colorize some things nicely; for example, now all prompts will
by default become bright white.
2018-02-17 00:03:54 +01:00
|
|
|
packages = [
|
|
|
|
"context",
|
|
|
|
"http2",
|
|
|
|
"http2/hpack",
|
|
|
|
"idna",
|
|
|
|
"internal/timeseries",
|
|
|
|
"lex/httplex",
|
|
|
|
"trace"
|
|
|
|
]
|
2017-11-09 02:08:51 +01:00
|
|
|
revision = "a337091b0525af65de94df2eb7e98bd9962dcbe2"
|
2017-08-02 03:37:06 +02:00
|
|
|
|
|
|
|
[[projects]]
|
|
|
|
branch = "master"
|
|
|
|
name = "golang.org/x/sys"
|
Make some stack-related CLI improvements (#947)
This change includes a handful of stack-related CLI formatting
improvements that I've been noodling on in the background for a while,
based on things that tend to trip up demos and the inner loop workflow.
This includes:
* If `pulumi stack select` is run by itself, use an interactive
CLI menu to let the user select an existing stack, or choose to
create a new one. This looks as follows
$ pulumi stack select
Please choose a stack, or choose to create a new one:
abcdef
babblabblabble
> currentlyselected
defcon
<create a new stack>
and is navigated in the usual way (key up, down, enter).
* If a stack name is passed that does not exist, prompt the user
to ask whether s/he wants to create one on-demand. This hooks
interesting moments in time, like `pulumi stack select foo`,
and cuts down on the need to run additional commands.
* If a current stack is required, but none is currently selected,
then pop the same interactive menu shown above to select one.
Depending on the command being run, we may or may not show the
option to create a new stack (e.g., that doesn't make much sense
when you're running `pulumi destroy`, but might when you're
running `pulumi stack`). This again lets you do with a single
command what would have otherwise entailed an error with multiple
commands to recover from it.
* If you run `pulumi stack init` without any additional arguments,
we interactively prompt for the stack name. Before, we would
error and you'd then need to run `pulumi stack init <name>`.
* Colorize some things nicely; for example, now all prompts will
by default become bright white.
2018-02-17 00:03:54 +01:00
|
|
|
packages = [
|
|
|
|
"unix",
|
|
|
|
"windows"
|
|
|
|
]
|
2017-11-09 02:08:51 +01:00
|
|
|
revision = "4b45465282a4624cf39876842a017334f13b8aff"
|
2017-08-02 03:37:06 +02:00
|
|
|
|
|
|
|
[[projects]]
|
|
|
|
branch = "master"
|
|
|
|
name = "golang.org/x/text"
|
Make some stack-related CLI improvements (#947)
This change includes a handful of stack-related CLI formatting
improvements that I've been noodling on in the background for a while,
based on things that tend to trip up demos and the inner loop workflow.
This includes:
* If `pulumi stack select` is run by itself, use an interactive
CLI menu to let the user select an existing stack, or choose to
create a new one. This looks as follows
$ pulumi stack select
Please choose a stack, or choose to create a new one:
abcdef
babblabblabble
> currentlyselected
defcon
<create a new stack>
and is navigated in the usual way (key up, down, enter).
* If a stack name is passed that does not exist, prompt the user
to ask whether s/he wants to create one on-demand. This hooks
interesting moments in time, like `pulumi stack select foo`,
and cuts down on the need to run additional commands.
* If a current stack is required, but none is currently selected,
then pop the same interactive menu shown above to select one.
Depending on the command being run, we may or may not show the
option to create a new stack (e.g., that doesn't make much sense
when you're running `pulumi destroy`, but might when you're
running `pulumi stack`). This again lets you do with a single
command what would have otherwise entailed an error with multiple
commands to recover from it.
* If you run `pulumi stack init` without any additional arguments,
we interactively prompt for the stack name. Before, we would
error and you'd then need to run `pulumi stack init <name>`.
* Colorize some things nicely; for example, now all prompts will
by default become bright white.
2018-02-17 00:03:54 +01:00
|
|
|
packages = [
|
|
|
|
"collate",
|
|
|
|
"collate/build",
|
|
|
|
"internal/colltab",
|
|
|
|
"internal/gen",
|
|
|
|
"internal/tag",
|
|
|
|
"internal/triegen",
|
|
|
|
"internal/ucd",
|
|
|
|
"language",
|
|
|
|
"secure/bidirule",
|
|
|
|
"transform",
|
|
|
|
"unicode/bidi",
|
|
|
|
"unicode/cldr",
|
|
|
|
"unicode/norm",
|
|
|
|
"unicode/rangetable"
|
|
|
|
]
|
2017-11-09 02:08:51 +01:00
|
|
|
revision = "88f656faf3f37f690df1a32515b479415e1a6769"
|
2017-08-02 03:37:06 +02:00
|
|
|
|
|
|
|
[[projects]]
|
|
|
|
branch = "master"
|
|
|
|
name = "google.golang.org/genproto"
|
|
|
|
packages = ["googleapis/rpc/status"]
|
2017-11-09 02:08:51 +01:00
|
|
|
revision = "11c7f9e547da6db876260ce49ea7536985904c9b"
|
2017-08-02 03:37:06 +02:00
|
|
|
|
|
|
|
[[projects]]
|
|
|
|
name = "google.golang.org/grpc"
|
Make some stack-related CLI improvements (#947)
This change includes a handful of stack-related CLI formatting
improvements that I've been noodling on in the background for a while,
based on things that tend to trip up demos and the inner loop workflow.
This includes:
* If `pulumi stack select` is run by itself, use an interactive
CLI menu to let the user select an existing stack, or choose to
create a new one. This looks as follows
$ pulumi stack select
Please choose a stack, or choose to create a new one:
abcdef
babblabblabble
> currentlyselected
defcon
<create a new stack>
and is navigated in the usual way (key up, down, enter).
* If a stack name is passed that does not exist, prompt the user
to ask whether s/he wants to create one on-demand. This hooks
interesting moments in time, like `pulumi stack select foo`,
and cuts down on the need to run additional commands.
* If a current stack is required, but none is currently selected,
then pop the same interactive menu shown above to select one.
Depending on the command being run, we may or may not show the
option to create a new stack (e.g., that doesn't make much sense
when you're running `pulumi destroy`, but might when you're
running `pulumi stack`). This again lets you do with a single
command what would have otherwise entailed an error with multiple
commands to recover from it.
* If you run `pulumi stack init` without any additional arguments,
we interactively prompt for the stack name. Before, we would
error and you'd then need to run `pulumi stack init <name>`.
* Colorize some things nicely; for example, now all prompts will
by default become bright white.
2018-02-17 00:03:54 +01:00
|
|
|
packages = [
|
|
|
|
".",
|
|
|
|
"balancer",
|
2018-05-17 00:37:34 +02:00
|
|
|
"balancer/base",
|
|
|
|
"balancer/roundrobin",
|
Make some stack-related CLI improvements (#947)
This change includes a handful of stack-related CLI formatting
improvements that I've been noodling on in the background for a while,
based on things that tend to trip up demos and the inner loop workflow.
This includes:
* If `pulumi stack select` is run by itself, use an interactive
CLI menu to let the user select an existing stack, or choose to
create a new one. This looks as follows
$ pulumi stack select
Please choose a stack, or choose to create a new one:
abcdef
babblabblabble
> currentlyselected
defcon
<create a new stack>
and is navigated in the usual way (key up, down, enter).
* If a stack name is passed that does not exist, prompt the user
to ask whether s/he wants to create one on-demand. This hooks
interesting moments in time, like `pulumi stack select foo`,
and cuts down on the need to run additional commands.
* If a current stack is required, but none is currently selected,
then pop the same interactive menu shown above to select one.
Depending on the command being run, we may or may not show the
option to create a new stack (e.g., that doesn't make much sense
when you're running `pulumi destroy`, but might when you're
running `pulumi stack`). This again lets you do with a single
command what would have otherwise entailed an error with multiple
commands to recover from it.
* If you run `pulumi stack init` without any additional arguments,
we interactively prompt for the stack name. Before, we would
error and you'd then need to run `pulumi stack init <name>`.
* Colorize some things nicely; for example, now all prompts will
by default become bright white.
2018-02-17 00:03:54 +01:00
|
|
|
"codes",
|
|
|
|
"connectivity",
|
|
|
|
"credentials",
|
2018-05-17 00:37:34 +02:00
|
|
|
"encoding",
|
|
|
|
"encoding/proto",
|
Make some stack-related CLI improvements (#947)
This change includes a handful of stack-related CLI formatting
improvements that I've been noodling on in the background for a while,
based on things that tend to trip up demos and the inner loop workflow.
This includes:
* If `pulumi stack select` is run by itself, use an interactive
CLI menu to let the user select an existing stack, or choose to
create a new one. This looks as follows
$ pulumi stack select
Please choose a stack, or choose to create a new one:
abcdef
babblabblabble
> currentlyselected
defcon
<create a new stack>
and is navigated in the usual way (key up, down, enter).
* If a stack name is passed that does not exist, prompt the user
to ask whether s/he wants to create one on-demand. This hooks
interesting moments in time, like `pulumi stack select foo`,
and cuts down on the need to run additional commands.
* If a current stack is required, but none is currently selected,
then pop the same interactive menu shown above to select one.
Depending on the command being run, we may or may not show the
option to create a new stack (e.g., that doesn't make much sense
when you're running `pulumi destroy`, but might when you're
running `pulumi stack`). This again lets you do with a single
command what would have otherwise entailed an error with multiple
commands to recover from it.
* If you run `pulumi stack init` without any additional arguments,
we interactively prompt for the stack name. Before, we would
error and you'd then need to run `pulumi stack init <name>`.
* Colorize some things nicely; for example, now all prompts will
by default become bright white.
2018-02-17 00:03:54 +01:00
|
|
|
"grpclb/grpc_lb_v1/messages",
|
|
|
|
"grpclog",
|
|
|
|
"internal",
|
|
|
|
"keepalive",
|
|
|
|
"metadata",
|
|
|
|
"naming",
|
|
|
|
"peer",
|
|
|
|
"reflection",
|
|
|
|
"reflection/grpc_reflection_v1alpha",
|
|
|
|
"resolver",
|
2018-05-17 00:37:34 +02:00
|
|
|
"resolver/dns",
|
|
|
|
"resolver/passthrough",
|
Make some stack-related CLI improvements (#947)
This change includes a handful of stack-related CLI formatting
improvements that I've been noodling on in the background for a while,
based on things that tend to trip up demos and the inner loop workflow.
This includes:
* If `pulumi stack select` is run by itself, use an interactive
CLI menu to let the user select an existing stack, or choose to
create a new one. This looks as follows
$ pulumi stack select
Please choose a stack, or choose to create a new one:
abcdef
babblabblabble
> currentlyselected
defcon
<create a new stack>
and is navigated in the usual way (key up, down, enter).
* If a stack name is passed that does not exist, prompt the user
to ask whether s/he wants to create one on-demand. This hooks
interesting moments in time, like `pulumi stack select foo`,
and cuts down on the need to run additional commands.
* If a current stack is required, but none is currently selected,
then pop the same interactive menu shown above to select one.
Depending on the command being run, we may or may not show the
option to create a new stack (e.g., that doesn't make much sense
when you're running `pulumi destroy`, but might when you're
running `pulumi stack`). This again lets you do with a single
command what would have otherwise entailed an error with multiple
commands to recover from it.
* If you run `pulumi stack init` without any additional arguments,
we interactively prompt for the stack name. Before, we would
error and you'd then need to run `pulumi stack init <name>`.
* Colorize some things nicely; for example, now all prompts will
by default become bright white.
2018-02-17 00:03:54 +01:00
|
|
|
"stats",
|
|
|
|
"status",
|
|
|
|
"tap",
|
|
|
|
"transport"
|
|
|
|
]
|
2018-05-17 00:37:34 +02:00
|
|
|
revision = "d11072e7ca9811b1100b80ca0269ac831f06d024"
|
|
|
|
version = "v1.11.3"
|
2017-08-02 03:37:06 +02:00
|
|
|
|
Make some stack-related CLI improvements (#947)
This change includes a handful of stack-related CLI formatting
improvements that I've been noodling on in the background for a while,
based on things that tend to trip up demos and the inner loop workflow.
This includes:
* If `pulumi stack select` is run by itself, use an interactive
CLI menu to let the user select an existing stack, or choose to
create a new one. This looks as follows
$ pulumi stack select
Please choose a stack, or choose to create a new one:
abcdef
babblabblabble
> currentlyselected
defcon
<create a new stack>
and is navigated in the usual way (key up, down, enter).
* If a stack name is passed that does not exist, prompt the user
to ask whether s/he wants to create one on-demand. This hooks
interesting moments in time, like `pulumi stack select foo`,
and cuts down on the need to run additional commands.
* If a current stack is required, but none is currently selected,
then pop the same interactive menu shown above to select one.
Depending on the command being run, we may or may not show the
option to create a new stack (e.g., that doesn't make much sense
when you're running `pulumi destroy`, but might when you're
running `pulumi stack`). This again lets you do with a single
command what would have otherwise entailed an error with multiple
commands to recover from it.
* If you run `pulumi stack init` without any additional arguments,
we interactively prompt for the stack name. Before, we would
error and you'd then need to run `pulumi stack init <name>`.
* Colorize some things nicely; for example, now all prompts will
by default become bright white.
2018-02-17 00:03:54 +01:00
|
|
|
[[projects]]
|
|
|
|
name = "gopkg.in/AlecAivazis/survey.v1"
|
|
|
|
packages = [
|
|
|
|
".",
|
|
|
|
"core",
|
|
|
|
"terminal"
|
|
|
|
]
|
|
|
|
revision = "0aa8b6a162b391fe2d95648b7677d1d6ac2090a6"
|
|
|
|
version = "v1.4.1"
|
|
|
|
|
2018-01-25 03:22:41 +01:00
|
|
|
[[projects]]
|
|
|
|
name = "gopkg.in/src-d/go-billy.v4"
|
Make some stack-related CLI improvements (#947)
This change includes a handful of stack-related CLI formatting
improvements that I've been noodling on in the background for a while,
based on things that tend to trip up demos and the inner loop workflow.
This includes:
* If `pulumi stack select` is run by itself, use an interactive
CLI menu to let the user select an existing stack, or choose to
create a new one. This looks as follows
$ pulumi stack select
Please choose a stack, or choose to create a new one:
abcdef
babblabblabble
> currentlyselected
defcon
<create a new stack>
and is navigated in the usual way (key up, down, enter).
* If a stack name is passed that does not exist, prompt the user
to ask whether s/he wants to create one on-demand. This hooks
interesting moments in time, like `pulumi stack select foo`,
and cuts down on the need to run additional commands.
* If a current stack is required, but none is currently selected,
then pop the same interactive menu shown above to select one.
Depending on the command being run, we may or may not show the
option to create a new stack (e.g., that doesn't make much sense
when you're running `pulumi destroy`, but might when you're
running `pulumi stack`). This again lets you do with a single
command what would have otherwise entailed an error with multiple
commands to recover from it.
* If you run `pulumi stack init` without any additional arguments,
we interactively prompt for the stack name. Before, we would
error and you'd then need to run `pulumi stack init <name>`.
* Colorize some things nicely; for example, now all prompts will
by default become bright white.
2018-02-17 00:03:54 +01:00
|
|
|
packages = [
|
|
|
|
".",
|
|
|
|
"helper/chroot",
|
|
|
|
"helper/polyfill",
|
|
|
|
"osfs",
|
|
|
|
"util"
|
|
|
|
]
|
2018-01-25 03:22:41 +01:00
|
|
|
revision = "e940f8b62a8e61adc71f69802c1cc8305b64ec96"
|
|
|
|
version = "v4.0.2"
|
|
|
|
|
2017-10-25 19:20:08 +02:00
|
|
|
[[projects]]
|
|
|
|
name = "gopkg.in/src-d/go-git.v4"
|
Make some stack-related CLI improvements (#947)
This change includes a handful of stack-related CLI formatting
improvements that I've been noodling on in the background for a while,
based on things that tend to trip up demos and the inner loop workflow.
This includes:
* If `pulumi stack select` is run by itself, use an interactive
CLI menu to let the user select an existing stack, or choose to
create a new one. This looks as follows
$ pulumi stack select
Please choose a stack, or choose to create a new one:
abcdef
babblabblabble
> currentlyselected
defcon
<create a new stack>
and is navigated in the usual way (key up, down, enter).
* If a stack name is passed that does not exist, prompt the user
to ask whether s/he wants to create one on-demand. This hooks
interesting moments in time, like `pulumi stack select foo`,
and cuts down on the need to run additional commands.
* If a current stack is required, but none is currently selected,
then pop the same interactive menu shown above to select one.
Depending on the command being run, we may or may not show the
option to create a new stack (e.g., that doesn't make much sense
when you're running `pulumi destroy`, but might when you're
running `pulumi stack`). This again lets you do with a single
command what would have otherwise entailed an error with multiple
commands to recover from it.
* If you run `pulumi stack init` without any additional arguments,
we interactively prompt for the stack name. Before, we would
error and you'd then need to run `pulumi stack init <name>`.
* Colorize some things nicely; for example, now all prompts will
by default become bright white.
2018-02-17 00:03:54 +01:00
|
|
|
packages = [
|
|
|
|
".",
|
|
|
|
"config",
|
|
|
|
"internal/revision",
|
|
|
|
"plumbing",
|
|
|
|
"plumbing/cache",
|
|
|
|
"plumbing/filemode",
|
|
|
|
"plumbing/format/config",
|
|
|
|
"plumbing/format/diff",
|
|
|
|
"plumbing/format/gitignore",
|
|
|
|
"plumbing/format/idxfile",
|
|
|
|
"plumbing/format/index",
|
|
|
|
"plumbing/format/objfile",
|
|
|
|
"plumbing/format/packfile",
|
|
|
|
"plumbing/format/pktline",
|
|
|
|
"plumbing/object",
|
|
|
|
"plumbing/protocol/packp",
|
|
|
|
"plumbing/protocol/packp/capability",
|
|
|
|
"plumbing/protocol/packp/sideband",
|
|
|
|
"plumbing/revlist",
|
|
|
|
"plumbing/storer",
|
|
|
|
"plumbing/transport",
|
|
|
|
"plumbing/transport/client",
|
|
|
|
"plumbing/transport/file",
|
|
|
|
"plumbing/transport/git",
|
|
|
|
"plumbing/transport/http",
|
|
|
|
"plumbing/transport/internal/common",
|
|
|
|
"plumbing/transport/server",
|
|
|
|
"plumbing/transport/ssh",
|
|
|
|
"storage",
|
|
|
|
"storage/filesystem",
|
|
|
|
"storage/filesystem/internal/dotgit",
|
|
|
|
"storage/memory",
|
|
|
|
"utils/binary",
|
|
|
|
"utils/diff",
|
|
|
|
"utils/ioutil",
|
|
|
|
"utils/merkletrie",
|
|
|
|
"utils/merkletrie/filesystem",
|
|
|
|
"utils/merkletrie/index",
|
|
|
|
"utils/merkletrie/internal/frame",
|
|
|
|
"utils/merkletrie/noder"
|
|
|
|
]
|
2018-01-25 03:22:41 +01:00
|
|
|
revision = "e9247ce9c5ce12126f646ca3ddf0066e4829bd14"
|
|
|
|
version = "v4.1.0"
|
2017-10-25 19:20:08 +02:00
|
|
|
|
|
|
|
[[projects]]
|
|
|
|
name = "gopkg.in/warnings.v0"
|
|
|
|
packages = ["."]
|
|
|
|
revision = "8a331561fe74dadba6edfc59f3be66c22c3b065d"
|
|
|
|
version = "v0.1.1"
|
|
|
|
|
2017-08-02 03:37:06 +02:00
|
|
|
[[projects]]
|
|
|
|
branch = "v2"
|
|
|
|
name = "gopkg.in/yaml.v2"
|
|
|
|
packages = ["."]
|
2017-09-07 18:02:15 +02:00
|
|
|
revision = "eb3733d160e74a9c7e442f435eb3bea458e1d19f"
|
2017-08-02 03:37:06 +02:00
|
|
|
|
|
|
|
[solve-meta]
|
|
|
|
analyzer-name = "dep"
|
|
|
|
analyzer-version = 1
|
2018-05-25 03:48:03 +02:00
|
|
|
inputs-digest = "a3c19b57bc10408ea6f35080bdca4a22257e7ab588c1fe3dfc88cf2b00aeea52"
|
2017-08-02 03:37:06 +02:00
|
|
|
solver-name = "gps-cdcl"
|
|
|
|
solver-version = 1
|