Code review comment for lp:~allanlesage/uci-engine/coverage-retriever-juju-deployment

This should be enough to deploy the coverage retriever. There is additional work to be done to add relations to other parts of the ci-engine deployment, but that can be done later.

This presents a small problem in that we need to be more flexible in how components are deployed. For example, the default behavior of deploy.py is to deploy everything needed for the ci-engine deployment. Does that include the coverage components or the components for some other future add on service? Just something that needs to be addressed. I think we look for ways to solve this problem at the next face to face sprint.