papollo

Python client for Apollo config center, with sync and async support.

from papollo import Apollo

client = Apollo("http://apollo-config:8080", "demo-app")

client.get("timeout")                          # "30", or None if missing
client.get("timeout", "10")                    # with default
client.get("db.url", namespace="database")
client.namespace("app.json")["content"]        # non-properties namespace
client.refresh()                               # pull latest releases

from papollo import AsyncApollo

client = AsyncApollo("http://apollo-config:8080", "demo-app")

await client.get("timeout")
await client.refresh()

A client is meant to live as long as the process, usually as a module level object. It holds an httpx connection pool, so call close() (or await client.aclose()) if you create short lived clients. Both also work as context managers. An AsyncApollo is bound to the event loop it is first used in.

Namespaces are fetched on first access and then served from memory. refresh() refetches every loaded namespace, and refresh(name) also loads a namespace that was not loaded yet, which is handy for failing fast at startup. Failures raise ApolloError and keep the previously cached config.

Other options: cluster, secret (access key), ip and label (gray release), timeout, and http_client to bring your own httpx.Client / httpx.AsyncClient. When timeout is not set, the httpx client's own timeout is used. ip is not detected automatically, so IP based gray release only works when it is set.

Testing

Most tests run against a real Apollo at http://localhost:8080, the rest cover pure functions and failures a real server can not produce on demand. The easiest server is the quick start all in one jar with an in memory H2 database:

SPRING_PROFILES_ACTIVE=github,database-discovery,auth SPRING_PROFILES_GROUP_GITHUB=h2 \
LOGGING_FILE_NAME=/tmp/apollo.log java -jar apollo-all-in-one.jar

uv run pytest

Tests that need Apollo are skipped when it is not reachable. Set PAPOLLO_REQUIRE_APOLLO=1 to make them fail instead, which is what CI should do. The portal at http://localhost:8070 is used to create apps and publish releases. Use APOLLO_CONFIG_URL, APOLLO_PORTAL_URL, APOLLO_PORTAL_USER, APOLLO_PORTAL_PASSWORD and APOLLO_ENV to point elsewhere.