Docs · Connectors

Wire in services. Keep the tokens out.

A connector lets a pod reach a forge, pipeline, registry, or database. The token is sealed in the broker; the pod authenticates on the wire and never holds it.

Add a connection

Register a service and its token once. It's brokered - never written into a pod.

>_zsh
# pipe the token on stdin so it never hits your shell history
echo $GITHUB_TOKEN | poddle connect add github \
  --connector forgejo --url https://git.acme.co
✓ connection “github” added (brokered)

Pipe secrets, don't type them

Feeding the token on stdin keeps it out of your shell history and process list. You can pass --token / --user directly for scripts, but stdin is the safer default. --connector is the type - forgejo, woodpecker, or a custom one.

List & remove

>_zsh
poddle connect ls
NAME    CONNECTOR   URL
github  forgejo     https://git.acme.co
poddle connect rm github

Broker it into a pod

Opt a pod into connections through its template's connectors list. When the pod calls the service, the broker injects the real credential on the wire and scrubs stray secrets from the outbound body - the pod only ever holds a revocable handle.

>_.poddle/api.toml
connectors = ["github", "postgres-prod"]

Connection definitions live in ~/.config/poddle/connectors. See every built-in connector type on the connectors page.

Templates →connect reference →Browse connectors →