Latest release broke backwards compatibility with git resolver configurations

[ralphbean]

Expected Behavior

In 006c9ac, it is stated that the old format for git resolver config maps will be supported. Updating to the latest should not cause existing git resolver usage to break.

Actual Behavior

Updating caused a pipeline git resolver reference to fail, with message: resolver failed to get Pipeline : error requesting remote resource: error getting "Git" "<redacted>": missing or empty server-url value in configmap.

The end user was able to work around the issue by providing an explicit serverURL in the params of their resolver reference, but the docs state that the serverURL is optional.

Additional Info

• Kubernetes version:

Server Version: version.Info{Major:"1", Minor:"28", GitVersion:"v1.28.12+f154a54", GitCommit:"d616c148c25194c61415fb2f8388497125d193fa", GitTreeState:"clean", BuildDate:"2024-09-03T14:59:33Z", GoVersion:"go1.20.12 X:strictfipsruntime", Compiler:"gc", Platform:"linux/amd64"}

• Tekton Pipeline version:

❯ tkn version
Client version: 0.37.0
Chains version: v0.22.2
Pipeline version: v0.65.0
Triggers version: v0.29.1
Operator version: devel

[vdemeester]

@piyush-garg

[PuneetPunamiya]

/assign

[vdemeester]

@ralphbean can you share us a redacted version of the configmap ?