trying out patches to services is hard

So I wanted to give https://github.com/theforeman/smart_proxy_pulp/pull/40 a go in the quadlet setup I have…

I had to create a Containerfile:

FROM quay.io/evgeni/foreman-proxy-rpm:3.12
USER root
RUN dnf install -y https://download.copr.fedorainfracloud.org/results/packit/theforeman-smart_proxy_pulp-40/rhel-9-x86_64/08129033-rubygem-smart_proxy_pulp/rubygem-smart_proxy_pulp-3.3.0-2.20241011111146235873.pr40.2.g4ce3ca5.el9.noarch.rpm
USER foreman-proxy

Build it:

podman build -f Containerfile -t quay.io/evgeni/foreman-proxy-rpm:3.12-patched

Then update /etc/containers/systemd/foreman-proxy.container to use the new tag, systemctl daemon-reload, systemctl restart foreman-proxy (maybe I could save the first two if I'd have re-used the tag, but then I wasn't sure podman won't try to re-pull from quay).

That's… suboptimal.

Start by reviewing the quadlet service configuration at /etc/containers/systemd/foreman-proxy.container and the existing service-management entry points in this repository. Reproduce the Containerfile build and systemctl restart flow described in the issue, then define a supported way to try a patched service image without manually rebuilding and editing the unit; done means that workflow is documented or automated and can be verified with the foreman-proxy service.