pulumi/pkg/operations/resources_test.go

112 lines
3.4 KiB
Go
Raw Normal View History

2018-05-22 21:43:36 +02:00
// Copyright 2016-2018, Pulumi Corporation.
//
// Licensed under the Apache License, Version 2.0 (the "License");
// you may not use this file except in compliance with the License.
// You may obtain a copy of the License at
//
// http://www.apache.org/licenses/LICENSE-2.0
//
// Unless required by applicable law or agreed to in writing, software
// distributed under the License is distributed on an "AS IS" BASIS,
// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
// See the License for the specific language governing permissions and
// limitations under the License.
2017-11-28 21:54:36 +01:00
2017-11-20 07:28:49 +01:00
package operations
import (
"encoding/json"
"io/ioutil"
"testing"
"github.com/stretchr/testify/assert"
"github.com/pulumi/pulumi/pkg/apitype"
"github.com/pulumi/pulumi/pkg/resource/stack"
)
2017-11-20 02:41:11 +01:00
func getPulumiResources(t *testing.T, path string) *Resource {
Implement more precise delete-before-replace semantics. (#2369) This implements the new algorithm for deciding which resources must be deleted due to a delete-before-replace operation. We need to compute the set of resources that may be replaced by a change to the resource under consideration. We do this by taking the complete set of transitive dependents on the resource under consideration and removing any resources that would not be replaced by changes to their dependencies. We determine whether or not a resource may be replaced by substituting unknowns for input properties that may change due to deletion of the resources their value depends on and calling the resource provider's Diff method. This is perhaps clearer when described by example. Consider the following dependency graph: A __|__ B C | _|_ D E F In this graph, all of B, C, D, E, and F transitively depend on A. It may be the case, however, that changes to the specific properties of any of those resources R that would occur if a resource on the path to A were deleted and recreated may not cause R to be replaced. For example, the edge from B to A may be a simple dependsOn edge such that a change to B does not actually influence any of B's input properties. In that case, neither B nor D would need to be deleted before A could be deleted. In order to make the above algorithm a reality, the resource monitor interface has been updated to include a map that associates an input property key with the list of resources that input property depends on. Older clients of the resource monitor will leave this map empty, in which case all input properties will be treated as depending on all dependencies of the resource. This is probably overly conservative, but it is less conservative than what we currently implement, and is certainly correct.
2019-01-28 18:46:30 +01:00
var checkpoint apitype.CheckpointV3
byts, err := ioutil.ReadFile(path)
assert.NoError(t, err)
err = json.Unmarshal(byts, &checkpoint)
assert.NoError(t, err)
Improve the overall cloud CLI experience This improves the overall cloud CLI experience workflow. Now whether a stack is local or cloud is inherent to the stack itself. If you interact with a cloud stack, we transparently talk to the cloud; if you interact with a local stack, we just do the right thing, and perform all operations locally. Aside from sometimes seeing a cloud emoji pop-up ☁️, the experience is quite similar. For example, to initialize a new cloud stack, simply: $ pulumi login Logging into Pulumi Cloud: https://pulumi.com/ Enter Pulumi access token: <enter your token> $ pulumi stack init my-cloud-stack Note that you may log into a specific cloud if you'd like. For now, this is just for our own testing purposes, but someday when we support custom clouds (e.g., Enterprise), you can just say: $ pulumi login --cloud-url https://corp.acme.my-ppc.net:9873 The cloud is now the default. If you instead prefer a "fire and forget" style of stack, you can skip the login and pass `--local`: $ pulumi stack init my-faf-stack --local If you are logged in and run `pulumi`, we tell you as much: $ pulumi Usage: pulumi [command] // as before... Currently logged into the Pulumi Cloud ☁️ https://pulumi.com/ And if you list your stacks, we tell you which one is local or not: $ pulumi stack ls NAME LAST UPDATE RESOURCE COUNT CLOUD URL my-cloud-stack 2017-12-01 ... 3 https://pulumi.com/ my-faf-stack n/a 0 n/a And `pulumi stack` by itself prints information like your cloud org, PPC name, and so on, in addition to the usuals. I shall write up more details and make sure to document these changes. This change also fairly significantly refactors the layout of cloud versus local logic, so that the cmd/ package is resonsible for CLI things, and the new pkg/backend/ package is responsible for the backends. The following is the overall resulting package architecture: * The backend.Backend interface can be implemented to substitute a new backend. This has operations to get and list stacks, perform updates, and so on. * The backend.Stack struct is a wrapper around a stack that has or is being manipulated by a Backend. It resembles our existing Stack notions in the engine, but carries additional metadata about its source. Notably, it offers functions that allow operations like updating and deleting on the Backend from which it came. * There is very little else in the pkg/backend/ package. * A new package, pkg/backend/local/, encapsulates all local state management for "fire and forget" scenarios. It simply implements the above logic and contains anything specific to the local experience. * A peer package, pkg/backend/cloud/, encapsulates all logic required for the cloud experience. This includes its subpackage apitype/ which contains JSON schema descriptions required for REST calls against the cloud backend. It also contains handy functions to list which clouds we have authenticated with. * A subpackage here, pkg/backend/state/, is not a provider at all. Instead, it contains all of the state management functions that are currently shared between local and cloud backends. This includes configuration logic -- including encryption -- as well as logic pertaining to which stacks are known to the workspace. This addresses pulumi/pulumi#629 and pulumi/pulumi#494.
2017-12-02 16:29:46 +01:00
snapshot, err := stack.DeserializeCheckpoint(&checkpoint)
assert.NoError(t, err)
resources := NewResourceTree(snapshot.Resources)
2017-11-20 02:41:11 +01:00
return resources
}
func TestTodo(t *testing.T) {
2017-11-20 02:41:11 +01:00
components := getPulumiResources(t, "testdata/todo.json")
assert.Equal(t, 4, len(components.Children))
2017-11-20 02:41:11 +01:00
// Table child
table, ok := components.GetChild("cloud:table:Table", "todo")
assert.True(t, ok)
2017-11-20 02:41:11 +01:00
if !assert.NotNil(t, table) {
return
}
assert.Equal(t, 2, len(table.State.Inputs))
assert.Equal(t, "id", table.State.Inputs["primaryKey"].StringValue())
assert.Equal(t, 1, len(table.Children))
table, ok = table.GetChild("aws:dynamodb/table:Table", "todo")
assert.True(t, ok)
assert.NotNil(t, table)
2017-11-20 02:41:11 +01:00
// Endpoint child
endpoint, ok := components.GetChild("cloud:http:HttpEndpoint", "todo")
assert.True(t, ok)
2017-11-20 02:41:11 +01:00
if !assert.NotNil(t, endpoint) {
return
}
assert.Equal(t, 5, len(endpoint.State.Inputs))
assert.Equal(t,
"https://eupwl7wu4i.execute-api.us-east-2.amazonaws.com/", endpoint.State.Inputs["url"].StringValue())
assert.Equal(t, 14, len(endpoint.Children))
endpoint, ok = endpoint.GetChild("aws:apigateway/restApi:RestApi", "todo")
assert.True(t, ok)
assert.NotNil(t, endpoint)
// Nonexistant resource.
r, ok := endpoint.GetChild("garden:ornimentation/gnome", "stone")
assert.False(t, ok)
assert.Nil(t, r)
}
func TestCrawler(t *testing.T) {
2017-11-20 02:41:11 +01:00
components := getPulumiResources(t, "testdata/crawler.json")
assert.Equal(t, 7, len(components.Children))
2017-11-20 02:41:11 +01:00
// Topic child
topic, ok := components.GetChild("cloud:topic:Topic", "countDown")
assert.True(t, ok)
2017-11-20 02:41:11 +01:00
if !assert.NotNil(t, topic) {
return
}
assert.Equal(t, 0, len(topic.State.Inputs))
assert.Equal(t, 1, len(topic.Children))
topic, ok = topic.GetChild("aws:sns/topic:Topic", "countDown")
assert.True(t, ok)
assert.NotNil(t, topic)
2017-11-20 02:41:11 +01:00
// Timer child
heartbeat, ok := components.GetChild("cloud:timer:Timer", "heartbeat")
assert.True(t, ok)
2017-11-20 02:41:11 +01:00
if !assert.NotNil(t, heartbeat) {
return
}
assert.Equal(t, 1, len(heartbeat.State.Inputs))
assert.Equal(t, "rate(5 minutes)", heartbeat.State.Inputs["scheduleExpression"].StringValue())
assert.Equal(t, 4, len(heartbeat.Children))
2017-11-20 02:41:11 +01:00
// Function child of timer
function, ok := heartbeat.GetChild("cloud:function:Function", "heartbeat")
assert.True(t, ok)
2017-11-20 02:41:11 +01:00
if !assert.NotNil(t, function) {
return
}
assert.Equal(t, 1, len(function.State.Inputs))
assert.Equal(t, 3, len(function.Children))
}