Modify ↓
Ticket #888 (closed defect: wontfix)
generate Probes scripts with a templating system like TGenshi
Reported by: | somekool <[email protected]…> | Owned by: | desai |
---|---|---|---|
Priority: | major | Milestone: | Bcfg2 1.2.0 Release |
Component: | bcfg2-client | Version: | 1.0 |
Keywords: | Cc: |
Description
this might sounds like a crazy request. but it seems to be the best way I could reuse code between probes.
sometimes identical logic needs to be used in several probes script. but no code reuse is possible between them unless I push a library script on all my system. which I don't want to update every now and then. I like the way bcfg2 push those probes script and runs them.
I think it'd be cool to preprocess the probes with TGenshi for more power... In the mean time, I guess I can push the file with a TGenshi ConfigFile? entry and ask the probe to run it. but people here don't like to push scripts with bcfg2.
unless you tell me a probe/group can output multiples group/probe entry?
Attachments
Change History
Note: See
TracTickets for help on using
tickets.
Probes can output multiple groups.
Additionally, http://trac.mcs.anl.gov/projects/bcfg2/ticket/710 requests the ability to output multiple values from a single probe, which will be implemented in 1.2.0. (You already can do that with existing functionality, but it requires more Python in templates than some people might like.)
Given that a probe can be written in any language, and the functionality requested both already exists and will be improved, I don't see any need to add this extra layer of abstraction.