Pact Broker

Why the cloudimg image

Pact Broker has no authentication of its own unless credentials are supplied, and the official image turns authentication on only if it finds them, so a missing configuration file produces an open broker rather than one that refuses to start. The cloudimg image never lets that happen: the broker is held back until the first boot of every instance has generated its own credentials, and it cannot start without them. Two accounts are created rather than one, a write login for your pipeline and a separate read only login for people and dashboards, each with its own password unique to that instance, so nobody who only needs to read the matrix holds the credential that could rewrite it. The upstream example contracts a new broker normally seeds itself with are switched off, so the instance you receive is genuinely empty, and the status badges the official image serves to anyone require a credential here. Only SSH and HTTPS are reachable: the broker never leaves the loopback interface, there is no plaintext port at all, and the database has no network listener whatsoever. The base URL the broker writes into every link it returns is resolved per instance, so CI tooling can follow those links immediately. An on instance self test publishes a contract, reads it back, records a verification result and checks can i deploy answers correctly both ways before removing everything it created. Paired deployment guide and 24/7 cloudimg support.