3 Commits

Author SHA1 Message Date
Jeremy Stanley
e2a1facede Sync project-config before deploying accessbot
The run-accessbot playbook relies on the accessbot role which
installs /etc/accessbot/channels.yaml from openstack/project-config,
so needs to make sure it uses the latest copy of that file. Add the
sync-project-config role before that so we'll have it.

Without this, application of accessbot configuration changes always
lags by one iteration, so we were perpetually applying the previous
version when deploying.

Change-Id: Ief318d10e7660a53cc92336d715116138ddf51b8
2021-07-09 23:15:52 +00:00
James E. Blair
fe2aa71eaf Run accessbot role before running accessbot
This will cause the config files to be updated (among several
other things we don't care about).

Change-Id: If1c1622eacbe820d5c7bdbb9681e673acbf88f98
2021-05-29 13:06:27 -07:00
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