jschoubben
68a9235792
Portainer mounts the container runtime's socket, and the catalogue's mount gate refused it — rightly by its own lights, since nothing in the manifest distinguishes a machine facility from the module's data. That distinction is 04-ISSUES/026's open question, so the gate now carries the one facility the catalogue mounts as a named exception beside the citation, one line per facility, never a pattern. Also the confession: the previous commit landed with this gate red, because a pipeline's tail swallowed go test's exit code. The gate was right and the process around it briefly was not.
examples
Things that run, kept here because a contract is easier to read as working code than as prose.
Nothing here is part of the control plane. The control plane decides and never touches a machine (README); everything in this directory runs on a machine and touches it. These are reference implementations of contracts the control plane defines, and a real one ships with the module that ships the software it configures.
postgres-provisioner |
the last step of a credential: reads what the mesh delivered and makes PostgreSQL accept it |
Running the provisioner
--watch reconciles now and again whenever what the mesh delivered changes. That is what lets it
be a module: an ordinary long-running service the host supervises, rather than something that has
to be invoked after every declaration by a timer or a unit wired to a file.
It polls rather than watching the filesystem, because the host writes atomically — the file is replaced, so a watch on the path stops seeing anything after the first replacement. A watcher that silently stops working is worse than a poll.
Credentials are compared by digest and never by content. This runs for as long as the machine is up, and a secret does not belong in a long-lived variable when a hash answers the same question.