Modify

Ticket #733 (closed enhancement: fixed)

Opened 12 years ago

Last modified 9 years ago

RFE: switch in Packages config to turn on/off auto update.

Reported by: Chris Stankaitis <cstankaitis@…> Owned by: desai
Priority: major Milestone: Bcfg2 1.3.0 Release
Component: bcfg2-server Version: 1.0
Keywords: Cc:

Description

Right now under Packages plugin in 1.0 if I update a package in my repo that new version will push out the next time my clients check in. This may not be a good thing depending on the environment. Under pre 1.0 versions this was mitigated by having to regen the PkgMGR xml to update the versions before bcfg2 would "patch" the box. Under 1.0 however unless you want to set a BoundPackage? statement for every package there is no way to stop bcfg2 from upgrading your system in the event your yum repo is updated.

Could a config variable be added to Packages/config.xml possibly

<Update>Yes|no</Update>

which would allow me to tell bcfg2 to verify the package but not update them if there is a newer version? then when the maintenance window happens, or the patchs are testing in staging I can just flip the config to <Update>Yes</Update> and let the boxes patch.

I think this will let me keep the awesome new functionality of the Packages plugin while also giving me some control over when/how my boxes get patched.

Attachments

Change History

comment:1 Changed 12 years ago by desai

  • Status changed from new to accepted
  • Milestone changed from Bcfg2 1.0 Release to Bcfg2 1.0.1 Release

I think that the short term way to solve this is a combination of Decisions? and reporting. In the long term, we should support action decisions as well, so you could specify that upgrades are not allowed, but installations are, etc.

comment:2 Changed 12 years ago by solj

  • Milestone changed from Bcfg2 1.0.1 Release to Bcfg2 1.1.0 Release

comment:3 Changed 11 years ago by solj

  • Milestone changed from Bcfg2 1.1.0 Release to Bcfg2 1.2.0 Release

comment:4 Changed 10 years ago by solj

  • Milestone changed from Bcfg2 1.2.0 Release to Bcfg2 1.3.0 Release

comment:5 Changed 9 years ago by https://www.google.com/accounts/o8/id?id=AItOawnSjgovXZr-_V3vGkvMSR0pc5LDykRc1Nc

  • Status changed from accepted to closed
  • Resolution set to fixed

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

View

Add a comment

Modify Ticket

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


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

 
Note: See TracTickets for help on using tickets.