fix(CosmosDb): SSL connection could not be established #1109
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Introduced the CosmosDbContainerWaitStrategy to boost the readiness check by connecting to a specific URL instead of looking for a log message. The existing wait strategy in the CosmosDbBuilder was modified to use this new strategy, thereby making the readiness check more reliable.
✅ Deploy Preview for testcontainers-dotnet ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
|
Seems like i used the wrong git config. Shouldn't be any issue. Sorry for that. |
HofmeisterAn
reviewed
Feb 8, 2024
HofmeisterAn
changed the title
HofmeisterAn
approved these changes
Feb 8, 2024
|
Thanks for looking into this issue and creating the PR. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Introduced the CosmosDbContainerWaitStrategy to boost the readiness check by connecting to a specific URL instead of looking for a log message. The existing wait strategy in the CosmosDbBuilder was modified to use this new strategy, thereby making the readiness check more reliable.
Why is it important?
The current readiness check is not reliable. Although the console output "Started" is logged, the container is not fully ready for use.
Related issues