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

Inconsistent Behavior with Viper Config Update and Reload #1827

Open
3 tasks
suvidhamalaviya3112 opened this issue May 8, 2024 · 1 comment
Open
3 tasks
Labels
kind/bug Something isn't working

Comments

@suvidhamalaviya3112
Copy link

suvidhamalaviya3112 commented May 8, 2024

Preflight Checklist

  • I have searched the issue tracker for an issue that matches the one I want to file, without success.
  • I am not looking for support or already pursued the available support channels without success.
  • I have checked the troubleshooting guide for my problem, without success.

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.

@suvidhamalaviya3112 suvidhamalaviya3112 added the kind/bug Something isn't working label May 8, 2024
Copy link

github-actions bot commented May 8, 2024

👋 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! ❤️

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant