-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
reorganisation of constants and validation of config settings #266
reorganisation of constants and validation of config settings #266
Conversation
- string constants being used have been defined in the correct modules - when they are used they have to be prefixed with the module, hence it becomes more clear to which module they belong - a new file tools/cvmfs_repository.py for constants used for the settings of a CernVM-FS repository is added - both the event handler and job manager verify at the start that required/recommended settings are defined in 'app.cfg'
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note: I have not run the bot instance on our site with this PR yet, I have only reviewed the code.
I think it's a good change and it adds needed structure for the bot configuration which will make it easier to setup on other sites too! I've just noted a few nitpicking things which could just be me not understanding the logic, go ahead and reject if that's the case.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great to me!
This PR turned out to be larger than originally intended (just validating that required config settings are defined when bot components start). However, it reorganises / brings consistent structure to how and where string constants are defined. Hopefully, this makes the code easier to read.
TODO