+1. I have no experience with this part of Evergreen, but moving these into the database and providing an Evergreen interface for them seems like a no-brainer.
