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

Refs #4873 - Add bundle command_execution_module() and adapt command_execution() and its tests #58

Closed
wants to merge 2 commits into from
Closed

Refs #4873 - Add bundle command_execution_module() and adapt command_execution() and its tests #58

wants to merge 2 commits into from

Conversation

nperron
Copy link
Contributor

@nperron nperron commented May 20, 2014

Refs #4873 - Add bundle command_execution_module() and adapt command_execution() and its tests

cf http://www.rudder-project.org/redmine/issues/4873

Nicolas Perron added 2 commits May 20, 2014 17:47
"${command_name}"
module => "${module}",
contain => command_execution_module_contain("${shell}"),
classes => classes_generic("${class_prefix}");
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

with this approach, you'll always have repaired status
You should have a convention in the output of the modules, to define when you have a repaired and when you have a kept
Idealy, if the module changes something, then it is repaired, else it is kept (or you can also fail if it fails)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I suppose that we should use classes based on ${class_prefix} (i.e ${class_prefix}report{success,repaired,failed} but it would be difficult to incite users to echo in their scripts something like "command_execution_module__usr_share_local_bin_my_script_sh_report_success".
Is that what you suggest ?

@peckpeck
Copy link
Member

We have no current use case for this.

@peckpeck peckpeck closed this Jun 13, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
4 participants