public-acme: the roots field is named roots, not root

step-ca (the other acme-ca provider) already spells it correctly; route-
proxy's own template reads ${bound:acme-ca:roots}. Found live, assigning
public-acme for the first time tonight: the mesh refused the push outright
rather than composing a broken binding — 'route-proxy asks its acme-ca
binding for roots, and what answers it says ... root'. Empty stays empty:
a public CA's root is the system trust store already, per route-proxy's
own design (an empty ACME_CA_BUNDLE means exactly that).

This commit is contained in:

jschoubben

2026-09-25 18:08:28 +02:00

parent dd5b973e66

commit 3147fac08b

1 changed files with 1 additions and 1 deletions

									
										modules/public-acme/module.json
									
		+1
		-1
	
												View File
												
					@@ -13,7 +13,7 @@

					      "at": "acme-v02.api.letsencrypt.org",

					      "at": "acme-v02.api.letsencrypt.org",

					      "port": 443,

					      "port": 443,

					      "path": "/directory",

					      "path": "/directory",

					      "root": ""

					      "roots": ""

					    }

					    }

					  }

					  }

					}

					}