Added support for Firestore remote provider #836
Merged
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
|
|
|
Although I'm generally against merging more providers into the Viper core, this is a simple change in a well-shaped PR, so 👍 |
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.
I'm using
viperfor cloud-native applications. So,etcdandconsulare not well solutions for me to configure my applications.This PR supports Firestore for developers who'd like to use Google Cloud Platform, for example
Additionally, I've updated dependency for
cryptlibrary, because looks likegit.luolix.top/xordataexchange/cryptis dead for a long time. And now this library is been developing in the forkgit.luolix.top/bketelsen/crypt