You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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:
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.
The text was updated successfully, but these errors were encountered: