pulumi/pkg/backend/display.go

// Copyright 2016-2017, Pulumi Corporation.  All rights reserved.

package backend

import "github.com/pulumi/pulumi/pkg/diag/colors"

// DisplayOptions controls how the output of events are rendered
type DisplayOptions struct {
	Color      colors.Colorization // colorization to apply to events
	ShowConfig bool                // true if we should show configuration information before updating or previewing
}
Clean up colorization logic The existing logic would flow colorization information into the engine, so depending on the settings in the CLI, the engine may or may not have emitted colorized events. This coupling is not great and we want to start moving to a world where the presentation happens exclusively at the CLI level. With this change, the engine will always produce strings that have the colorization formatting directives (i.e. the directives that reconquest/loreley understands) and the CLI will apply colorization (which could mean either running loreley to turn the directives into ANSI escape codes, or drop them or retain them, for debuging purposes). Fixes #742 2018-01-31 18:41:42 +01:00			`// Copyright 2016-2017, Pulumi Corporation. All rights reserved.`

			`package backend`

			`import "github.com/pulumi/pulumi/pkg/diag/colors"`

			`// DisplayOptions controls how the output of events are rendered`
			`type DisplayOptions struct {`
Remove UpdateOptions.ShowConfig The engine now unconditionally emits a new type of event, a PreludeEvent, which contains the configuration for a stack as well as an indication if the stack is being previewed or updated. The responsibility for interpreting the --show-config flag on the command line is now handled by the CLI, which uses this to decide if it should print the configuration or not, and then writes the "Previewing changes" or "Deploying chanages" header. 2018-01-31 22:07:40 +01:00			`Color colors.Colorization // colorization to apply to events`
			`ShowConfig bool // true if we should show configuration information before updating or previewing`
Clean up colorization logic The existing logic would flow colorization information into the engine, so depending on the settings in the CLI, the engine may or may not have emitted colorized events. This coupling is not great and we want to start moving to a world where the presentation happens exclusively at the CLI level. With this change, the engine will always produce strings that have the colorization formatting directives (i.e. the directives that reconquest/loreley understands) and the CLI will apply colorization (which could mean either running loreley to turn the directives into ANSI escape codes, or drop them or retain them, for debuging purposes). Fixes #742 2018-01-31 18:41:42 +01:00			`}`