Update themes/default/content/blog/continue-on-error/index.md

Co-authored-by: Justin Van Patten <[email protected]>
pulumi · May 6, 2024 · 3dccb18 · 3dccb18
1 parent 4876374
commit 3dccb18
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/themes/default/content/blog/continue-on-error/index.md b/themes/default/content/blog/continue-on-error/index.md
@@ -55,6 +55,6 @@ When the execution finishes, Pulumi will report the resource failures as you wou
 
 `pulumi destroy --continue-on-error` was introduced in Pulumi v3.112.0.  After upgrading to this version you can go ahead and use this feature.
 
-The situation for `pulumi up --continue-on-error` is slightly more complicated.  Since we now have resources that fail to create, but the pulumi program continues to execute, the SDK has to deal with the outputs of these resources.  Currently during `pulumi up` there are no "unknown" values expected by the SDK.  Since we may now have a failed resource, the outputs for that resource might still be unknown, and the SDK will have to deal with that.  This means that to fully support this feature some SDK changes were necessary.  So in addition to upgrading to Pulumi v3.114.0, you will also have to upgrade the Pulumi SDK to v3.114.0 for Go, Python and NodeJS, 3.63.0 for dotnet and 1.7.0 for yaml.
+`pulumi up --continue-on-error` was introduced in Pulumi v3.114.0. However, it also requires updated language SDKs to work best. Since we now have resources that fail to create, but the Pulumi program continues to execute, the SDK has to deal with the outputs of these resources.  Currently during `pulumi up` there are no "unknown" values expected by the SDK.  Since we may now have a failed resource, the outputs for that resource might still be unknown, and the SDK will have to deal with that.  This means that to fully support this feature some SDK changes were necessary.  So in addition to upgrading the Pulumi CLI to v3.114.0, you will also have to upgrade the Pulumi SDK to v3.114.0 for Go, Python and Node.js, 3.63.0 for .NET. For Pulumi YAML programs, you'll need to use v3.115.0 of the Pulumi CLI.
 
 The flag still exists for older SDK versions, however the Pulumi engine will return an error to your program, which then will need to be handled, or the rest of the program might not be executed, and thus some resources may not be updated.