0feb838506
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
17 lines
381 B
Bash
Executable File
17 lines
381 B
Bash
Executable File
#!/bin/bash
|
|
|
|
if [ ${DIB_DEBUG_TRACE:-0} -gt 0 ]; then
|
|
set -x
|
|
fi
|
|
set -eu
|
|
set -o pipefail
|
|
|
|
ZUUL_USER_SSH_PUBLIC_KEY=${ZUUL_USER_SSH_PUBLIC_KEY:-$HOME/.ssh/id_rsa.pub}
|
|
|
|
if [ ! -f $ZUUL_USER_SSH_PUBLIC_KEY ]; then
|
|
die "Can not find public key for zuul user!"
|
|
fi
|
|
|
|
# save the public key inside the chroot
|
|
cat $ZUUL_USER_SSH_PUBLIC_KEY >> $TMP_HOOKS_PATH/zuul-user-ssh-public-key
|