Skip to content
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

Conversation

amousset
Copy link
Member

@amousset amousset requested a review from ncharles May 18, 2020 14:46
Copy link
Member

@ncharles ncharles left a 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)
Copy link
Member

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

Copy link
Member

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

classes => if_ok_cancel("rudder_report_force_component_none");

classes:
# double negation, so that the default is dry_run (in case of error)
Copy link
Member

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

@amousset
Copy link
Member Author

PR updated with a new commit

@Normation-Quality-Assistant
Copy link
Contributor

OK, squash merging this PR

@Normation-Quality-Assistant Normation-Quality-Assistant force-pushed the arch_17095/allow_forcing_a_none_component_in_reporting branch from d116b36 to b5c3a48 Compare May 24, 2020 19:22
@Normation-Quality-Assistant Normation-Quality-Assistant merged commit b5c3a48 into Normation:branches/rudder/6.1 May 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants