Ticket #799 (closed enhancement: wontfix)
I wish I could specify custom group on the command line
| Reported by: | somekool <[email protected]…> | Owned by: | desai |
|---|---|---|---|
| Priority: | minor | Milestone: | Bcfg2 1.2.0 Release |
| Component: | bcfg2-client | Version: | 1.0 |
| Keywords: | Cc: |
Description
there are some packages that must not be installed when I kick a new system. so I need to know in the bcfg2 config if this machine is being installed or is it a running system.
this could be done like ...
/usr/sbin/bcfg2 -l blacklist --groups step-kickstart
this would be very flexible and could allow many tricks in the bcfg2 config repository.
thanks
Attachments
Change History
comment:2 Changed 13 years ago by somekool <[email protected]…>
I know the -b option and I am using it quite a bit. this is not what I am looking for.
comment:3 Changed 13 years ago by solj
- Milestone changed from Bcfg2 1.1.0 Release to Bcfg2 1.2.0 Release
I think you may be able to get the functionality you're looking for via the Trigger plugin. At any rate, this feature won't be added for this release.
comment:4 Changed 12 years ago by desai
- Status changed from new to closed
- Resolution set to wontfix
The way to accomplish what you are looking for is asserting a group membership with a probe when a file doesn't exist, and then creating that file when the client is in the group. That is the pattern for one time behavior in bcfg2. The approach you suggest is problematic because it can lead to fault prone setups. (bcfg1 worked this way)
You ought to look at the -b option for the client.