system-config/playbooks/roles/zuul-user/tasks/main.yaml
Monty Taylor 9fd2135a46 Split eavesdrop into its own playbook
Extract eavedrop into its own service playbook and
puppet manifest. While doing that, stop using jenkinsuser
on eavesdrop in favor of zuul-user.

Add the ability to override the keys for the zuul user.

Remove openstack_project::server, it doesn't do anything.

Containerize and anisblize accessbot. The structure of
how we're doing it in puppet makes it hard to actually
run the puppet in the gate. Run the script in its own
playbook so that we can avoid running it in the gate.

Change-Id: I53cb63ffa4ae50575d4fa37b24323ad13ec1bac3
2020-04-23 14:34:28 -05:00

21 lines
445 B
YAML

- name: Create zuul user
user:
name: zuul
comment: User for running remote zuul jobs
shell: /bin/bash
- name: Install sudo permissions for zuul
copy:
src: zuul.sudo
dest: '/etc/sudoers.d/zuul'
owner: root
group: root
mode: 0440
when: zuul_user_enable_sudo
- name: Install system-config per-project key for zuul
authorized_key:
user: zuul
state: present
key: '{{ zuul_user_authorized_key }}'