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.
13 lines
401 B
Go
13 lines
401 B
Go
// Copyright 2017 Pulumi, Inc. All rights reserved.
|
|
|
|
package workspace
|
|
|
|
import (
|
|
"github.com/pulumi/coconut/pkg/tokens"
|
|
)
|
|
|
|
// Settings defines workspace settings shared amongst many related projects.
|
|
type Settings struct {
|
|
Namespace string `json:"namespace,omitempty"` // an optional namespace.
|
|
Env tokens.QName `json:"env,omitempty"` // an optional default environment to use.
|
|
}
|