Fabiano Fidêncio cfd8f4ff76 gha: payload-after-push: Pass secrets down ...

The "build-assets-${arch}" jobs need to have access to the secrets in
order to log into the container registry in the cases where
"push-to-registry", which is used to push the builder containers to
quay.io, is set to "yes".

Now that "build-assets-${arch}" pass the secrets down, we need to log
into the container registry in the "build-kata-static-tarball-${arch}"
files, in case "push-to-registry" is set to "yes".

Fixes: #6899

Signed-off-by: Fabiano Fidêncio <fabiano.fidencio@intel.com>

2023-05-19 15:00:06 +02:00

..

cargo-deny-composite-action

github-actions: Add cargo-deny

2022-08-30 09:30:03 -07:00

workflows

gha: payload-after-push: Pass secrets down

2023-05-19 15:00:06 +02:00