Juntai Configuration Client

juntai-configuration-client is the backend Python client for publishing and resolving opaque configuration revisions. The stable import is juntai.configuration.

After the corrected release is published, backend services install only:

python -m pip install "juntai-configuration-client>=1,<2"

The package pushes payload bytes directly to an OCI Distribution-compatible registry, verifies the immutable manifest digest and media types, and registers generic metadata through the internal Configuration Registry RPC service. Resolution obtains the exact metadata through that service, pulls directly from OCI by digest, and verifies every descriptor before returning opaque bytes. Domain services continue to own serialization, schemas, and interpretation.

The previous juntai-configuration distribution and its associated evidence are superseded and must not be used or republished. Its external deletion is not a release gate and this project does not provide an alias or compatibility bridge. A corrected juntai-configuration-client package is built only from the pinned Configuration Registry v1.0.0 Protobuf release and the pinned FuseAPI generator.

Generated modules are an implementation detail. Callers use only the high-level ConfigurationClient workflows. Browser applications, Console or Micro-UI code, registry administration, and OCI credential behavior are outside this package.

Owning backend services inject platform-provided workload identity and an OCI transport. This package constructs only a secure mTLS gRPC channel; it has no insecure Registry mode and does not acquire workload or OCI credentials:

from juntai.configuration import ConfigurationClient

with ConfigurationClient.from_workload(
    registry_target="dns:///configuration-registry.platform.svc:7443",
    oci=oci_transport,
    identity_provider=workload_identity_provider,
) as configurations:
    published = configurations.publish(
        namespace="runtime",
        name="credit-review",
        kind="axiom.workflow-runtime",
        payload=serialized_configuration,
        media_type="application/vnd.juntai.axiom.workflow-runtime.v1+json",
        provenance={"source_revision": source_revision, "build_id": build_id},
        idempotency_key=idempotency_key,
        correlation_id=correlation_id,
        deadline_seconds=10,
    )
    exact_bytes = configurations.resolve_and_download(
        published.reference,
        correlation_id=correlation_id,
        deadline_seconds=10,
    )

The metadata RPC accepts only the exact owner contract. Registration sends source_revision and build_id; tenant, owner, producer identity, and creation time are server-derived. Resolution always uses the exact tenant-scoped configuration_id + revision_id pair and never follows an alias.

Development

python scripts/check_production_boundary.py
uv sync --locked --all-groups --no-editable
uv run --locked --no-sync python scripts/generate_registry_grpc.py --check
uv run --locked --no-sync pytest
uv run --locked --no-sync ruff format --check .
uv run --locked --no-sync ruff check .
uv build

The OCI conformance vector is conformance/configuration-oci-v1.json. The exact Registry v1.0.0 owner pin is contracts/upstream/configuration-registry.lock.json; its source is reproduced under contracts/upstream/configuration-registry/v1, and generated modules live only under juntai.configuration.generated.juntai.registry.configuration.v1.

Deterministic stub generation is pinned independently through juntai-fuse-api[grpc-generated]==1.1.2, profile juntai.fuse.profile.grpc-generated v1.0.0. Its immutable release identity and toolchain are recorded in contracts/upstream/fuse-api-generation.lock.json.