-
Notifications
You must be signed in to change notification settings - Fork 104
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create example for testing parallel ECS updates #1334
Conversation
@@ -201,6 +202,24 @@ func TestVpcMultipleSimilarSubnetSpecArgs(t *testing.T) { | |||
integration.ProgramTest(t, &test) | |||
} | |||
|
|||
func TestAccEcsParallel(t *testing.T) { | |||
maxDuration(15*time.Minute, t, func(t *testing.T) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Deploying and updating 10 of these ECS services took 1+ hours before. Now that it's all parallel it runs in under 10min
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good! My only question is whether we need this test in pulumi-awsx
. I feel like a regression test belongs in pu/pu
since that is where the breaking change would happen and where the fix would be needed.
Generally I agree with you, but this aspect of pu/pu is under-tested right now. I tried adding some tests for this area (provider server) there, but this would've required to refactor the provider server, which would be quite the rabbit hole. |
/release minor |
This PR has been shipped in release v2.13.0. |
Adding an example to test parallel updates to components like ECS services. Currently component updates are serialized (#1250), but pulumi/pulumi#7629 fixed that.
I used this test for verifying the changes locally, now that the change is released we can use this as a regression test