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
Fixes #17095: Allow forcing a "None" component in reporting #1197
Fixes #17095: Allow forcing a "None" component in reporting #1197
Conversation
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.
This is great, but I fear people would make mistakes using it because of the lack of proper documentation for this method
@@ -728,3 +733,27 @@ bundle agent endExecution | |||
* Any existing configuration policy will continue to be applied without change. * | |||
*********************************************************************************"; | |||
} | |||
bundle agent rudder_set_force_component_none(mode) |
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.
you should advertise that it is necessary to call it twice: once to set the mode, and once to remove the mode, otherwise all reports would be Nonde
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.
also, that calling it with any text but "false" would make futur reports None
tree/20_cfe_basics/log_rudder.cf
Outdated
classes => if_ok_cancel("rudder_report_force_component_none"); | ||
|
||
classes: | ||
# double negation, so that the default is dry_run (in case of error) |
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.
the comment is not correct
PR updated with a new commit |
OK, squash merging this PR |
d116b36
to
b5c3a48
Compare
https://issues.rudder.io/issues/17095