Ticket #578 (new enhancement)
Add an attribute deprecated to group to give a deprecated date
| Reported by: | [email protected]… | Owned by: | desai |
|---|---|---|---|
| Priority: | minor | Milestone: | Bcfg2 1.4.0 Release |
| Component: | bcfg2-client | Version: | 1.0 |
| Keywords: | deprecation | Cc: |
Description
Something that would be interesting is to implement the possibility to have a expired attribute to a group so we can define it dirty after a certain date. By default there would no date, now would meen it's expired whatever the date is.
With this feature on, it would be easier to maintaint big park of computer. We could define some group as deprecated this way with the 'now' value. Some groups defined as Operating System could tell us that the os is no supported by the editor anymore with security updates.
Attachments
Change History
comment:1 Changed 15 years ago by [email protected]…
- Keywords deprecation added; expiration removed
- Summary changed from Add an attribute expired to group to give an expiration date to Add an attribute deprecated to group to give a deprecated date
Changed 15 years ago by [email protected]…
- Attachment 0001-Added-an-admin-mode-to-bcfg2-so-we-can-find-out-what.patch added
Patch to add an admin mode for deprecation detection
comment:2 Changed 15 years ago by [email protected]…
I feel the patch is not quite complete in my sense. This ways we could to a cron mail jobs easy but I'd like to also have a ways to query bcfg2 on the deprecation status of the client with an ERP system. So the salesman could do some profit ;)
I would like to have your thought on this.
Changed 15 years ago by [email protected]…
- Attachment patch0.patch added
2nd version of the patch, with better output
comment:4 Changed 13 years ago by solj
- Milestone changed from Bcfg2 1.0 Release to Bcfg2 1.0.1 Release
comment:5 Changed 13 years ago by solj
- Milestone changed from Bcfg2 1.0.1 Release to Bcfg2 1.1.0 Release
comment:6 Changed 13 years ago by solj
- Milestone changed from Bcfg2 1.1.0 Release to Bcfg2 1.2.0 Release
On a second thought, the attribute should be name 'deprecated' instead of 'expired' so there is no confusion