-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
fix: Remove depricated entry_parser
from scrapeconfig
#2752
Conversation
c35dfc1
to
fb56d92
Compare
entry_parser
from scrapeconfigentry_parser
from scrapeconfig
fb56d92
to
3f01b4a
Compare
@@ -82,7 +80,11 @@ type PushTargetConfig struct { | |||
|
|||
// DefaultScrapeConfig is the default Config. | |||
var DefaultScrapeConfig = Config{ | |||
EntryParser: api.Docker, | |||
PipelineStages: []interface{}{ |
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.
[q]: unfortunately coz the type of pipeline stages are just []interface{}
. Would love to know if there is a better way!
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.
Changes to the comments look OK.
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.
LGTM
Signed-off-by: Cyril Tovena <cyril.tovena@gmail.com>
What this PR does / why we need it:
To remove deprecated
entry_parser
config and replace it withpipeline_stages
everywhere.Which issue(s) this PR fixes:
Fixes #2631 #2577
Special notes for your reviewer:
remove deprecated
entry_parser
from scrapeconfig. use pipeline_stages instead.Checklist