-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
[AGENTCFG-79] Remove usage of Viper from comp/logs/agent/config/parser.go #34427
Open
rahulkaukuntla
wants to merge
10
commits into
main
Choose a base branch
from
rahul/fixing-viper-parser
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+406
−100
Open
Changes from all commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
f6d99c5
pre-incident code
rahulkaukuntla 66e1fb8
testing every parseable struct and including inputs used in e2e tests
rahulkaukuntla 5767fb8
lint
rahulkaukuntla 7002c49
handling newlines in []string fields
rahulkaukuntla dbdece7
changing name of TagsField to StringSliceField for accuracy
rahulkaukuntla d24decd
fixing test
rahulkaukuntla 69dd42a
resolving merge conflict
rahulkaukuntla 1c79606
Merge branch 'main' into rahul/fixing-viper-parser
rahulkaukuntla 48d2b50
addressing comments
rahulkaukuntla 2d162ec
updating unmarshalling error statement
rahulkaukuntla File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We seems to have a split in the code base between v2 and v3 (108 import of
gopkg.in/yaml.v2
vs 33 fogopkg.in/yaml.v3"
). Any reasons to use v3 in particular ?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it seems that we are migrating to yaml.v3, so I thought that I would get ahead of the curve: #33450