Compare commits

..

No commits in common. "c7274fc8bbd514e7ed12d43032ca3d1b9a898d67" and "13327bad6f05e1e0881f70e4577fdc3f7cf33503" have entirely different histories.

View file

@ -21,6 +21,8 @@ if [ -z "$GITHUB_SHA" ]; then
echo "GITHUB_SHA not defined, pass it in the environment with an 'env:' clause to the action" && exit 1
fi
env
echo "Going to apply kustomization configuration at ${KUST_CONFIG}"
echo "K3S_YAML:"
echo "$K3S_YAML"
@ -44,5 +46,15 @@ kubectl --kubeconfig /tmp/k3s.yaml kustomize "/tmp/${KUST_CONFIG}" | sed "s/kust
echo "UPDATED YAML:"
cat /tmp/manifests.yaml
echo "applying..."
# if we have FORGEJO_REF_NAME beginning with "v", then set the image to a tag with value FORGEJO_REF_NAME.
if [ -n "$FORGEJO_REF_NAME" ] && [[ "$FORGEJO_REF_NAME" == v* ]]; then
echo "FORGEJO_REF_NAME starts with v, setting image tag to $FORGEJO_REF_NAME"
# sed -i "s|image: myapp:latest|image: myapp:$FORGEJO_REF_NAME|g" /tmp/manifests.yaml
kubectl kustomize /tmp/${KUST_CONFIG} edit set image myapp=myapp:$FORGEJO_REF_NAME
else
echo "FORGEJO_REF_NAME does not start with v, leaving image tag as is"
fi
kubectl --kubeconfig /tmp/k3s.yaml apply -f - </tmp/manifests.yaml
echo "Done applying kustomized manifests at ${KUST_CONFIG}, success"