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

Firestore backend only supports byte array data #862

Open
AlexMeuer opened this issue Mar 6, 2020 · 1 comment
Open

Firestore backend only supports byte array data #862

AlexMeuer opened this issue Mar 6, 2020 · 1 comment

Comments

@AlexMeuer
Copy link

AlexMeuer commented Mar 6, 2020

Viper uses github.com/bketelsen/crypt to fetch remote configs. Crypt supports fetching from Firestore but only grabs a field named data which it expects to be an encrypted byte array.

If I'm using Firestore as a config backend, I'm not encrypting the config, I'm putting it there for ease of change. Having to use a single pre-determined field breaks that convenience.

@sagikazarmark
Copy link
Collaborator

Unfortunately this is how the current remote provider works. This will probably change in Viper v2, until then, I would suggest implementing a custom remote provider based on this:

https://github.com/sagikazarmark/viperx

Basically, I've implemented the same thing for Vault.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants