2017-06-26 23:46:34 +02:00
|
|
|
// Copyright 2016-2017, Pulumi Corporation. All rights reserved.
|
2017-03-15 23:40:06 +01:00
|
|
|
|
2017-09-22 04:18:21 +02:00
|
|
|
package cmd
|
2017-03-15 23:40:06 +01:00
|
|
|
|
|
|
|
|
import (
|
|
|
|
|
"github.com/spf13/cobra"
|
Make major commands more pleasant
This change eliminates the need to constantly type in the environment
name when performing major commands like configuration, planning, and
deployment. It's probably due to my age, however, I keep fat-fingering
simple commands in front of investors and I am embarrassed!
In the new model, there is a notion of a "current environment", and
I have modeled it kinda sorta just like Git's notion of "current branch."
By default, the current environment is set when you `init` something.
Otherwise, there is the `coco env select <env>` command to change it.
(Running this command w/out a new <env> will show you the current one.)
The major commands `config`, `plan`, `deploy`, and `destroy` will prefer
to use the current environment, unless it is overridden by using the
--env flag. All of the `coco env <cmd> <env>` commands still require the
explicit passing of an environment which seems reasonable since they are,
after all, about manipulating environments.
As part of this, I've overhauled the aging workspace settings cruft,
which had fallen into disrepair since the initial prototype.
2017-03-22 03:23:32 +01:00
|
|
|
|
2017-09-22 04:18:21 +02:00
|
|
|
"github.com/pulumi/pulumi/pkg/engine"
|
|
|
|
|
"github.com/pulumi/pulumi/pkg/util/cmdutil"
|
|
|
|
|
"github.com/pulumi/pulumi/pkg/util/contract"
|
2017-03-15 23:40:06 +01:00
|
|
|
)
|
|
|
|
|
|
|
|
|
|
func newPlanCmd() *cobra.Command {
|
|
|
|
|
var analyzers []string
|
2017-07-14 02:09:46 +02:00
|
|
|
var debug bool
|
2017-03-23 16:10:33 +01:00
|
|
|
var dotOutput bool
|
Make major commands more pleasant
This change eliminates the need to constantly type in the environment
name when performing major commands like configuration, planning, and
deployment. It's probably due to my age, however, I keep fat-fingering
simple commands in front of investors and I am embarrassed!
In the new model, there is a notion of a "current environment", and
I have modeled it kinda sorta just like Git's notion of "current branch."
By default, the current environment is set when you `init` something.
Otherwise, there is the `coco env select <env>` command to change it.
(Running this command w/out a new <env> will show you the current one.)
The major commands `config`, `plan`, `deploy`, and `destroy` will prefer
to use the current environment, unless it is overridden by using the
--env flag. All of the `coco env <cmd> <env>` commands still require the
explicit passing of an environment which seems reasonable since they are,
after all, about manipulating environments.
As part of this, I've overhauled the aging workspace settings cruft,
which had fallen into disrepair since the initial prototype.
2017-03-22 03:23:32 +01:00
|
|
|
var env string
|
2017-09-17 17:10:46 +02:00
|
|
|
var parallel int
|
2017-03-15 23:40:06 +01:00
|
|
|
var showConfig bool
|
2017-08-06 19:05:51 +02:00
|
|
|
var showReplacementSteps bool
|
2017-06-11 17:09:20 +02:00
|
|
|
var showSames bool
|
2017-03-15 23:40:06 +01:00
|
|
|
var summary bool
|
|
|
|
|
var cmd = &cobra.Command{
|
Make major commands more pleasant
This change eliminates the need to constantly type in the environment
name when performing major commands like configuration, planning, and
deployment. It's probably due to my age, however, I keep fat-fingering
simple commands in front of investors and I am embarrassed!
In the new model, there is a notion of a "current environment", and
I have modeled it kinda sorta just like Git's notion of "current branch."
By default, the current environment is set when you `init` something.
Otherwise, there is the `coco env select <env>` command to change it.
(Running this command w/out a new <env> will show you the current one.)
The major commands `config`, `plan`, `deploy`, and `destroy` will prefer
to use the current environment, unless it is overridden by using the
--env flag. All of the `coco env <cmd> <env>` commands still require the
explicit passing of an environment which seems reasonable since they are,
after all, about manipulating environments.
As part of this, I've overhauled the aging workspace settings cruft,
which had fallen into disrepair since the initial prototype.
2017-03-22 03:23:32 +01:00
|
|
|
Use: "plan [<package>] [-- [<args>]]",
|
2017-03-15 23:40:06 +01:00
|
|
|
Aliases: []string{"dryrun"},
|
|
|
|
|
Short: "Show a plan to update, create, and delete an environment's resources",
|
|
|
|
|
Long: "Show a plan to update, create, and delete an environment's resources\n" +
|
|
|
|
|
"\n" +
|
|
|
|
|
"This command displays a plan to update an existing environment whose state is represented by\n" +
|
|
|
|
|
"an existing snapshot file. The new desired state is computed by compiling and evaluating an\n" +
|
|
|
|
|
"executable package, and extracting all resource allocations from its resulting object graph.\n" +
|
|
|
|
|
"This graph is compared against the existing state to determine what operations must take\n" +
|
|
|
|
|
"place to achieve the desired state. No changes to the environment will actually take place.\n" +
|
|
|
|
|
"\n" +
|
|
|
|
|
"By default, the package to execute is loaded from the current directory. Optionally, an\n" +
|
|
|
|
|
"explicit path can be provided using the [package] argument.",
|
2017-04-12 20:12:25 +02:00
|
|
|
Run: cmdutil.RunFunc(func(cmd *cobra.Command, args []string) error {
|
2017-09-22 04:18:21 +02:00
|
|
|
contract.Assertf(!dotOutput, "TODO[pulumi/pulumi#235]: DOT files not yet supported")
|
2017-08-23 01:23:50 +02:00
|
|
|
|
2017-08-23 19:58:35 +02:00
|
|
|
return lumiEngine.Plan(engine.PlanOptions{
|
2017-08-23 01:23:50 +02:00
|
|
|
Package: pkgargFromArgs(args),
|
2017-08-06 19:05:51 +02:00
|
|
|
Debug: debug,
|
2017-08-23 01:23:50 +02:00
|
|
|
Environment: env,
|
2017-08-06 19:05:51 +02:00
|
|
|
Analyzers: analyzers,
|
2017-09-17 17:10:46 +02:00
|
|
|
Parallel: parallel,
|
2017-08-06 19:05:51 +02:00
|
|
|
ShowConfig: showConfig,
|
|
|
|
|
ShowReplacementSteps: showReplacementSteps,
|
|
|
|
|
ShowSames: showSames,
|
|
|
|
|
Summary: summary,
|
2017-08-23 01:23:50 +02:00
|
|
|
})
|
2017-03-15 23:40:06 +01:00
|
|
|
}),
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
cmd.PersistentFlags().StringSliceVar(
|
|
|
|
|
&analyzers, "analyzer", []string{},
|
|
|
|
|
"Run one or more analyzers as part of this deployment")
|
2017-07-14 02:09:46 +02:00
|
|
|
cmd.PersistentFlags().BoolVarP(
|
|
|
|
|
&debug, "debug", "d", false,
|
|
|
|
|
"Print detailed debugging output during resource operations")
|
2017-03-23 16:10:33 +01:00
|
|
|
cmd.PersistentFlags().BoolVar(
|
|
|
|
|
&dotOutput, "dot", false,
|
|
|
|
|
"Output the plan as a DOT digraph (graph description language)")
|
Make major commands more pleasant
This change eliminates the need to constantly type in the environment
name when performing major commands like configuration, planning, and
deployment. It's probably due to my age, however, I keep fat-fingering
simple commands in front of investors and I am embarrassed!
In the new model, there is a notion of a "current environment", and
I have modeled it kinda sorta just like Git's notion of "current branch."
By default, the current environment is set when you `init` something.
Otherwise, there is the `coco env select <env>` command to change it.
(Running this command w/out a new <env> will show you the current one.)
The major commands `config`, `plan`, `deploy`, and `destroy` will prefer
to use the current environment, unless it is overridden by using the
--env flag. All of the `coco env <cmd> <env>` commands still require the
explicit passing of an environment which seems reasonable since they are,
after all, about manipulating environments.
As part of this, I've overhauled the aging workspace settings cruft,
which had fallen into disrepair since the initial prototype.
2017-03-22 03:23:32 +01:00
|
|
|
cmd.PersistentFlags().StringVarP(
|
|
|
|
|
&env, "env", "e", "",
|
|
|
|
|
"Choose an environment other than the currently selected one")
|
2017-09-17 17:10:46 +02:00
|
|
|
cmd.PersistentFlags().IntVarP(
|
|
|
|
|
¶llel, "parallel", "p", 0,
|
|
|
|
|
"Allow P resource operations to run in parallel at once (<=1 for no parallelism)")
|
2017-03-15 23:40:06 +01:00
|
|
|
cmd.PersistentFlags().BoolVar(
|
|
|
|
|
&showConfig, "show-config", false,
|
|
|
|
|
"Show configuration keys and variables")
|
Implement `get` functions on all resources
This change implements the `get` function for resources. Per pulumi/lumi#83,
this allows Lumi scripts to actually read from the target environment.
For example, we can now look up a SecurityGroup from its ARN:
let group = aws.ec2.SecurityGroup.get(
"arn:aws:ec2:us-west-2:153052954103:security-group:sg-02150d79");
The returned object is a fully functional resource object. So, we can then
link it up with an EC2 instance, for example, in the usual ways:
let instance = new aws.ec2.Instance(..., {
securityGroups: [ group ],
});
This didn't require any changes to the RPC or provider model, since we
already implement the Get function.
There are a few loose ends; two are short term:
1) URNs are not rehydrated.
2) Query is not yet implemented.
One is mid-term:
3) We probably want a URN-based lookup function. But we will likely
wait until we tackle pulumi/lumi#109 before adding this.
And one is long term (and subtle):
4) These amount to I/O and are not repeatable! A change in the target
environment may cause a script to generate a different plan
intermittently. Most likely we want to apply a different kind of
deployment "policy" for such scripts. These are inching towards the
scripting model of pulumi/lumi#121, which is an entirely different
beast than the repeatable immutable infrastructure deployments.
Finally, it is worth noting that with this, we have some of the fundamental
underpinnings required to finally tackle "inference" (pulumi/lumi#142).
2017-06-20 02:24:00 +02:00
|
|
|
cmd.PersistentFlags().BoolVar(
|
2017-08-06 19:05:51 +02:00
|
|
|
&showReplacementSteps, "show-replacement-steps", false,
|
|
|
|
|
"Show detailed resource replacement creates and deletes instead of a single step")
|
2017-03-15 23:40:06 +01:00
|
|
|
cmd.PersistentFlags().BoolVar(
|
2017-06-11 17:09:20 +02:00
|
|
|
&showSames, "show-sames", false,
|
2017-03-15 23:40:06 +01:00
|
|
|
"Show resources that needn't be updated because they haven't changed, alongside those that do")
|
|
|
|
|
cmd.PersistentFlags().BoolVarP(
|
|
|
|
|
&summary, "summary", "s", false,
|
|
|
|
|
"Only display summarization of resources and plan operations")
|
|
|
|
|
|
|
|
|
|
return cmd
|
|
|
|
|
}
|
