github-actions[bot]
commented
1 month ago š Thanks for reporting!
A maintainer will take a look at your issue shortly. š
In the meantime: We are working on Viper v2 and we would love to hear your thoughts about what you like or don't like about Viper, so we can improve or fix those issues.
ā° If you have a couple minutes, please take some time and share your thoughts: https://forms.gle/R6faU74qPRPAzchZ9
š£ If you've already given us your feedback, you can still help by spreading the news, either by sharing the above link or telling people about this on Twitter:
https://twitter.com/sagikazarmark/status/1306904078967074816
Thank you! ā¤ļø
Preflight Checklist
Viper Version
1.18.1
Go Version
1.20
Config Source
Files, Remove K/V stores
Format
YAML
Repl.it link
No response
Code reproducing the issue
No response
Expected Behavior
The tool should consistently update the specified key-value pair without losing existing data.
Actual Behavior
Sometimes, the configuration is not read properly into memory, causing the tool to update data before existing data is loaded. Consequently, existing data is lost, and the YAML file contains only the newly added data.
Steps To Reproduce
No response
Additional Information
I have a tool written in Golang that utilizes Viper for updating YAML files based on received API objects, as well as for unmarshalling YAML data into objects. However, I'm encountering inconsistent behaviour where sometimes the tool fails to update specific key-value pairs, leading to the loss of existing data and the override of the updated key-value pairs. I have debugged the issue and observed through logging that the configuration is not consistently read into memory, leading to this inconsistent behavior.
Note: This is observed interminnetly.