-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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(config): return error on order set as string #12880
Conversation
Order should be a number, not a string, so instead of silently failing we should call the user to action. fixes: influxdata#12879
Would you prefer this attempt to parse a string to an int first? Or tell and expect the user to use an int? Currently we are silently ignoring the value, and so a user using processors with a string order is not getting the order they want. |
Download PR build artifacts for linux_amd64.tar.gz, darwin_amd64.tar.gz, and windows_amd64.zip. 👍 This pull request doesn't change the Telegraf binary size 📦 Click here to get additional PR build artifactsArtifact URLs |
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.
Shouldn't we have a test-case for this so it will always work?
For me it is file like this; erroring out as the example config shows integer values and docs mention it starts at 1.
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. Thanks for fixing this @powersj!
(cherry picked from commit f1da63d)
Order should be a number, not a string, so instead of silently failing we should call the user to action.
fixes: #12879