Enclaves
Service Contract
Service contract fields and validation rules.
Every release includes a service contract. Enclavely validates this contract before deployment.
Supported contract
{
"contractVersion": "v1",
"transport": "http1-vsock",
"enclave": {
"cid": 16,
"port": 8080,
"healthcheckPath": "/healthz",
"readinessPath": "/readyz",
"attestationRequired": true,
"capabilities": ["decrypt"]
}
}Fields
contractVersion: must bev1transport: must behttp1-vsockenclave.cid: positive integerenclave.port:1..65535enclave.healthcheckPath: path starting with/enclave.readinessPath: path starting with/enclave.attestationRequired: booleanenclave.capabilities: non-empty list ofsignand/ordecrypt
In enclavely.yaml
service_contract:
contract_version: v1
transport: http1-vsock
enclave:
cid: 16
port: 8080
healthcheck_path: /healthz
readiness_path: /readyz
attestation_required: true
capabilities: [decrypt]Validation points
enclavely buildvalidates the contract schemaenclavely deployenforces contract values used for rollout checks
Health and readiness paths here must match what your service actually exposes.