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 #15008: Add a "Rudder by example" to add CPU vulnerabilities status to inventory #584

Conversation

amousset
Copy link
Member

@amousset amousset commented Jun 3, 2019

@amousset amousset force-pushed the ust_15008/add_a_rudder_by_example_to_add_cpu_vulnerabilities_status_to_inventory branch from f4d5912 to c4dc27d Compare June 3, 2019 11:17
@amousset
Copy link
Member Author

amousset commented Jun 3, 2019

Commit modified

@amousset amousset force-pushed the ust_15008/add_a_rudder_by_example_to_add_cpu_vulnerabilities_status_to_inventory branch from c4dc27d to 4c898ca Compare June 3, 2019 11:21
@amousset
Copy link
Member Author

amousset commented Jun 3, 2019

Commit modified

@amousset amousset force-pushed the ust_15008/add_a_rudder_by_example_to_add_cpu_vulnerabilities_status_to_inventory branch from 4c898ca to 1ce3a72 Compare June 3, 2019 11:22
@amousset
Copy link
Member Author

amousset commented Jun 3, 2019

Commit modified


An inventory extension script can be written in any language, it just needs to be an
executable file placed in `/var/rudder/hooks.d` that outputs a json object. It will be called at each
inventory,and its output will be added into it.
Copy link
Member

Choose a reason for hiding this comment

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

Missing space after comma

* Determine the status of the node for each known vulnerability
* Add details in a separate variable for mode advanced handling

In our case, we have write a small python script (the https://github.com/Normation/rudder-tools/blob/master/contrib/inventory-hooks/cpu_vulnerabilities.py[script] and its https://github.com/Normation/rudder-tools/blob/master/contrib/inventory-hooks/cpu_vulnerabilities.adoc[documentation]) that outputs our CPU vulnerabilities in the
Copy link
Member

Choose a reason for hiding this comment

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

we wrote or we have written

@amousset
Copy link
Member Author

amousset commented Jun 3, 2019

Commit modified

@Normation-Quality-Assistant
Copy link
Contributor

This PR is not mergeable to upper versions.
Since it is "Ready for merge" you must merge it by yourself using the following command:
rudder-dev merge https://github.com/Normation/rudder-doc/pull/584
-- Your faithful QA
Kant merge: "In law a man is guilty when he violates the rights of others. In ethics he is guilty if he only thinks of doing so."
(https://ci.normation.com/jenkins/job/merge-accepted-pr/10842/console)

@amousset
Copy link
Member Author

amousset commented Jun 3, 2019

OK, squash merging this PR

@amousset amousset force-pushed the ust_15008/add_a_rudder_by_example_to_add_cpu_vulnerabilities_status_to_inventory branch from ed22d1c to bf4536d Compare June 3, 2019 12:42
@amousset amousset merged commit bf4536d into Normation:branches/rudder/5.0 Jun 3, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants