Fix bodhi-shell in the BCD development environment

While working on removing Vagrant I noticed this didn't work, so
let's fix it. It runs into the same shebang issue I had problems
with for a couple of other things, and it turns out to be easiest
to just forget about the 'normal' implementation and replace it
with a simple alias, since we know where the config file is in
the development environment.

Signed-off-by: Adam Williamson <[email protected]>

devel/ansible-podman/containers/bodhi/bashrc

@@ -16,6 +16,7 @@ alias bstart="systemctl start bodhi.service celery.service [email protected]
 alias bstop="systemctl stop bodhi.service celery.service [email protected] [email protected]"
 alias blint="pre-commit run -a"
 alias bmessages="journalctl -u fm-consumer@printer -f"
+alias bodhi-shell="python3 /usr/bin/pshell /etc/bodhi/production.ini"
 
 
 function bresetdb {

devel/ansible-podman/containers/bodhi/bodhi.service

@@ -9,6 +9,9 @@ WorkingDirectory=/bodhi/bodhi-server
 ExecStartPre=/usr/bin/poetry -C /bodhi/bodhi-messages install --only-root
 ExecStartPre=/usr/bin/poetry -C /bodhi/bodhi-client install --only-root
 ExecStartPre=/usr/bin/poetry -C /bodhi/bodhi-server install --only-root
+# the shebang on pshell breaks this in the container environment,
+# so we just replace it with an alias in bashrc
+ExecStartPre=rm -f /usr/local/bin/bodhi-shell
 ExecStartPre=/usr/local/bin/bodhi-wait.py
 # we don't run alembic and pserve directly from /usr/bin as some
 # options in their shebangs break finding our bodhi modules