I think we might have a potential issue where we specify the k8s deployment to use the specific image in
gwa-deploy/resources/deployment.yaml:
image: cjtkirk1/gwa:latest
Basically it might give us issues if either:
We are running multiple concurrent builds/deploy (either via GH actions or locally) at the same time (and a different gwa:latest image is tagged with that tag)
We run a previous older commit which tags it with the gwa:latest tag.
I mention it as I think we might have run into the issue on #110 where I seem to have tested it with a success on my fork branch yet you report an exception being thrown.
Maybe something to just keep in mind and isn't actually effecting anything - a bit difficult to tell for sure.
Usually what I do here to avoid this issue is tag the image with the commit SHA hash.
I think we might have a potential issue where we specify the k8s deployment to use the specific image in
gwa-deploy/resources/deployment.yaml:Basically it might give us issues if either:
gwa:latestimage is tagged with that tag)gwa:latesttag.I mention it as I think we might have run into the issue on #110 where I seem to have tested it with a success on my fork branch yet you report an exception being thrown.
Maybe something to just keep in mind and isn't actually effecting anything - a bit difficult to tell for sure.
Usually what I do here to avoid this issue is tag the image with the commit SHA hash.