Ticket #807 (closed enhancement: worksforme)
bcfg2 client "diff report" feature
| Reported by: | https://www.google.com/accounts/o8/id?id=AItOawmQmn0B7szSWU05XNIWqq49So7cIisAOpI | Owned by: | desai |
|---|---|---|---|
| Priority: | minor | Milestone: | Bcfg2 1.1.0 Release |
| Component: | bcfg2-client | Version: | 1.0 |
| Keywords: | Cc: | [email protected]… |
Description
At this point in time you can run bcfg2 in a dry run mode which will show you what files will change and in a manual mode where you need to approve the changes before they happen, but to the best of my knowledge there is no easy way to get bcfg2 to tell you what it's going to change inside a config file. You can run paranoid mode and then diff the change against the backup but by that time you have already made the change and possibly made a mistake in your config file.
I think it would be very useful if bcfg2 client could be run in a mode that would:
1) Inform "we are going to change configfile X
2) provide an svn style diff of the old vs new config.
That way you can run in a dry-run + diff report mode and it will show you all the changes not just that it will change a config file. before you apply the changes live.
Right now this is a very manual process as far as I know.
You can get this information using the Dynamic Reports. You will get diffs for each of the 'bad' entries for a client.