The devuser element is designed to add a single development user and
manage their keys. Any local use of devuser by a developer thus
silently conflicts with zuul-worker.
Additionally, this is currently tacitly taking the public-key from
~/.ssh/id_rsa.pub -- i.e. the public key of the currently building
user. Mixing permissions from the builder into the final-image makes
sense for a development-user case, but not for deploying worker
accounts.
This simply creates the worker account by hand, which is easy enough.
To maintain the status-quo we still source ~/.ssh/id_rsa.pub by
default, but provide a documented flag to override this.
Change-Id: Ic9c9e415c158ad1f057b8d2aa2776dbe2bbd1e47
Now that zuulv2.5 has landed, we can start building our DIBs using the
new zuul-worker element. As part of the jenkins clean up, we'll
eventually be removing all things jenkins from our puppet manifests.
As we move forward, we'll be using DIB to bootstrap our zuul-workers
over puppet.
Change-Id: I0e76931fdb4ca0c7445b1e72dc348f0cf03eaee5
Depends-On: Idb4ef11576671180060fb5b2b1202f9bfec5fd47
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
Ian Wienand