Custom Query (894 matches)

running the bcfg2 client should not be destructive by default.

it could be either interactive or error out asking the user to specify a mode

-n (no) / -I (interactive) / -y (yes/proactive)

I think this may be an issue with python-apt, but the Purging mechanism is not working properly. Configuration files are being left behind.

I'd like to be able to call a probe from another probe. The driving factor for this is to reduce code duplication in my probes. An example:

I have a probe that uses dmidecode to determine what hardware manufacturer I'm currently running on. This sets a dynamic group that I use within my configuration (manuf-dell, for example).

I have a second probe that queries my RPM database looking for a specific rpm gpg key and sets a dynamic group if I don't find it (rpm_needs_dell_gpg). The problem is, I only want to set this group if I know I'm running on dell hardware.

I have three options for doing this:

1. One monolithic probe that combines these two options so I reduce code duplication. This is unappealing because this can get large quick (for one script).

2. Have my rpm_gpg probe issue the same dmidecode command as my manufacturer probe. This is unappealing because that means I have to update two places if I ever need to change the dmidecode call.

3. Move the manufacturer specific rpm gpg probes into the manufacturer probe. This is unappealing because that means I have to update two places if I ever need to change the rpm calls or methods I use to probe for gpg keys.