dekorate.docker.docker-file only works if module root contains a Dockerfile

[kabir]

When using dekorate.docker.registry=localhost:3000 and dekorate.docker.docker-file=src/main/resources/Dockerfile the registry only seems populated properly if there is a file in the module root called Dockerfile.

In the generated META-INF/dekorate/kubernetes.yaml, the presence of a Dockerfile in the module root seems to have an impact on what registry is used for the image in the kubernetes.yaml.

If there is a Dockerfile, as expected, kubernetes.yml contains:

          image: localhost:3000/kabir/issue-100-docker-registry-docker-file-needs-Dockerfile:2.9-SNAPSHOT

If there is no Dockerfile, kubernetes.yml contains the following instead (note 'localhost:3000' is now 'kabir' instead):

          image: kabir/issue-100-docker-registry-docker-file-needs-Dockerfile:2.9-SNAPSHOT

In both cases the generated docker.yml contains the following information (which is correct as far as I can tell):

registry: localhost:3000
dockerFile: src/main/resources/Dockerfile

I've added a test demonstrating the behaviour at https://github.com/dekorateio/dekorate/compare/main...kabir:issue-1000%3Dtest?expand=1. This is an adjusted copy of issue-420-docker-registry.

As-is, it will fail. If you rename _Dockerfile to Dockerfile, it passes. Something seems to be going on during the merging and generating the Kubernetes manifest, but I can't quite put my finger on what is going wrong.

[iocanel]

reproduced.