66bd3f4aa8
* Make `async:true` the default for `invoke` calls (#3750) * Switch away from native grpc impl. (#3728) * Remove usage of the 'deasync' library from @pulumi/pulumi. (#3752) * Only retry as long as we get unavailable back. Anything else continues. (#3769) * Handle all errors for now. (#3781) * Do not assume --yes was present when using pulumi in non-interactive mode (#3793) * Upgrade all paths for sdk and pkg to v2 * Backport C# invoke classes and other recent gen changes (#4288) Adjust C# generation * Replace IDeployment with a sealed class (#4318) Replace IDeployment with a sealed class * .NET: default to args subtype rather than Args.Empty (#4320) * Adding system namespace for Dotnet code gen This is required for using Obsolute attributes for deprecations ``` Iam/InstanceProfile.cs(142,10): error CS0246: The type or namespace name 'ObsoleteAttribute' could not be found (are you missing a using directive or an assembly reference?) [/Users/stack72/code/go/src/github.com/pulumi/pulumi-aws/sdk/dotnet/Pulumi.Aws.csproj] Iam/InstanceProfile.cs(142,10): error CS0246: The type or namespace name 'Obsolete' could not be found (are you missing a using directive or an assembly reference?) [/Users/stack72/code/go/src/github.com/pulumi/pulumi-aws/sdk/dotnet/Pulumi.Aws.csproj] ``` * Fix the nullability of config type properties in C# codegen (#4379) |
||
|---|---|---|
| .. | ||
| step1 | ||
| step2 | ||
| step3 | ||
| step4 | ||
| step5 | ||
| step6 | ||
| README.md | ||
| steps_test.go | ||
README.md
tests/integration/steps
This test attempts to exhaustively try all interesting combinations of resource steps. This includes:
- Same
- Create
- Update
- Delete
- CreateReplacement
- DeleteReplaced
in addition to the ability to recover from failures. For example, there is a "pending deletion" capability that will remember resources that were meant to be deleted, but couldn't be, due to a failure partway through.
The test is broken into a series of steps that will be executed in order. Because the steps create different resources, we will end up with a specific sequence of CRUD operations that we will validate.
Step 1
Populate the world:
- Create 4 resources, a1, b1, c1, d1. c1 depends on a1 via an ID property.
Checkpoint: a1, b1, c1, d1
Step 2
Same, Update, Same, Delete, Create:
-
Create 1 resource, a2, equivalent to the a1 in Step 1 (Same(a1, a2)).
-
Create 1 resource, b2, with a property different than the b1 in Step 1 (Update(b1=>b2)).
-
Create 1 resource, c2, equivalent to the c1 in Step 1 (Same(c1, c2)).
-
Elide d (Delete(d1)).
-
Create 1 resource, e2, not present in Step 1 (Create(e2)).
Checkpoint: a2, b2, c2, e2
Step 3
Replace a resource:
-
Create 1 resource, a3, with a property different than the a2 in Step 2, requiring replacement (CreateReplacement(a3), Update(c2=>c3), DeleteReplaced(a2)).
-
Elide b (Delete(b2)).
-
Create 2 resources, c3 and e3, equivalent to Step 2 (Same(c2, c3), Same(e2, e3)).
Checkpoint: a3, c3, e3
Step 4
Replace a resource (but this time, deleteBeforeReplace):
-
Create 1 resource, a4, equivalent to the a3 in Step 3 (Same(a3, a4)).
-
Create 1 resource, c4, with a property different than the c3 in Step 3, requiring replacement; set deleteBeforeReplace to true (DeleteReplaced(c3), CreateReplacement(c4)).
-
Create 1 resource, e4, equivlaent to the e3 in Step 3 (Same(e3, e4)).
Checkpoint: a4, c4, e4
Step 5
Fail during an update:
-
Create 1 resource, a5, with a property different than the a4 in Step 4, requiring replacement (CreateReplacement(a5), Update(c4=>c5), DeleteReplaced(a4)).
-
Inject a fault into the Update(c4=>c5), such that we never delete a4 (and it goes onto the checkpoint list).
Checkpoint: a5, c5, e5; pending delete: a4
Step 6
Delete everything:
-
Elide a (Delete(a5)).
-
Elide c (Delete(c)).
-
Elide e (Delete(e)).
-
Pending delete (Delete(a4)).
Checkpoint: empty