Push and login using podman action vs from buildah action?

[anitabee]

👋
Not sure if this question belongs here so feel free to point me to different direction.

What I am trying to do
I am trying to make workflow that will build image using this action and push it to in-house container registry. From the runners I am using GitHub ARC setup with Kubernetes mode, this means that workflow jobs in which I build Containerfile spins in separate container (buildah).

The challenge I am having
As I run each job in separate container, If I want to use recommended flow from this action:

1. Build image with buildah redhat-actions/buildah-build@v2 (buildah)
2. And than push to registry redhat-actions/push-to-registry@v2 (podman)

I either need to have custom docker image that has both podman and buildah or I need to stash image somewhere to use it next job, the later one doesn't look like viable option and custom image I would do only in case I don't have other options.

The question
One other thing I thought of (which is why the question) is to have custom action that supports push-to-registry using buildah. But I am wondering if you opted for using podman push/login on purpose? As in, is podman's purpose to do auth and push and I am going agains current if I opt for buildah?

Thanks in advance