The provisioner client accepts credential form none through the mesh-sdk list (issue 774) #564

Merged
jschoubben merged 1 commits from fix/credential-forms-one-list into main 2026-10-30 15:10:29 +00:00
1 Commits
Author SHA1 Message Date
jschoubben 67dcf252ec Check a plan's credential form against mesh-sdk's one list, so the client takes plans naming none again (issue 774)
mesh/delivery merged: source.main moved to novox/mesh-catalog@72cee59acc32
mesh/delivery-group group fix/credential-forms-one-list merged: every member is merged
mesh/check checking 67dcf252ecfa on 82ac613b4ed0 | novox/mesh-catalog#564 in group fix/credential-forms-one-list
Since 13:55 the client refused every plan with credential-form none
(gitea's forge-account, the artifact store), and g14 and shanks placed no
files for mesh-build-go, mesh-build-node, mesh-build-image or ssh-client.
Second meeting of the credential-form list kind: the controller's copy was
fixed alone before. Thorough: one list in mesh-sdk; this client drops its
copy and pins mesh-sdk 9379e9a. A none entry is never a holder's issued
value: its bound values come from the provider's entry, and a secret named
for it fails loudly instead of waiting on a vault that mints nothing.
2026-10-30 16:06:46 +01:00