Skip to content
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

Simply k8s client configmap event reload it (7) #1425

Conversation

wind57
Copy link
Contributor

@wind57 wind57 commented Aug 27, 2023

No description provided.

@@ -625,10 +627,11 @@ private boolean isDeploymentReady(String deploymentName, String namespace) throw
return availableReplicas != null && availableReplicas >= 1;
}

private static void waitForDeploymentAfterPatch(String deploymentName, String namespace) {
private static void waitForDeploymentAfterPatch(String deploymentName, String namespace,
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this makes this method "stronger", meaning it makes it far more reliable in terms of knowing when it is safe to start assertions after a patch. I was forced to add labels in here and look for pods because I was having problems with tests

@wind57
Copy link
Contributor Author

wind57 commented Sep 11, 2023

this PR goes in the same direction of changing the way we test via PATCH, decrease test times by around 1.5 minutes here

@wind57 wind57 marked this pull request as ready for review September 11, 2023 20:54
@wind57
Copy link
Contributor Author

wind57 commented Sep 11, 2023

@ryanjbaxter one more refactor, things will get somehow more fun soon, when I remove integrations tests. Thank you

@ryanjbaxter ryanjbaxter added this to the 3.0.5 milestone Sep 11, 2023
@ryanjbaxter ryanjbaxter merged commit f957d04 into spring-cloud:3.0.x Sep 11, 2023
22 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
No open projects
Status: Done
Development

Successfully merging this pull request may close these issues.

3 participants