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

When a key has a url in it, v.Get should return v.override values, instead of only v.config #36

Merged
merged 2 commits into from
May 28, 2024

Conversation

dustmop
Copy link

@dustmop dustmop commented May 23, 2024

No description provided.

dustmop added 2 commits May 23, 2024 10:12
When we assign to a map that uses urls for keys, we need to lookup values from that map in the same manner. Without doing so, `Get` will return inconsistent results. The agent codebase generally doesn't call `Get` this way, because we've known url keys work weird, but viper uses this type of call within AllSettings() in order to rebuild the config. In some cases, this could corrupt the data in the config.
@dustmop dustmop requested a review from a team as a code owner May 23, 2024 16:01
@dustmop dustmop changed the title When a key has a url in it, v.Get should return v.override values, instead of only v.default When a key has a url in it, v.Get should return v.override values, instead of only v.config May 23, 2024
@dustmop dustmop merged commit c4cf4fd into master May 28, 2024
7 checks passed
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

Successfully merging this pull request may close these issues.

2 participants