Re: CIAT configuration

In general, I don't like adding new repos to the set of things people need to know about -- people use Baserock and run their own

infrastructure already have to deal with upstream definitions, their project's definitions, their local infrastructure.git repo, and their local-config/lorries.git repo. So if it can be placed into definitions.git cleanly, then that would be nice. But I can't imagine how it would work without seeing it. One thing I really *don't* want is for a CIAT instance to have a fixed config set at the moment you run `morph deploy`. It's fine to allow specifying a config there, but it needs to be configurable after deployment as well. We made this mistake with Trove and distbuild initially and had to spend time making it possible to 'generic'

instances later on. The 'generic' ones (where you can edit a file in the system named /etc/trove/trove.conf, rerun trove-setup.service and the configuration is then updated) are way more convenient. Sam Sam