Connect a config connector

A config connector lets the console manage config that your own backend keeps, beside the config that lives on the platform. It is a project's, set up in the publishing console on the project's Config pages, not on a Connections page. The Connections page lists it and sends you there. See Connections for how connecting works in general.

What it needs

• A backend of your own that answers three calls over HTTPS: describe, snapshot and apply. That is the connector.
• Its address, reachable from the internet. Each call is a path under it.
• The Project settings permission, to set up or remove a connection. Anybody who can see the project can see and test one.

There is nothing secret to give GreenMind. The platform signs every request it makes to your connector with a key pair of its own, and your connector checks the signature against the public keys the platform publishes. No key, token or secret of yours is held here.

Setting it up

On the project's Config pages, open Connections, choose New connection, then connect each environment and Test connection. Config connectors has every step, the three calls, how to check a request, and what the test checks.

If it goes wrong

• A check fails on Test connection. The page names the check. A failing apply almost always means your row hash differs from the platform's. Config connectors lists them all.
• The connector does not answer. The rest of your config carries on. Compare leaves the connector's tables out, and a release that touches them waits until it answers again.