Open nainaz opened 3 years ago
@nainaz this shouldn't be Quarkus specific. You wrote you run build
before, what repository did you use there? I think the bug is that when you enter incorrect registry in some step, the incorrect value is written to faas.yaml
and the value in the file is then authoritative.
There is inconsistency deploy
is prompting for registry
whereas build
is prompting for image
. This should be unified. What should we do? @boson-project/core
There is inconsistency deploy is prompting for registry whereas build is prompting for image.
I mentioned this in #24 but I don't recall a prompt during deploy
.
I mentioned this in #24 but I don't recall a prompt during deploy.
Well clearly my multi-tasking is getting the better of me. Both prompt if there is no image yet built. But they prompt for the same thing.
❯ faas deploy
A registry for Function images is required. For example, 'docker.io/tigerteam'.
Registry for Function images: docker.io/tigerteam^C⏎
~/demo/foo is 📦 1.0.0-SNAPSHOT via ☕ v11.0.8 took 31s
❯ faas build
Building image:
A registry for Function images is required. For example, 'docker.io/tigerteam'.
Registry for Function images: ^C⏎
@lance there are two kinds of prompt. One explicit by using the -c
flag, the other one is invoked by absence of some value. If a value is absent they both ask for registry. But for the -c
flag it's different.
With the -c
flag you are asked for registry even it it's set, the thing is that the value you enter there is ignored and the value from faas.yaml
is used anyway. I believe that's this bug.
Describe the bug After creating the the image for the Quarkus Function accepting events. kn faas deploy fails with the error message :
To Reproduce Steps to reproduce the behavior:
Expected behavior image should get pushed to quay.io
Screenshots
Desktop (please complete the following information):
Additional context Add any other context about the problem here.