2017-06-26 23:46:34 +02:00
|
|
|
// Copyright 2016-2017, Pulumi Corporation. All rights reserved.
|
2017-03-06 15:32:39 +01:00
|
|
|
|
2017-04-12 19:38:12 +02:00
|
|
|
package main
|
2017-03-06 15:32:39 +01:00
|
|
|
|
|
|
|
import (
|
2017-03-07 14:47:42 +01:00
|
|
|
"errors"
|
|
|
|
|
2017-03-06 15:32:39 +01:00
|
|
|
"github.com/spf13/cobra"
|
|
|
|
|
2017-05-18 20:38:28 +02:00
|
|
|
"github.com/pulumi/lumi/pkg/tokens"
|
|
|
|
"github.com/pulumi/lumi/pkg/util/cmdutil"
|
2017-03-06 15:32:39 +01:00
|
|
|
)
|
|
|
|
|
|
|
|
func newEnvInitCmd() *cobra.Command {
|
|
|
|
return &cobra.Command{
|
|
|
|
Use: "init <env>",
|
|
|
|
Aliases: []string{"create"},
|
|
|
|
Short: "Create an empty environment with the given name, ready for deployments",
|
|
|
|
Long: "Create an empty environment with the given name, ready for deployments\n" +
|
|
|
|
"\n" +
|
|
|
|
"This command creates an empty environment with the given name. It has no resources,\n" +
|
|
|
|
"but afterwards it can become the target of a deployment using the `deploy` command.",
|
2017-04-12 20:12:25 +02:00
|
|
|
Run: cmdutil.RunFunc(func(cmd *cobra.Command, args []string) error {
|
2017-03-06 15:32:39 +01:00
|
|
|
// Read in the name of the environment to use.
|
|
|
|
if len(args) == 0 {
|
2017-03-07 14:47:42 +01:00
|
|
|
return errors.New("missing required environment name")
|
2017-03-06 15:32:39 +01:00
|
|
|
}
|
|
|
|
|
|
|
|
name := tokens.QName(args[0])
|
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
|
|
|
createEnv(name)
|
2017-03-07 14:47:42 +01:00
|
|
|
return nil
|
|
|
|
}),
|
2017-03-06 15:32:39 +01:00
|
|
|
}
|
|
|
|
}
|