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

Add possibility to extend inventory in Rudder with scripts on the client side #403

Open
ncharles opened this issue Nov 14, 2017 · 1 comment

Comments

@ncharles
Copy link
Contributor

The goal is to add an extra tag in the inventory, in RUDDER/CUSTOM_PROPERTIES , that would contain all the JSON outputed by scripts existing in 'C:\Program Files\Rudder\hooks.d' or '/var/rudder/hooks.d'
Script needs to be executable, and will be executed in alphanumerical order
JSON needs to be valid

ncharles added a commit to ncharles/fusioninventory-agent that referenced this issue Nov 14, 2017
ncharles added a commit to ncharles/fusioninventory-agent that referenced this issue Nov 15, 2017
ncharles added a commit to ncharles/fusioninventory-agent that referenced this issue Nov 20, 2017
ncharles added a commit to ncharles/fusioninventory-agent that referenced this issue Nov 20, 2017
@g-bougard
Copy link
Contributor

I don't know if it's really related to your issue, but I'm thinking to enhance Collect task to support JSON file parsing to permit collecting specific data from a well-known JSON file. From the FusionInventory plugin view you'll have the possibility to create Collect job like it's actually done to query win32 registry specifying a path, a hive and value name.

Regarding your issue, this can't replace the fact of collecting ALL the Rudder custom properties placing them in the RUDDER XML namespace. I even don't know if Rudder has the feature to push Collect tasks toward the agent. But it could be a simple helper to collect Rudder custom properties also in GLPI.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants