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 = [
|
2018-06-22 04:39:18 +02:00
|
|
|
"api/types/time",
|
2018-04-10 21:03:11 +02:00
|
|
|
"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]]
|
|
|
|
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"
|
|
|
|
]
|
2018-06-23 04:03:30 +02:00
|
|
|
revision = "b4deda0973fb4c70b50d226b1af49f3da59f5265"
|
|
|
|
version = "v1.1.0"
|
2017-11-09 02:08:51 +01:00
|
|
|
|
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"
|
|
|
|
|
Detect secret-like config (#1689)
Previously, we would unconditionally warn anytime you added a non-secret
config:
$ pulumi config set aws:region us-west-2
warning: saved config key '%s' value '%s' as plaintext;
re-run with --secret to encrypt the value instead.
Use --plaintext to avoid this warning
This was particularly annoying, since it is very common to store
non-secret config. For instance, the AWS region. And it was easy to tune
out because it wasn't actually warning about anything interesting.
This change, which resolves pulumi/pulumi#570, uses an approach similar
to Go's gas linter, to detect high entropy values, and issue an error.
This ensures that we only make noise on things we suspect are actually
secrets being stored in plaintext, and forces the user to pass
--plaintext. For instance, the common case issues no errors:
$ pulumi config set aws:region us-west-2
And in the event that you store something that is secret-like:
$ pulumi config set aws:region nq8r4B4xslzrtj0a3
error: config value 'nq8r4B4xslzrtj0a3' looks like a secret;
rerun with --secret to encrypt it, or --plaintext if you meant
to store in plaintext
To suppress this, simply pass --secret (to encrypt) or --plaintext (to
override the warning).
2018-08-02 13:14:16 +02:00
|
|
|
[[projects]]
|
|
|
|
name = "github.com/nbutton23/zxcvbn-go"
|
|
|
|
packages = [
|
|
|
|
".",
|
|
|
|
"adjacency",
|
|
|
|
"data",
|
|
|
|
"entropy",
|
|
|
|
"frequency",
|
|
|
|
"match",
|
|
|
|
"matching",
|
|
|
|
"scoring",
|
|
|
|
"utils/math"
|
|
|
|
]
|
|
|
|
revision = "eafdab6b0663b4b528c35975c8b0e78be6e25261"
|
|
|
|
version = "v0.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"
|
|
|
|
|
Implement first-class providers. (#1695)
### First-Class Providers
These changes implement support for first-class providers. First-class
providers are provider plugins that are exposed as resources via the
Pulumi programming model so that they may be explicitly and multiply
instantiated. Each instance of a provider resource may be configured
differently, and configuration parameters may be source from the
outputs of other resources.
### Provider Plugin Changes
In order to accommodate the need to verify and diff provider
configuration and configure providers without complete configuration
information, these changes adjust the high-level provider plugin
interface. Two new methods for validating a provider's configuration
and diffing changes to the same have been added (`CheckConfig` and
`DiffConfig`, respectively), and the type of the configuration bag
accepted by `Configure` has been changed to a `PropertyMap`.
These changes have not yet been reflected in the provider plugin gRPC
interface. We will do this in a set of follow-up changes. Until then,
these methods are implemented by adapters:
- `CheckConfig` validates that all configuration parameters are string
or unknown properties. This is necessary because existing plugins
only accept string-typed configuration values.
- `DiffConfig` either returns "never replace" if all configuration
values are known or "must replace" if any configuration value is
unknown. The justification for this behavior is given
[here](https://github.com/pulumi/pulumi/pull/1695/files#diff-a6cd5c7f337665f5bb22e92ca5f07537R106)
- `Configure` converts the config bag to a legacy config map and
configures the provider plugin if all config values are known. If any
config value is unknown, the underlying plugin is not configured and
the provider may only perform `Check`, `Read`, and `Invoke`, all of
which return empty results. We justify this behavior becuase it is
only possible during a preview and provides the best experience we
can manage with the existing gRPC interface.
### Resource Model Changes
Providers are now exposed as resources that participate in a stack's
dependency graph. Like other resources, they are explicitly created,
may have multiple instances, and may have dependencies on other
resources. Providers are referred to using provider references, which
are a combination of the provider's URN and its ID. This design
addresses the need during a preview to refer to providers that have not
yet been physically created and therefore have no ID.
All custom resources that are not themselves providers must specify a
single provider via a provider reference. The named provider will be
used to manage that resource's CRUD operations. If a resource's
provider reference changes, the resource must be replaced. Though its
URN is not present in the resource's dependency list, the provider
should be treated as a dependency of the resource when topologically
sorting the dependency graph.
Finally, `Invoke` operations must now specify a provider to use for the
invocation via a provider reference.
### Engine Changes
First-class providers support requires a few changes to the engine:
- The engine must have some way to map from provider references to
provider plugins. It must be possible to add providers from a stack's
checkpoint to this map and to register new/updated providers during
the execution of a plan in response to CRUD operations on provider
resources.
- In order to support updating existing stacks using existing Pulumi
programs that may not explicitly instantiate providers, the engine
must be able to manage the "default" providers for each package
referenced by a checkpoint or Pulumi program. The configuration for
a "default" provider is taken from the stack's configuration data.
The former need is addressed by adding a provider registry type that is
responsible for managing all of the plugins required by a plan. In
addition to loading plugins froma checkpoint and providing the ability
to map from a provider reference to a provider plugin, this type serves
as the provider plugin for providers themselves (i.e. it is the
"provider provider").
The latter need is solved via two relatively self-contained changes to
plan setup and the eval source.
During plan setup, the old checkpoint is scanned for custom resources
that do not have a provider reference in order to compute the set of
packages that require a default provider. Once this set has been
computed, the required default provider definitions are conjured and
prepended to the checkpoint's resource list. Each resource that
requires a default provider is then updated to refer to the default
provider for its package.
While an eval source is running, each custom resource registration,
resource read, and invoke that does not name a provider is trapped
before being returned by the source iterator. If no default provider
for the appropriate package has been registered, the eval source
synthesizes an appropriate registration, waits for it to complete, and
records the registered provider's reference. This reference is injected
into the original request, which is then processed as usual. If a
default provider was already registered, the recorded reference is
used and no new registration occurs.
### SDK Changes
These changes only expose first-class providers from the Node.JS SDK.
- A new abstract class, `ProviderResource`, can be subclassed and used
to instantiate first-class providers.
- A new field in `ResourceOptions`, `provider`, can be used to supply
a particular provider instance to manage a `CustomResource`'s CRUD
operations.
- A new type, `InvokeOptions`, can be used to specify options that
control the behavior of a call to `pulumi.runtime.invoke`. This type
includes a `provider` field that is analogous to
`ResourceOptions.provider`.
2018-08-07 02:50:29 +02:00
|
|
|
[[projects]]
|
|
|
|
name = "github.com/satori/go.uuid"
|
|
|
|
packages = ["."]
|
|
|
|
revision = "f58768cc1a7a7e77a3bd49e98cdd21419399b6a3"
|
|
|
|
version = "v1.2.0"
|
|
|
|
|
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"
|
|
|
|
|
2018-06-08 21:57:59 +02:00
|
|
|
[[projects]]
|
|
|
|
name = "github.com/spf13/cast"
|
|
|
|
packages = ["."]
|
|
|
|
revision = "8965335b8c7107321228e3e3702cab9832751bac"
|
|
|
|
version = "v1.2.0"
|
|
|
|
|
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
|
Initial support for passing URLs to `new` and `up` (#1727)
* Initial support for passing URLs to `new` and `up`
This PR adds initial support for `pulumi new` using Git under the covers
to manage Pulumi templates, providing the same experience as before.
You can now also optionally pass a URL to a Git repository, e.g.
`pulumi new [<url>]`, including subdirectories within the repository,
and arbitrary branches, tags, or commits.
The following commands result in the same behavior from the user's
perspective:
- `pulumi new javascript`
- `pulumi new https://github.com/pulumi/templates/templates/javascript`
- `pulumi new https://github.com/pulumi/templates/tree/master/templates/javascript`
- `pulumi new https://github.com/pulumi/templates/tree/HEAD/templates/javascript`
To specify an arbitrary branch, tag, or commit:
- `pulumi new https://github.com/pulumi/templates/tree/<branch>/templates/javascript`
- `pulumi new https://github.com/pulumi/templates/tree/<tag>/templates/javascript`
- `pulumi new https://github.com/pulumi/templates/tree/<commit>/templates/javascript`
Branches and tags can include '/' separators, and `pulumi` will still
find the right subdirectory.
URLs to Gists are also supported, e.g.:
`pulumi new https://gist.github.com/justinvp/6673959ceb9d2ac5a14c6d536cb871a6`
If the specified subdirectory in the repository does not contain a
`Pulumi.yaml`, it will look for subdirectories within containing
`Pulumi.yaml` files, and prompt the user to choose a template, along the
lines of how `pulumi new` behaves when no template is specified.
The following commands result in the CLI prompting to choose a template:
- `pulumi new`
- `pulumi new https://github.com/pulumi/templates/templates`
- `pulumi new https://github.com/pulumi/templates/tree/master/templates`
- `pulumi new https://github.com/pulumi/templates/tree/HEAD/templates`
Of course, arbitrary branches, tags, or commits can be specified as well:
- `pulumi new https://github.com/pulumi/templates/tree/<branch>/templates`
- `pulumi new https://github.com/pulumi/templates/tree/<tag>/templates`
- `pulumi new https://github.com/pulumi/templates/tree/<commit>/templates`
This PR also includes initial support for passing URLs to `pulumi up`,
providing a streamlined way to deploy installable cloud applications
with Pulumi, without having to manage source code locally before doing
a deployment.
For example, `pulumi up https://github.com/justinvp/aws` can be used to
deploy a sample AWS app. The stack can be updated with different
versions, e.g.
`pulumi up https://github.com/justinvp/aws/tree/v2 -s <stack-to-update>`
Config values can optionally be passed via command line flags, e.g.
`pulumi up https://github.com/justinvp/aws -c aws:region=us-west-2 -c foo:bar=blah`
Gists can also be used, e.g.
`pulumi up https://gist.github.com/justinvp/62fde0463f243fcb49f5a7222e51bc76`
* Fix panic when hitting ^C from "choose template" prompt
* Add description to templates
When running `pulumi new` without specifying a template, include the template description along with the name in the "choose template" display.
```
$ pulumi new
Please choose a template:
aws-go A minimal AWS Go program
aws-javascript A minimal AWS JavaScript program
aws-python A minimal AWS Python program
aws-typescript A minimal AWS TypeScript program
> go A minimal Go program
hello-aws-javascript A simple AWS serverless JavaScript program
javascript A minimal JavaScript program
python A minimal Python program
typescript A minimal TypeScript program
```
* React to changes to the pulumi/templates repo.
We restructured the `pulumi/templates` repo to have all the templates in the root instead of in a `templates` subdirectory, so make the change here to no longer look for templates in `templates`.
This also fixes an issue around using `Depth: 1` that I found while testing this. When a named template is used, we attempt to clone or pull from the `pulumi/templates` repo to `~/.pulumi/templates`. Having it go in this well-known directory allows us to maintain previous behavior around allowing offline use of templates. If we use `Depth: 1` for the initial clone, it will fail when attempting to pull when there are updates to the remote repository. Unfortunately, there's no built-in `--unshallow` support in `go-git` and setting a larger `Depth` doesn't appear to help. There may be a workaround, but for now, if we're cloning the pulumi templates directory to `~/.pulumi/templates`, we won't use `Depth: 1`. For template URLs, we will continue to use `Depth: 1` as we clone those to a temp directory (which gets deleted) that we'll never try to update.
* List available templates in help text
* Address PR Feedback
* Don't show "Installing dependencies" message for `up`
* Fix secrets handling
When prompting for config, if the existing stack value is a secret, keep it a secret and mask the prompt. If the template says it should be secret, make it a secret.
* Fix ${PROJECT} and ${DESCRIPTION} handling for `up`
Templates used with `up` should already have a filled-in project name and description, but if it's a `new`-style template, that has `${PROJECT}` and/or `${DESCRIPTION}`, be helpful and just replace these with better values.
* Fix stack handling
Add a bool `setCurrent` param to `requireStack` to control whether the current stack should be saved in workspace settings. For the `up <url>` case, we don't want to save. Also, split the `up` code into two separate functions: one for the `up <url>` case and another for the normal `up` case where you have workspace in your current directory. While we may be able to combine them back into a single function, right now it's a bit cleaner being separate, even with some small amount of duplication.
* Fix panic due to nil crypter
Lazily get the crypter only if needed inside `promptForConfig`.
* Embellish comment
* Harden isPreconfiguredEmptyStack check
Fix the code to check to make sure the URL specified on the command line matches the URL stored in the `pulumi:template` config value, and that the rest of the config from the stack satisfies the config requirements of the template.
2018-08-11 03:08:16 +02:00
|
|
|
inputs-digest = "54dbb01365a37a74aba07358a4e069c1ae7e9efd3a893e8c2ca6b6d3aea3bfb2"
|
2017-08-02 03:37:06 +02:00
|
|
|
solver-name = "gps-cdcl"
|
|
|
|
solver-version = 1
|