tree a9bfed53185636a6c79751242c51692b433f312d
parent f8aec83b3b7fa4547ec1486c72a1dfadfda6433f
author Ricardo Carrillo Cruz <ricardo.carrillo.cruz@gmail.com> 1480678918 +0000
committer James E. Blair <jeblair@redhat.com> 1490816621 -0700

Add per-repo public and private keys

Every project should have a public and private key to encrypt secrets.
Zuul expects them to already exist under /var/lib/zuul/keys on the
scheduler host.  If an operator manages these keys externally, they
should simply be placed there.  If they are not found, Zuul will
create them on startup and store them there so they will be found on
the next run.

The test framework uses a pre-generated keypair most of the time to
save time, however, a test is added to ensure that the auto-generate
code path is run.

Co-Authored-By: James E. Blair <jeblair@redhat.com>
Change-Id: Iedf7ce6ca97fab2a8b800158ed1561e45899bc51