pulumi/pkg/engine/destroy.go

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

package engine

import (
	"github.com/pulumi/pulumi/pkg/util/contract"
)

func Destroy(update Update, events chan<- Event, opts UpdateOptions) (ResourceChanges, error) {
	contract.Require(update != nil, "update")

	defer func() { events <- cancelEvent() }()

	info, err := planContextFromUpdate(update)
	if err != nil {
		return nil, err
	}
	defer info.Close()

	return deployLatest(info, deployOptions{
		UpdateOptions: opts,

		Destroy: true,

		Events: events,
		Diag:   newEventSink(events),
	})
}
Wire up Lumi to the new runtime strategy :fire: :fire: :fire: :boat: :fire: :fire: :fire: Getting closer on #311. 2017-08-30 03:24:12 +02:00			`// Copyright 2017, Pulumi Corporation. All rights reserved.`

Move a bunch of code around Move most of the guts of `lumi` into the newly created `engine` package. 2017-08-23 01:56:15 +02:00			`package engine`

Require environment name on deployment APIs Deployments always need to be done in the context of some environment, so let's make the argument explicit instead of it coming in the property bag 2017-10-02 20:14:27 +02:00			`import (`
Have the CLI keep track of the current environment Previously, the engine was concered with maintaing information about the currently active environment. Now, the CLI is in charge of this. As part of this change, the engine can now assume that every environment has a non empty name (and I've added asserts on the entrypoints of the engine API to ensure that any consumer of the engine passes a non empty environment name) 2017-10-03 01:37:12 +02:00			`"github.com/pulumi/pulumi/pkg/util/contract"`
Require environment name on deployment APIs Deployments always need to be done in the context of some environment, so let's make the argument explicit instead of it coming in the property bag 2017-10-02 20:14:27 +02:00			`)`
Move a bunch of code around Move most of the guts of `lumi` into the newly created `engine` package. 2017-08-23 01:56:15 +02:00
Export resource change counts from engine 2018-01-20 21:07:03 +01:00			`func Destroy(update Update, events chan<- Event, opts UpdateOptions) (ResourceChanges, error) {`
Refactor the engine's entrypoints. These changes refactor the engine's entrypoints--Deploy, Destroy, and Preview--to be update-centric rather than stack-centric. Each of these methods now takes a value of a new type, Update, that abstracts away the vagaries of fetching and maintaining the update's state. This refactoring also reinforces Pulumi.yaml as a CLI concept rather than an engine concept; the CLI is now the only reader/writer of this format. These changes will smooth the way for a few refactorings on the service side that will aid in update isolation. 2018-01-08 22:01:40 +01:00			`contract.Require(update != nil, "update")`
Have the CLI keep track of the current environment Previously, the engine was concered with maintaing information about the currently active environment. Now, the CLI is in charge of this. As part of this change, the engine can now assume that every environment has a non empty name (and I've added asserts on the entrypoints of the engine API to ensure that any consumer of the engine passes a non empty environment name) 2017-10-03 01:37:12 +02:00
Break the diag goroutine upon exit 2017-10-23 00:52:00 +02:00			`defer func() { events <- cancelEvent() }()`

Remove the Engine type entirely. It no longer carries any state. All of its methods are now package-level functions. 2018-01-08 23:20:51 +01:00			`info, err := planContextFromUpdate(update)`
Move a bunch of code around Move most of the guts of `lumi` into the newly created `engine` package. 2017-08-23 01:56:15 +02:00			`if err != nil {`
Export resource change counts from engine 2018-01-20 21:07:03 +01:00			`return nil, err`
Move a bunch of code around Move most of the guts of `lumi` into the newly created `engine` package. 2017-08-23 01:56:15 +02:00			`}`
Initial work on tracing support (#521) Adds OpenTracing in the Pulumi engine and plugin + langhost subprocesses. We currently create a single root span for any `Enging.plan` operation - which is a single `preview`, `update`, `destroy`, etc. The only sub-spans we currently create are at gRPC boundaries, both on the client and server sides and on both the langhost and provider plugin interfaces. We could extend this to include spans for any other semantically meaningful sections of compute inside the engine, though initial examples show we get pretty good granularity of coverage by focusing on the gRPC boundaries. In the future, this should be easily extensible to HTTP boundaries and to track other bulky I/O like datastore read/writes once we hook up to the PPC and Pulumi Cloud. We expose a `--trace <endpoint>` option to enable tracing on the CLI, which we will aim to thread through to subprocesses. We currently support sending tracing data to a Zipkin-compatible endpoint. This has been validated with both Zipkin and Jaeger UIs. We do not yet have any tracing inside the TypeScript side of the JS langhost RPC interface. There is not yet automatic gRPC OpenTracing instrumentation (though it looks like it's in progress now) - so we would need to manually create meaningful spans on that side of the interface. 2017-11-09 02:08:51 +01:00			`defer info.Close()`
Move a bunch of code around Move most of the guts of `lumi` into the newly created `engine` package. 2017-08-23 01:56:15 +02:00
Remove the Engine type entirely. It no longer carries any state. All of its methods are now package-level functions. 2018-01-08 23:20:51 +01:00			`return deployLatest(info, deployOptions{`
Surface update options to the service (#806) This PR surfaces the configuration options available to updates, previews, and destroys to the Pulumi Service. As part of this I refactored the options to unify them into a single `engine.UpdateOptions`, since they were all overlapping to various degrees. With this PR we are adding several new flags to commands, e.g. `--summary` was not available on `pulumi destroy`. There are also a few minor breaking changes. - `pulumi destroy --preview` is now `pulumi destroy --dry-run` (to match the actual name of the field). - The default behavior for "--color" is now `Always`. Previously it was `Always` or `Never` based on the value of a `--debug` flag. (You can specify `--color always` or `--color never` to get the exact behavior.) Fixes #515, and cleans up the code making some other features slightly easier to add. 2018-01-18 20:10:15 +01:00			`UpdateOptions: opts,`

			`Destroy: true,`

			`Events: events,`
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			`Diag: newEventSink(events),`
Move a bunch of code around Move most of the guts of `lumi` into the newly created `engine` package. 2017-08-23 01:56:15 +02:00			`})`
			`}`