Modify ↓
Ticket #24 (closed enhancement: wontfix)
ValidateBcfg2Repo as part of init script
Reported by: | [email protected]… | Owned by: | desai |
---|---|---|---|
Priority: | minor | Milestone: | |
Component: | bcfg2-client | Version: | |
Keywords: | Cc: |
Description
Consider running ValidateBcfg2Repo as part of the init script.
Attachments
Change History
comment:2 Changed 17 years ago by anonymous
I would say that you could cause a much worse problem, depending on client configuration, if validation failed, yet the server started and made itself available.
This is just one of many times that I'm sure would be useful times to validate.
comment:3 Changed 17 years ago by desai
- Status changed from new to closed
- Resolution set to wontfix
I am not comfortable making the init script do something like this. I think that it is a fine thing to add as a site-specific customization, but I don't think that it is useful to detect conditions that may or may not be errors, when we can't do anything about them.
Note: See
TracTickets for help on using
tickets.
I think that the long term way we will integrate validation is as a part of file parsing, not as an external process. The validator can be run at any time, and should be run any time changes are performed. I think that we could cause a number of bad side effects if we were to cause any action in event of validation failure, as there are bugs in schemas from time to time.