Maxime/revert go version bump#2136
Closed
hush-hush wants to merge 98 commits into
Closed
Conversation
This allows users to set configuration that would have precedence on env variable. This is very useful when some post-processing is done on the configuration.
Adding a method to merge config in the override section
Fix AllSettings when some map keys contain the key delimiter
Expose type casting errors
Merge changes from original repo
Try using `UnmarshalStrict`, if it fails, print the errors as a warning and try again with plain `Unmarshal`. Errors look this way: ``` 2019/03/26 15:11:33 warning reading config file: yaml: unmarshal errors: line 6: key "api_key" already set in map ```
…rebased Warn when a yaml file has duplicated keys
This can be used to enforce a config schema
For consistency
By creating a new Viper for each test instead of using the global one
Make tests independent from each other
Enable storing a set of known valid config keys
run `go mod tidy`
Go modules fix
define custom install to make go modules work
…-components Update codeowners for Agent Shared Components
IsConfigured on an inner setting checks children's env vars
Bump mapstructure to v2.4.0
Remove unused exported functions
remove viper remote feature (and directory)
A section is an inner node. HasSection returns if a section is defined in the config, regardless of whether it is empty or not. HasSection will return false for leaf nodes with non-nil values.
HasSection method returns if a section exists
find function would ignore any nil value preventing from working.
Replace gopkg.in/yaml.v2 with go.yaml.in/yaml/v2
Function relying on allSettings would not always return the same data when empty yaml section where used. Env vars like "a_b_c: 123" with Yaml like: ``` a: b: ``` Would return different result depending on the map order from allKeys.
…orpatch/go/0-1781556124 fix(deps): vuln gopkg.in/yaml.v2 (patch → v2.2.8)
We need to use 1.25 to be compatible OTLP agent
|
Matthew Hardwick seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account. You have signed the CLA already but the status is still pending? Let us recheck it. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
18 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.