pulumi/tests/integration/protect_resources/step2/index.ts

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

import { Resource } from "./resource";

// Now, simply update the resource; this should work fine:
let a = new Resource("eternal", { state: 2 }, { protect: true });
Update the copyright end date to 2018. (#1068) Just what it says on the tin. 2018-03-21 20:43:21 +01:00			`// Copyright 2016-2018, Pulumi Corporation. All rights reserved.`
Implement resource protection (#751) This change implements resource protection, as per pulumi/pulumi#689. The overall idea is that a resource can be marked as "protect: true", which will prevent deletion of that resource for any reason whatsoever (straight deletion, replacement, etc). This is expressed in the program. To "unprotect" a resource, one must perform an update setting "protect: false", and then afterwards, they can delete the resource. For example: let res = new MyResource("precious", { .. }, { protect: true }); Afterwards, the resource will display in the CLI with a lock icon, and any attempts to remove it will fail in the usual ways (in planning or, worst case, during an actual update). This was done by adding a new ResourceOptions bag parameter to the base Resource types. This is unfortunately a breaking change, but now is the right time to take this one. We had been adding new settings one by one -- like parent and dependsOn -- and this new approach will set us up to add any number of additional settings down the road, without needing to worry about breaking anything ever again. This is related to protected stacks, as described in pulumi/pulumi-service#399. Most likely this will serve as a foundational building block that enables the coarser grained policy management. 2017-12-20 23:31:07 +01:00
			`import { Resource } from "./resource";`

			`// Now, simply update the resource; this should work fine:`
			`let a = new Resource("eternal", { state: 2 }, { protect: true });`