vmware-tanzu
kp image trigger error output
[Reported by @mgbrodi]
Problem: when kp image trigger was run, it resulted in an unrelated and confusing error message, especially since the user expects a build to be triggered by the command.
Error: no builds found
The expectation is to show a more helpful error message.
For this particular case, the root cause of failure was identified as invalid creds for the image - git secret for a private repo was created with a public key (instead of a private key) and also there was a basic auth secret created for an MFA enabled Github account
what trigger really means is invalidate the last build, and run another one
kpack is always checking that the last build is valid, and if not, then it will run another build. running trigger makes the last build invalid and so kpack runs it again
while pushing kpack build image to harbor . i am getting the following error
Error: images.kpack.io "f1c816bf556c88881308j363e48aac28e090e0f9" already exists
