Ticket #799 (closed enhancement: wontfix)

Opened 13 years ago

Last modified 12 years ago

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:


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.



Change History

comment:1 Changed 13 years ago by strauss

You ought to look at the -b option for the client.

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)

WARNING! You need to establish a session before you can create or edit tickets. Otherwise the ticket will get treated as spam.


Add a comment

Modify Ticket

Change Properties
<Author field>
as closed
The resolution will be deleted. Next status will be 'reopened'

E-mail address and user name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.