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.
This update addresses an issue in previous versions of zitadel-rust where the crate was unable to connect to the server. The cause of this issue was that the previous versions of this crate was unable to find certificates which consistently results in the error message "could not set up TLS connection".
The reason of this error message is that there isn't always a certificate within the image thus resulting in this error.
To fix this issue I've added an option for the user that lets him choose between using tls-roots or using tls-webpki-roots
However, it's important to note that this change introduces a breaking change to the crate's configuration options.
Users are now required to choose between using tls-roots or tls-webpki-roots for TLS certificate configurations.
Whilst this change may be inconvenient, it is pretty usual within other crates choose between tls-webpki-roots and tls-roots.
Here's an example of how to use the new configuration:
or